W3C home > Mailing lists > Public > w3c-rdfcore-wg@w3.org > March 2002

Re: xml literal and xslt (resend)

From: Dave Beckett <dave.beckett@bristol.ac.uk>
Date: Mon, 11 Mar 2002 15:36:57 +0000
To: Jeremy Carroll <jjc@hplb.hpl.hp.com>
cc: w3c-rdfcore-wg <w3c-rdfcore-wg@w3.org>
Message-ID: <13879.1015861017@tatooine.ilrt.bris.ac.uk>

Not replying to all this message; but I'm summarising something that
I read underlying this:

  Applying XSLT over RDF/XML (or XML) with embedded XML that uses
  qnames in attribute values can mess things up.  This is due to
  RDF's XML syntax not knowing about such things and XSLT and other
  XML specs using them.

I don't see how this is an RDF Model question, and I haven't been
hearing any large requirement for users for XSLTing lots of RDF/XML.
If XSLT's design makes it hard to do this particular case, that isn't
an issue the RDF Core WG can or should address.

So I'd reduce your assumptions from:

- we want RDF/XML to be processable through XSLT without getting corrupted.

  but it doesn't seem easy to do in certain cases where qnames as
  attribute values are meaningful in embedded XML inside parseType
  litearl.  Sorry, we have no solution at this time.

I feel we shouldn't over-engineer and require new
implementation code in order to address this.

I definitely support:

  "dropping qnames in attribute values from the level of ambition,
  and merely trying to not prevent implementations from treating
  unusual namespaces unusually" -- Jeremy

Note there is a use case for PIs in embedded XML, recently posted to

Received on Monday, 11 March 2002 10:40:09 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:53:56 UTC