Draft for review: ISO 8601 date work on IS 29500

[Chris Rae]

Hi Murata-san: thanks for writing this one up. I just spoke to Gareth and we feel like this is outside the scope of the date amendment as it has a reach far broader than just dates. However, it does look like something worth capturing in schema - would it be okay if we suggest creating a DR to cover this?

Chris

-----Original Message-----
From: MURATA Makoto (FAMILY Given) [mailto:eb2m-mrt at asahi-net.or.jp] 
Sent: 28 July 2010 22:09
To: e-SC34-WG4 at ecma-international.org
Subject: Re: Draft for review: ISO 8601 date work on IS 29500

Here is a rewrite.

sml_typeDesignatorAndContents = 
  (attribute t { string "b"}, element f { sml_CT_CellFormula }?,
                              element v { xsd:bool })
  | (attribute t { string "d"}, element f { sml_CT_CellFormula }?,
                                element v { xsd:date })
  | (attribute t { string "n"}?, element f { sml_CT_CellFormula }?,
                                 element v { xsd:long | xsd:float })
  | (attribute t { string "e"}, element f { sml_CT_CellFormula }?,
                                element v { s_ST_Xstring })
  | (attribute t { string "str"}, element f { sml_CT_CellFormula }?
                                  element v { s_ST_Xstring })
  | (attribute t { string "s"}, element v { xsd:short })
  | (attribute t { string "inlineStr"}, element is { sml_CT_Rst })

I still have some questions.

1) When @t="str", do we have to allow both <f> and <v>?
2) When @t="s", are permissible values of <v> xsd:short?
3) When @t="n", are permissible values of <v> xsd:long or xsd:float?  It
    appears that 9999999999999999 is silently converted to
                       9999999999999990.
4) When @t="b", can <v> contain true or false?  Or, can they
                          only contain 0 or 1?
Cheers,
Makoto