You could use a regex or separate them by element name.
The latter simplfies the validation as to container
but it does nothing with regards to the actual content
unless you microparse (the regex). Actually, given
any use of a typed text node where the text node
value tells you the type, you always have to resort
to microparsing for safe validation. It isn't that tricky.
len
From: Art Botterell [mailto:]
On Jun 9, 2005, at 7:44 PM, Renato Iannella wrote:
> Since a URN is part of the URI family, then we could have one element
> that covers booth cases:
Except that the valueListName (the URN) needs to be mandatory while
the valueListLocation (the URI) would be optional. Not sure how to
enforce that if they share an element.
It's sort of like the dual use of <uri> in <resource>... relying on
the particular data value to inform the semantics seems like it may
be unnecessarily tricky.
