New R2RML version ready for publication -- please review changes!

I have (much later than I promised -- sorry!) completed the R2RML update, and have prepared a version to be published as PR:

http://www.w3.org/2001/sw/rdb2rdf/r2rml/PR-r2rml-20120717/

Below is a list of changes -- if anything is a problem for anyone, then *please speak up immediately*.

The SotD needs to be reviewed by someone familiar with the process. The publication date (July 17) is speculative, as is the end of the review period (August 14), so these probably still need to be updated. We also need a timestamped URL for the implementation report I believe.

Here's the full diff (except SotD):
http://www.w3.org/2001/sw/rdb2rdf/r2rml/diffs/PR.html#index

A detailed list of changes follows below, with some justification etc.

Best,
Richard



List of changes:

1. new SotD
http://www.w3.org/2001/sw/rdb2rdf/r2rml/PR-r2rml-20120717/#status

2. Added "@prefix ex:" declaration to first example in 2.3
http://www.w3.org/2001/sw/rdb2rdf/r2rml/PR-r2rml-20120717/#example-simple

3. Added a class rr:TermMap to the list of R2RML classes in 4.1, as superclass of rr:(Subject|Predicate|Object|Graph)Map. Also added this to Appendix B.1. Note that classes are ignored in R2RML processing, hence no change of conformance.
http://www.w3.org/2001/sw/rdb2rdf/r2rml/PR-r2rml-20120717/#dfn-r2rml-classes
http://www.w3.org/2001/sw/rdb2rdf/r2rml/PR-r2rml-20120717/#class-index

4. Added a sentence in 4.1: "A resource should not be typed as an R2RML class if it does not meet the definition of that class." This is sort of obvious and legitimises the reporting of such cases as a warning in an R2RML validator.
http://www.w3.org/2001/sw/rdb2rdf/r2rml/PR-r2rml-20120717/#vocabulary

5. Removed a stray "and" in 4.3, see diff

6. Added an extra "sometimes" in a note in 5.2: "However, this approach may sometimes not be practical"
http://www.w3.org/2001/sw/rdb2rdf/r2rml/PR-r2rml-20120717/#r2rml-views

7. Switched the order of examples in 5.2, and changed the text for the unnamed column example. Old: "the following SELECT query is not a valid R2RML query"; new: "the following SELECT query SHOULD NOT be used". In the text above, a MUST NOT was changed to SHOULD NOT in a previous draft, and the example was not updated accordingly.
http://www.w3.org/2001/sw/rdb2rdf/r2rml/PR-r2rml-20120717/#dfn-sql-query

8. Changed a sentence in 6 to reflect the fact that we now allow multiple predicate maps and object maps per predicate-object map. Old text: "Each [predicate-object map] specifies a predicate-object pair that, together with the subject generated by the subject map, may form one RDF triple for each row." New text: "They specify pairs of predicate maps and object maps that, together with the subjects generated by the subject map, may form one or more RDF triples for each row."
http://www.w3.org/2001/sw/rdb2rdf/r2rml/PR-r2rml-20120717/#dfn-triples-map

9. Added a clause to the definition of string templates for rr:template: "There SHOULD be at least one pair of unescaped curly braces." This is sort of obvious, and legitimises reporting the lack of any "{COLUMN}" section in a string template as a warning in an RDF validator.
http://www.w3.org/2001/sw/rdb2rdf/r2rml/PR-r2rml-20120717/#dfn-string-template

10. Added a Note to Section 7.4 on rr:termType: "Constant-valued term maps are not considered as having a term type, and specifying rr:termType on these term maps has no effect. The type of the generated RDF term is determined directly by the value of rr:constant: If it is an IRI, then an IRI will be generated; if it is a literal, a literal will be generated."
http://www.w3.org/2001/sw/rdb2rdf/r2rml/PR-r2rml-20120717/#termtype

11. Fixed one of the example "quoted and escaped data values" in 7.7 from
DATE 2011-11-11
to
DATE '2011-11-11'
http://www.w3.org/2001/sw/rdb2rdf/r2rml/PR-r2rml-20120717/#dfn-quoted-data-value

12. Clarified a sentence in 8 (the resource may have further properties that are not in the rr namespace). Old: A join condition is represented by a resource that has exactly two properties"; New: "A join condition is represented by a resource that has exactly one value for each of the following two properties:"

13. Fix incorrect link for "IRI" in Appendix A
http://www.w3.org/2001/sw/rdb2rdf/r2rml/PR-r2rml-20120717/#terminology

14. Added more details to Appendix B.1 and B.2 in order to help implementers: The class table lists the minimum properties that a resource must have in order to be a member of the class. Some disjointness conditions are listed below the table. The property table now groups each rr:xxxMap property together with its rr:xxx shortcut in order to make the cardinalities more accurate, and highlights the four properties where the actual cardinalities depend on the presence of other properties. See here for details:
http://www.w3.org/2001/sw/rdb2rdf/r2rml/diffs/PR.html#index
http://www.w3.org/2001/sw/rdb2rdf/r2rml/PR-r2rml-20120717/#index

15. Updated Turtle URL from Team Submission to RDF WG Last Call version

16. Updated DM URL

Received on Friday, 13 July 2012 17:26:38 UTC