OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

office-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: ODF 1.2 CD03 (all versions) 17.3.13 (dateOrDateTime)


Section 17.3.13 (dateOrDateTime) has the following text:

"A dateOrDateTime value is essentially an [xmlschema-2] date and time
value with an optional time component. In other words, it may contain
either a date, or a date and time value."


It is unclear to me what "essentially" means. Does the value sometimes
not contain an xmlschema-2 date and time value?

Proposed solution:

Make it clear that either:

1) a dateOrTime value is defined (and must conform to) as specified in
(basically the reference that is already used)

2) add descriptive text to the specification with examples of when
"essentially" applies and when "essentially" does not apply.

I would encourage ODF TC to go with "option 1". It would enable
maximum reuse of existing libraries conforming to "xsd:datetime".

Jesper Lund Stocholm
SC34/WG4 http://www.itscj.ipsj.or.jp/sc34/wg4/

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]