 |
 |
> From [log in to unmask] Thu Oct 17 13:50 MET 2002 > MIME-Version: 1.0 > Content-Transfer-Encoding: 7bit > X-Priority: 3 (Normal) > X-MSMail-Priority: Normal > X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 > Importance: Normal > Date: Thu, 17 Oct 2002 12:52:17 +0100 > From: Pete Johnston <[log in to unmask]> > Subject: Re: URIs in XML encoding of DC and RSS 2.0 > To: [log in to unmask] > > Roland, > > > what's more close to truth: > > > > "dcterms:URI encodes the element content as a URI" > > > > or > > > > "dcterms:URI assures the element content is a URI" > > > > In both cases i understand URI as defined by RFC2396. > > I am learning by experience that the "truth" in this territory is a > slippery creature, but I think the second statement is more accurate. > > e.g. if I define element content as having a type of xs:anyURI, a > validating parser signals an error for element content: > > http://purl.org/dc/a%b Isn't that a bug of the parser in view of http://www.w3.org/TR/xlink/#link-locators (item 1), which is called from http://www.w3.org/TR/xmlschema-2/ section 3.2.17.1 lexical space of anyURI ? > > The parser does _not_ transform it into http://purl.org/dc/a%25b > > If the element content is http://purl.org/dc/a%25b then the parser > accepts it as valid. > > (Well, this is the behaviour of Xerces 2.2.0) Seems we're up in thin air... Uhhh.... rs > > Pete > >