- From: Pat Hayes <phayes@ihmc.us>
- Date: Wed, 1 May 2013 09:45:39 -0500
- To: Ivan Herman <ivan@w3.org>
- Cc: W3C RDF WG <public-rdf-wg@w3.org>
On May 1, 2013, at 4:46 AM, Ivan Herman wrote: > A minor(?) remark: > > On May 1, 2013, at 03:24 , Pat Hayes <phayes@ihmc.us> wrote: > >> >> Proposed text changes: >> >> In Semantics >> >> <end of section 4 defining simple interpretations, add a paragraph:> >> >> Semantic extensions may impose further constraints upon interpretation mappings, by requiring some IRIs to refer in particular ways. For example, D-interpretations, described below, require some IRIs, understood as referring to datatypes. to have a fixed interpretation. Such an IRI is called a <em>rigid identifier</em>. >> >> <section 7, literlas and datatypes.> >> >> .... Datatypes are indicated by IRIs. >> >> Interpretations will vary according to which IRIs they recognize as denoting datatypes. We describe this using a parameter D on interpretations. where D is a set of IRIs that constitute the recognized datatype IRIs and which are considered to be rigid identifiers. If D includes any of the datatype IRIs listed in ///Concepts Section 5/// then they must be interpreted as described there, and the IRI rdf:plainLiteral must be interpreted to refer to the datatype defined in [RDF-PLAINLITERAL]. When other datatypes are used, all recognized IRIs [[must]] be treated as rigid identifiers, so that the mapping between a recognized IRI and the datatype it refers to must be specified unambiguously and treated as fixed during all RDF transformations or manipulations. >> >> ------------ >> >> In Concepts: >> >> 1.3 The Referent of an IRI >> >> The resource denoted by an IRI is also called its referent. For some IRIs with particular meanings, such as those identifying XSD datatypes, the referent is fixed by this specification. For all other IRIs, what exactly is denoted by any given IRI is not defined by this specification. Other specifications may fix IRI referents, or apply other constraints on what may be the referent of any IRI. >> >> >> 5.4 Datatype IRIs >> >> Datatypes are identified by IRIs. If D is a set of IRIs which are used to refer to datatypes, then the elements of D are called <em>recognized</em> datatype IRIs. Recognized IRIs are considered to be rigid identifiers. All semantic interpretations must conform to a fixed mapping between recognized IRIs and the datatypes they are specified to identify. All interpretations I [[must]] recognize the following IRIs with the mappings specified: >> >> I( http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral ) is the datatype rdf:XMLLiteral ; >> I( http://www.w3.org/1999/02/22-rdf-syntax-ns#HTM ) is the datatype rdf:HTML ; >> I( http://www.w3.org/2001/XMLSchema#xxx ) is the RDF-compatible XSD type named xsd:xxx, for every XSD type listed in section 5.1 >> >> Semantic extensions of RDF [[may]] recognize other datatype IRIs and impose fixed interpretations upon them, but they [[must not]] interpret a datatype IRI differently from its defining specification. > > (minor: #HTM -> #HTML above) > > As far as I know, the Concepts document does not talk about 'interpretations' at the moment. Yes. Probably this sentence should be transposed to Semantics. > So if we go along with this text that we should either define what it means or refer to the Sem document. (I am not sure what is the best approach.) Alternatively, we could be silent on what interpretation means in the Concepts document but then the last sentence should be modified. Yes, or simply removed. > > Also, I seem to remember that we said the XMLLiteral and the HTML datatypes are not required in RDF 1.1, but they are optional. But I may be wrong on that one... They are optional, but what isn't optional is to use those IRIs to mean something else. So if you use them, they have to mean what they are supposed to mean. We might need to add text to clarify this. Hmm, 15 mins before the telecon.... Pat > > Ivan > > > >> >> --------- >> >> I would also like to say something along the following lines, but I am not sure where it should go exactly. >> >> --------- >> >> Applications [[may]] give a warning message if they are unable to determine the referent of an IRI used in a typed literal, but they [[should not]] reject such RDF as either a syntactic or semantic error. >> >> Pat >> >> >> ------------------------------------------------------------ >> 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 >> >> >> >> >> >> > > > ---- > 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 Wednesday, 1 May 2013 14:46:06 UTC