[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: IDREF*S*
Oops, sorry about that ... ----- Original Message ----- From: "James Clark" <jjc@jclark.com> To: "Kurt Cagle" <kurt@kurtcagle.net> Sent: Wednesday, May 02, 2001 9:16 PM Subject: Re: IDREF*S* > I suggest you send your replies to the whole list. > > ----- Original Message ----- > From: "Kurt Cagle" <cagle@olywa.net> > To: "James Clark" <jjc@jclark.com> > Sent: Thursday, May 03, 2001 11:09 AM > Subject: Re: IDREF*S* > > > > > XML allows a single attribute value to contain more than one reference. > Do > > > we need to support this in out ID/IDREF replacement feature? (I believe > > > Schema's key/keyref feature does not support this.) > > > > It's a pain to convert idref="idref1 idref2 idref3" into individual > > references in XSLT or DOM. It is far easier to work with > > <refs> > > <ref idref="idref1"/> > > <ref idref="idref2"/> > > <ref idref="idref3"/> > > </refs> > > > > even if it somewhat more verbose. This becomes a clean iteration with no > > additional processing, select="//ref/@idref", and is easier to follow from > a > > legibility standpoint. It also makes it easier to pass xlink or rdf > > information this way, whereas attempting to do the same with white space > > separated attribute values is considerably uglier. > > > > -- Kurt > > > > > > > > > > > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC