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

RE: xml:base and rdf:parseType="Literal"

From: Jeremy Carroll <jjc@hplb.hpl.hp.com>
Date: Mon, 15 Apr 2002 13:43:48 +0100
To: "Dave Beckett" <dave.beckett@bristol.ac.uk>, "Brian McBride" <bwm@hplb.hpl.hp.com>
Cc: "RDF Core" <w3c-rdfcore-wg@w3.org>
Message-ID: <JAEBJCLMIFLKLOJGMELDIEKGCDAA.jjc@hplb.hpl.hp.com>
I also think "No" but for reasons that perhaps I should have highlighted

The exc-c14n spec says:

The exclusive canonical form of a document subset is a physical
representation of the XPath node-set, that is an octet sequence, produced by
the method described in this specification. It is as defined in the
Canonical XML Recommendation [XML-C14N] except for the changes summarized as

+ attributes in the XML namespace, such as xml:lang and xml:space are not
imported into orphan nodes of the document subset, and
+ namespace nodes that are not on the InclusiveNamespaces PrefixList are
expressed only in start tags where they are visible and if they are not in
effect from an output ancestor of that tag

I see special treatment of xml:base as excluded by the first bullet point.
Our resolution I think then prohibits an implementation that does import.
If we had gone for inclusive c14n it would have gone the other way.


> -----Original Message-----
> From: w3c-rdfcore-wg-request@w3.org
> [mailto:w3c-rdfcore-wg-request@w3.org]On Behalf Of Dave Beckett
> Sent: 08 April 2002 11:41
> To: Brian McBride
> Cc: RDF Core
> Subject: Re: xml:base and rdf:parseType="Literal"
> >>>Brian McBride said:
> > Jeremy,
> Well, you addressed this to the group
> > I came across this in some RDF Stuart has written:
> >
> > <rdf:Description rdf:about="http://example.org/"
> >                   xml:base="http://example/org/base/">
> >    <rdf:value rdf:parseType="Literal">
> >      <a href="foo">link</a>
> >    </rdf:value>
> > </rdf:Description>
> >
> > I wasn't sure whether the xml:base had any effect on the href.
> No.
> Since
> 1) xml:base applies only to fields that contain URIs that XML
>    applications (RDF/XML here) know about.  RDF/XML doesn't do that
>    inside parsetype literal content.
> 2) the <a> has no namespace.
>    RDF/XML doesn't apply to non-namespaced elements anywhere
> 3) X/HTML don't use xml:base so even if it was an X/HTML fragment
>    and element, it wouldn't apply.
> Dave
Received on Monday, 15 April 2002 08:44:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:24:12 UTC