Re: [xml-dev] ID/IDREF is evil
Arjun,
That explains a lot. You see that limitation now within the context of NIEM and other largely relational standards, where you have id and idref artifacts. Because idref is only defined relative to its enclosing document, this means that it's remarkably difficult to create a reference to remote entities, meaning that any NIEM document effectively has to contain the entire serialization of all of its objects. In some cases this makes sense, but in a fairly significant number its a truly bizarre constraint (for instance, in those situations where you are adding a new member to a family in an insurance form, you actually have to send EVERYONE covered in that form.
Kurt
Kurt Cagle
Invited Expert, XForms Working Group, W3C
Invited Expert, XForms Working Group, W3C
Managing Editor, XMLToday.org
443-837-8725
On Mon, Feb 3, 2014 at 5:39 PM, Arjun Ray <[email protected]> wrote:
On Mon, 03 Feb 2014 23:33:21 +0000, you wrote:An omission in XML 1.0 due to time constraints and the "requirement"
| #1 being that you need one of those ghastly DTDs.
that no new syntax was to be introduced that the WebSGML TC would not
sign off on.
Declaring ID attributes in an internal subset was quite obviously a
non-starter. We should have bit the bullet then and invented some new
syntax. (I actually thought of several back then, but held my peace.)
_______________________________________________________________________
XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.
[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: [email protected]
subscribe: [email protected]
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php