On Thu, 1 Mar 2001, John Halleck wrote:
> [...]
> Let's also not confuse the concept of each station have a unique identifier with
> the concept of each station having an XML ID.
>
> Assuming
> <!ELEMENT station ...>
> <!ATTLIST station name CDATA>
> <!ATTLIST station unique NMTOKEN>
> we can have the first occurance of the point be
> <station name="A1" unique="p1">
> and later when the loops close we can have
> <station name="a1" unique="p1">
> down in that page. This is legal, and everywhere the point appears it
> has the same unique identifier
> HOWEVER, if unique is an ID then this is not legal. While a given ID can
> can be referenced from all over the place, it can only appear ONCE IN THE
> FILE, so the second occurance is above is not legal.
I should clairify... it can exist as an ID definition only at one point
in the file. (If a given attribute is an ID, then it can appear with a
specific value once.)
Of course, any number of IDREFs can point at it.
> You could, of course do something like:
> <!ELEMENT station ...>
> <!ATTLIST station name CDATA>
> <!ATTLIST station uniqueID ID #IMPLIED>
> <!ATTLIST station uniqueREF IDREF #IMPLIED>
> and recast the example as:
> <station name="A1" uniqueID="p1">
> and then when the station appears later in the data when we close the
> loop we would have:
> <station name="a1" uniqueREF="p1">
> but I personally thing this is ugly.
> I'd personally prefer that the unique item associated with a station or
> shot not be an XML ID.
>
>
>
> > Garry Petrie
> >
>
This archive was generated by hypermail 2b30 : Mon Apr 02 2001 - 18:00:00 CEST