[
Lists Home |
Date Index |
Thread Index
]
Yes, but we do get the cases such as the X3D MFString
mappings that become ugly for authors and error prone.
It should have been done with elements, but applying
that as a general rule to the language for consistency
would have resulted in a very verbose language. Today,
the normative definition for the XML encoding is an
ugly and heavily parameterized DTD which when contrasted
to the lighter cleaner curly syntax which is almost the
same as VRML97, gives the X3D encoding something of a
black eye. There is an XML Schema, but I don't think
anyone has put their mind to doing a RELAX NG version.
It could improve the situation but not being a RELAX
designer, I can't say. Having just been elected to
the BoD, it is something I will suggest.
len
-----Original Message-----
From: James Clark [mailto:jjc@jclark.com]
As regards list, RELAX NG is already providing more than W3C XML Schema.
For example, in RELAX NG you can have a list of an NCName followed by a
URI. As for why we didn't go further than this and support
non-whitespace separated lists, I think there was doubt as to whether
this was pushing the envelope in the right direction. Isn't it better
to mark up complex structure explicitly with elements and attributes?
The general policy for version 1.0 was only to put in features that we
were sure about it. Non-whitespace separated lists are something that
could easily be added in version 2 if experience with version 1.0 shows
it to be desirable.
|
