- From: Pat Hayes <phayes@ihmc.us>
- Date: Fri, 18 Nov 2011 10:31:37 -0600
- To: RDF Working Group WG <public-rdf-wg@w3.org>
- Cc: Peter Frederick Patel-Schneider <pfps@research.bell-labs.com>, Ivan Herman <ivan@w3.org>
(Coming to this issue late...) Seems to me that making XMLLIteral optional is a better way to proceed than keeping it non-optional but making it effectively vacuous. The only rationale for its being compulsory is now lost in time: it had to do with wanting RDF/XML to be "self-describing", as I recall. So making it be just a regular, and hence optional, datatype seems to be a sensible and simplifying thing to do. If it is a subdatatype of xsd:string, there seems to be little point in having it at all. Pat On Nov 17, 2011, at 2:51 AM, Ivan Herman wrote: > > On Nov 16, 2011, at 21:51 , Peter Frederick Patel-Schneider wrote: > >> This would still require any tool that does inference to correctly >> create XML infosets. > > That is correct. As Jeremy says, if XML Literal becomes optional, then this may still be o.k. > > Let me also add: we should realize that there *are* legitimate usages of XML Literals, even if they are in the long tail, so to say. We always referred to I18N usages, but that is not the only one. For example, if I want a literal that expresses a mathematical formula, then using the content markup of MathML is still one of the best solutions (though not the only one, one can use LaTeX formulae). Similarly, if I want to describe some 2D geometry in a literal, using SVG may be the most obvious approach. In all those cases I may want to compare, say, two math formulae whether they are identical, and referring to the infoset is a viable solution. > > I think that Peter's proposal goes a bit too far. Sorry Peter... > > Ivan > > > >> My proposal would eliminate that. >> >> peter >> >> >> From: Ivan Herman <ivan@w3.org> >> Subject: Re: ISSUE-13: a proposal for rdf:XMLLiteral >> Date: Wed, 16 Nov 2011 13:43:36 -0600 >> >>> Well, I try to keep a bit closer to what we have now. Here is my view... (To make things simpler at this point I do as if the xml literals had a root element. As Jerremy said this is not exactly true, but that can be folded in later) >>> >>> 1. The lexical space for XML literals are valid XML strings >>> 2. The value space for XML literals are XML Infosets.[1] >>> 3. The lexical to value mapping means parsing the XML string and build (some internal representation of) the infoset. >>> 4. RDF serialization SHOULD attempt to parse XML Literals without chaning the input strings. If this is not possible, the transformation they perform should have the same value, ie, yield the same XML Infosets. >>> >>> That is it. Of course, one possible way of implementing vale space check is to use canonicalization. But one can also imagine a comparison of some internal representation of a DOM tree, for example; the details are not covered by the RDF standards. >>> >>> Ivan >>> >>> [1] http://www.w3.org/TR/xml-infoset/ >>> >>> ---- >>> Ivan Herman >>> Tel:+31 641044153 >>> http://www.ivan-herman.net >>> >>> On 16 Nov 2011, at 18:39, Peter Frederick Patel-Schneider <pfps@research.bell-labs.com> wrote: >>> >>>> Here is my my proposal for rdf:XMLLiteral >>>> 1/ The datatype rdf:XMLLiteral is a sub-datatype of xsd:string. >>>> 2/ The lexical space of rdf:XMLLiteral is the set of finite-length >>>> sequences of characters. >>>> 3/ The value space of rdf:XMLLiteral is the set of finite-length >>>> sequences of characters. >>>> 4/ The lexical to value mapping for rdf:XMLLiteral is the identity >>>> mapping. >>>> 5/ RDF syntaxes may define a special syntax for rdf:XMLLiteral and the >>>> parse process for that RDF syntax may modify the surface form into some >>>> other lexical form. >>>> 6a/ In RDF/XML, parseType literal is one of these special syntaxes and >>>> the modification produces the canonical form. >>>> 6b/ In RDF/XML, parseType literal is one of these special syntaxes and >>>> the modification does not change the canonical form. >>>> >>>> >>>> I prefer 6a. >>>> >>>> >>>> peter >>>> >>> >> > > > ---- > Ivan Herman, W3C Semantic Web Activity Lead > Home: http://www.w3.org/People/Ivan/ > mobile: +31-641044153 > FOAF: http://www.ivan-herman.net/foaf.rdf > > > > > > > ------------------------------------------------------------ IHMC (850)434 8903 or (650)494 3973 40 South Alcaniz St. (850)202 4416 office Pensacola (850)202 4440 fax FL 32502 (850)291 0667 mobile phayesAT-SIGNihmc.us http://www.ihmc.us/users/phayes
Received on Friday, 18 November 2011 16:32:29 UTC