On Fri, Oct 8, 2010 at 8:46 AM, Henry S. Thompson <ht@inf.ed.ac.uk> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Jonathan Rees writes: > >> (I still don't know whether having type ID is enough to make an >> attribute fragid-defining.) In that case, my suggestion would be to change the (non-normative) xml schema document for RDF/XML to not make rdf:ID an ID. Then this issue will go away. Do you have a more specific pointer to the relevant section in XPointer so I can have that for future reference? Also, is there any formal connection between the current XML schema document and the spec? If not, it's a bit odd that W3C should serve anything at all about this, and I would even recommend that it be considered for removal. -Alan > > Yes, it is, per XPointer and _a posteriori_ per 3023bis. > > ht > - -- > Henry S. Thompson, School of Informatics, University of Edinburgh > 10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440 > Fax: (44) 131 651-1426, e-mail: ht@inf.ed.ac.uk > URL: http://www.ltg.ed.ac.uk/~ht/ > [mail from me _always_ has a .sig like this -- mail without it is forged spam] > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.6 (GNU/Linux) > > iD8DBQFMrxKQkjnJixAXWBoRAnAaAJ0ceV5U1Ss1u9ybVKgB8oTspolBEwCeKtZn > JIvUUCCsiZpTOZDsEy19BqE= > =702j > -----END PGP SIGNATURE----- > >Received on Friday, 8 October 2010 20:30:21 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:35 UTC