ORA-DM-163-B: incomplete rules for regenerating the string value

SECTION 6.2.2: Accessors (in 6.2 Element nodes)

dm:string-value(): the note about "recovering" the original 
lexical representation of xs:dateTime, xs:date and xs:time 
types hints that the model is that the original lexical
representation can be lost (probably as a result of forming the 
PSVI).  If that is the case, then don't we need to talk about some 
other types as well?  For example, xs:duration.  There are
many equivalent ways to represent a zero duration, such as
P0Y = P0M = P0D = PT0H = PT0M = PT0S.  Given an element of 
simple type xs:duration whose value is the zero duration, 
which of these (or many other candidates) is the string value?
In general many types have more than one lexical representation
for the same value.  Since the model is that the implementaiton
is not required to save the true original lexical representation,
we need rules telling which lexical representation to 
regenerate as the string value.

- Steve B.

Received on Monday, 16 February 2004 17:26:11 UTC