Cart
[Home] [By Thread] [By Date] [Recent Entries]
Eric van der Vlist wrote: > > I have mixed feelings about this long discussion about XML IDs. > > On one hand, the concept of ID seems to be very useful and we obviously > need unique IDs to avoid ambiguity. > > OTH, can an ID for application X be exactly the same than an ID for > application Y? Can we be sure that their needs will be close enough to > guarantee that they will refer to the same "object" with the same scope? An ID is the name of a subresource (fragment) that _the document asserts_. Applications are free to use these document defined names, or choose others. Fragment identifiers of URIs are intended to be parsed according to media type (perhaps application/xml) and as such the idea that there is an "XML name" for a fragment of a document is a completely valid one, of course realizing that other applications may choose to name things in different ways. For example XSLT keys or XML Schema keys, the point being that if the HTTP server returns the document of media type application/xml, that the fragment identifier will have a consistent interpretation. It is important to start with this as a basis. Jonathan
|
