Re: issue-118 proposed text

Hi Pat (and Peter),

When making the change in Concepts from datatype maps to datatype IRIs, I think it makes sense in section 5.5 ("The Value Corresponding to a Literal") to change:
[[
Let d be the datatype associated with the datatype IRI in the implementation-defined datatype map.
]]
to:
[[
Let d be the referent of the datatype IRI in the set of recognized datatype IRIs.
]]
…where "referent" and "recognized datatype IRIs" are defined terms.

Does that wording make sense to you?  Can you suggest improved wording?  Thanks.

Regards,
Dave
--
http://about.me/david_wood



On May 1, 2013, at 11:23, 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. 
> 
> <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 recognized, 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 have fixed referents, which [[must]] satisfy these conditions:
> 
> If the IRI 
> http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral
> is recognized then it refers to the datatype rdf:XMLLiteral ;
> If the IRI 
> http://www.w3.org/1999/02/22-rdf-syntax-ns#HTM
> ) is recognized then it refers to the datatype rdf:HTML ;
> If any IRI of the form  
> http://www.w3.org/2001/XMLSchema#xxx
> ) is recognized then it refers to 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 require them to refer to a fixed datatype. 
> 
> RDF processors are not required to recognize datatype IRIs. Any literal typed with an unrecognized IRI is treated just like an unknown IRI, i.e. as referring to an unknown thing. 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. 
> 
> 
> 
> 
> ------------------------------------------------------------
> 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
> 
> 
> 
> 
> 
>