This document is also available in this non-normative format: insert: <a rel="alternate" href="csv2rdf.epub">ePub insert: </a>insert: </p>
insert: <p>
The English version of this specification is the only normative version. Non-normative insert: <a href="http://www.w3.org/Consortium/Translation/">translations insert: </a>may also be available. insert: </p>
This document defines the procedures and rules to be applied when converting tabular data into RDF. Tabular data may be complemented with metadata annotations that describe its structure, the meaning of its content and how it may form part of a collection of interrelated tabular data. This document specifies the effect of this metadata on the resulting RDF.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
The CSV on the Web Working Group was chartered to produce a recommendation "Access methods for CSV Metadata" as well as recommendations for "Metadata vocabulary for CSV data" and "Mapping mechanism to transforming CSV into various formats (e.g., RDF, JSON, or XML)". This document aims to satisfy the RDF variant of the mapping recommendation.
This document was published by the CSV on the Web Working Group as a Proposed Recommendation. If you wish to make comments regarding this document, please send them to insert: <a href="mailto:public-csv-wg@w3.org">public-csv-wg@w3.org insert: </a>( insert: <a href="mailto:public-csv-wg-request@w3.org?subject=subscribe">subscribe insert: </a>, insert: <a href="http://lists.w3.org/Archives/Public/public-csv-wg/">archives insert: </a>). All comments are welcome. insert: </p>
insert: <p>
Please see the Working Group's insert: <a href="http://www.w3.org/2013/csvw/implementation_report.html">implementation report insert: </a>. insert: </p>
insert: <p>
This document has been reviewed by insert: <abbr title="World Wide Web Consortium">W3C insert: </abbr>Members, by software developers, and by other insert: <abbr title="World Wide Web Consortium">W3C insert: </abbr>groups and interested parties, and is intended to become endorsed by the Director as a W3C Recommendation. The delete: <abbr title="World Wide Web Consortium">W3C delete: </abbr>Membership and other interested parties are invited to review the document and send comments to delete: <a rel="discussion" href="mailto:public-csv-wg@w3.org">public-csv-wg@w3.org delete: </a>( delete: <a href="mailto:public-csv-wg-request@w3.org?subject=subscribe">subscribe delete: </a>, delete: <a href="http://lists.w3.org/Archives/Public/public-csv-wg/">archives delete: </a>) through 15 December 2015. Advisory Committee Representatives should consult their delete: <a href="https://www.w3.org/2002/09/wbs/myQuestionnaires">WBS questionnaires delete: </a>. Note that substantive technical comments were expected during the Last Call review period that ended 30 October 2015. delete: </p>delete: <p>Please see the Working Group's delete: <a href="http://www.w3.org/2013/csvw/implementation_report.html">implementation report delete: </a>. delete: </p>delete: <p>Publication as a Proposed Recommendation does not imply endorsement by the delete: <abbr title="World Wide Web Consortium">W3C delete: </abbr>Membership. This It is a draft stable document and may be updated, replaced used as reference material or obsoleted by other documents at any time. It cited from another document. insert: <abbr title="World Wide Web Consortium">W3C insert: </abbr>'s role in making the Recommendation is inappropriate to cite this document as other than work in progress. draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web.
delete: <a href="#changes-since-the-working-draft-of-16-april-2015" class="tocxref">insert: <a class="tocxref" href="#changes-since-the-working-draft-of-16-april-2015"> C.2 Changes since the working draft of 16 April 2015
This document describes the processing of delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-tabular-data" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-tabular-data" class="externalDFN"> tabular data to create an RDF subject-predicate-object triples [ delete: <a class="bibref" href="#bib-rdf11-concepts">insert: <a href="#bib-rdf11-concepts" class="bibref"> rdf11-concepts ]. Since RDF is an abstract syntax , these triples delete: <em class="rfc2119" title="MAY">insert: <em title="MAY" class="rfc2119"> MAY be serialized in a concrete RDF syntax such as N-Triples [ delete: <a class="bibref" href="#bib-n-triples">insert: <a href="#bib-n-triples" class="bibref"> n-triples ], Turtle [ delete: <a class="bibref" href="#bib-turtle">insert: <a href="#bib-turtle" class="bibref"> turtle ], RDFa [ delete: <a class="bibref" href="#bib-rdfa-primer">insert: <a href="#bib-rdfa-primer" class="bibref"> rdfa-primer ], JSON-LD [ delete: <a class="bibref" href="#bib-json-ld">insert: <a href="#bib-json-ld" class="bibref"> json-ld ], or TriG [ delete: <a class="bibref" href="#bib-trig">insert: <a href="#bib-trig" class="bibref"> trig ]. The RDF serializations offered by a conversion application is implementation defined.
The [ delete: <a class="bibref" href="#bib-tabular-data-model">insert: <a href="#bib-tabular-data-model" class="bibref"> tabular-data-model ] defines an delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-annotated-tabular-data-model" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-annotated-tabular-data-model" class="externalDFN"> annotated tabular data model consisting of delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-table" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-table" class="externalDFN"> tables , delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-column" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-column" class="externalDFN"> columns , delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-row" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-row" class="externalDFN"> rows , and delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell" class="externalDFN"> cells , enriched with delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-annotations" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-annotation" class="externalDFN"> annotations that describe the structure of the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-tabular-data" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-tabular-data" class="externalDFN"> tabular data and the meaning of its content. A delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-group-of-tables" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-group-of-tables" class="externalDFN"> group of tables is a collection of delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-table" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-table" class="externalDFN"> tables published as a single atomic unit.
The conversion procedure described in this specification operates on the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-annotated-tabular-data-model" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-annotated-tabular-data-model" class="externalDFN"> annotated tabular data model . This specification does not specify the processes needed to convert CSV-encoded data into tabular data form. Please refer to [ delete: <a class="bibref" href="#bib-tabular-data-model">insert: <a href="#bib-tabular-data-model" class="bibref"> tabular-data-model ] for details of delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#parsing">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#parsing"> parsing tabular data .
Conversion applications delete: <em class="rfc2119" title="MUST">insert: <em title="MUST" class="rfc2119"> MUST provide at least two modes of operation: delete: <a href="#dfn-standard-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-standard-mode"> standard and delete: <a href="#dfn-minimal-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-minimal-mode"> minimal .
delete: <dfn data-dfn-type="dfn" id="dfn-standard-mode">insert: <dfn id="dfn-standard-mode" data-dfn-type="dfn"> Standard mode conversion frames the information gleaned from the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell" class="externalDFN"> cells of the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-tabular-data" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-tabular-data" class="externalDFN"> tabular data with details of the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-row" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-row" class="externalDFN"> rows , delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-table" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-table" class="externalDFN"> tables , and a delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-group-of-tables" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-group-of-tables" class="externalDFN"> group of tables within which that information is provided.
delete: <dfn data-dfn-type="dfn" id="dfn-minimal-mode">insert: <dfn id="dfn-minimal-mode" data-dfn-type="dfn"> Minimal mode conversion includes only the information gleaned from the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell" class="externalDFN"> cells of the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-tabular-data" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-tabular-data" class="externalDFN"> tabular data .
delete: <a href="#dfn-standard-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-standard-mode"> Standard and delete: <a href="#dfn-minimal-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-minimal-mode"> minimal conversion are described normatively below .
Conversion applications delete: <em class="rfc2119" title="MAY">insert: <em title="MAY" class="rfc2119"> MAY offer additional implementation specific conversion modes.
delete: <a href="http://www.w3.org/TR/2015/PR-tabular-metadata-20151117/#dfn-transformation-definition" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-metadata-20151217/#dfn-transformation-definition" class="externalDFN"> Transformation definitions , as defined in [ delete: <a class="bibref" href="#bib-tabular-metadata">insert: <a href="#bib-tabular-metadata" class="bibref"> tabular-metadata ] delete: <em class="rfc2119" title="MAY">insert: <em title="MAY" class="rfc2119"> MAY be used to specify how delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-tabular-data" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-tabular-data" class="externalDFN"> tabular data can be transformed into another format using a script or template. Such delete: <a href="http://www.w3.org/TR/2015/PR-tabular-metadata-20151117/#dfn-transformation-definition" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-metadata-20151217/#dfn-transformation-definition" class="externalDFN"> transformation definitions delete: <em class="rfc2119" title="MAY">insert: <em title="MAY" class="rfc2119"> MAY use the RDF output described in this specification as input.
There is no requirement on conversion applications to check the semantic consistency of the data during the conversion, nor to validate the triples against RDF schema. Downstream applications delete: <em class="rfc2119" title="SHOULD">insert: <em title="SHOULD" class="rfc2119"> SHOULD be aware of the potential for inconsistencies and take appropriate action.
As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.
The key words MAY , MUST , and SHOULD are to be interpreted as described in [ delete: <a class="bibref" href="#bib-RFC2119">insert: <a href="#bib-RFC2119" class="bibref"> RFC2119 ].
delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-tabular-data" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-tabular-data" class="externalDFN"> Tabular data delete: <em class="rfc2119" title="MUST">insert: <em title="MUST" class="rfc2119"> MUST conform to the description from [ delete: <a class="bibref" href="#bib-tabular-data-model">insert: <a href="#bib-tabular-data-model" class="bibref"> tabular-data-model ]. In particular note that each delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-row" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-row" class="externalDFN"> row delete: <em class="rfc2119" title="MUST">insert: <em title="MUST" class="rfc2119"> MUST contain the same number of delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell" class="externalDFN"> cells (although some of these delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell" class="externalDFN"> cells may be empty).
Not all CSV-encoded data can be parsed into a tabular data model. An algorithm for parsing CSV-based files is described in [ delete: <a class="bibref" href="#bib-tabular-data-model">insert: <a href="#bib-tabular-data-model" class="bibref"> tabular-data-model ].
This specification makes use of the delete: <dfn data-dfn-type="dfn" id="dfn-compact-iri-syntax">insert: <dfn id="dfn-compact-iri-syntax" data-dfn-type="dfn"> compact IRI Syntax ; please refer to the Compact IRIs from [ delete: <a class="bibref" href="#bib-json-ld">insert: <a href="#bib-json-ld" class="bibref"> json-ld ].
This specification makes use of the following namespaces:
The following typographic conventions are used in this specification:
markup
Markup (elements, attributes, properties), machine processable values (string, characters, media types), property name, or a file name is in red-orange monospace font.
variable
A variable in pseudo-code or in an algorithm description is in italics.
A references to a definition in this document , when the reference itself is also a markup, is underlined, red-orange monospace font, and is also an active link to the definition itself.
A reference to a definition in another document , when the reference itself is also a markup, is underlined, in italics red-orange monospace font, and is also an active link to the definition itself.
Notes are in light green boxes with a green left border and with a "Note" header in green. Notes are normative or informative depending on the whether they are in a normative or informative section, respectively.
Example 1
Examples are in light khaki boxes, with khaki left border, and with a numbered "Example" header in khaki. Examples are always informative. The content of the example is in monospace font and may be syntax colored.
The procedures for converting delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-tabular-data" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-tabular-data" class="externalDFN"> tabular data into RDF are described below for both delete: <a href="#dfn-standard-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-standard-mode"> standard and delete: <a href="#dfn-minimal-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-minimal-mode"> minimal modes.
delete: <dfn data-dfn-type="dfn" id="dfn-about-url">insert: <dfn id="dfn-about-url" data-dfn-type="dfn"> about URL
The delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-about-url" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-about-url" class="externalDFN"> about URL annotation on the current delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell" class="externalDFN"> cell . As defined in [ delete: <a class="bibref" href="#bib-tabular-data-model">insert: <a href="#bib-tabular-data-model" class="bibref"> tabular-data-model ].
The delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-annotated-table" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-annotated-table" class="externalDFN"> annotated table is defined in [ delete: <a class="bibref" href="#bib-tabular-data-model">insert: <a href="#bib-tabular-data-model" class="bibref"> tabular-data-model ] as describing a particular delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-table" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-table" class="externalDFN"> table and its annotations.
A blank node is defined in [ delete: <a class="bibref" href="#bib-rdf11-concepts">insert: <a href="#bib-rdf11-concepts" class="bibref"> rdf11-concepts ] as an RDF Term disjoint from IRIs or delete: <a href="#dfn-literal-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-literal-node"> literals .
delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-errors" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-errors" class="externalDFN"> Cell errors are defined in [ delete: <a class="bibref" href="#bib-tabular-data-model">insert: <a href="#bib-tabular-data-model" class="bibref"> tabular-data-model ] as a (possibly empty) list of validation errors generated while parsing the literal content of a delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> cell to generate the delete: <a data-lt="cell value" href="#dfn-cell-value" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell-value" data-lt="cell value"> semantic value .
delete: <dfn data-dfn-type="dfn" id="dfn-cell-value">insert: <dfn id="dfn-cell-value" data-dfn-type="dfn"> cell value
A delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-value" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-value" class="externalDFN"> cell value is defined in [ delete: <a class="bibref" href="#bib-tabular-data-model">insert: <a href="#bib-tabular-data-model" class="bibref"> tabular-data-model ] as the semantic value of the delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> cell ; this delete: <em class="rfc2119" title="MAY">insert: <em title="MAY" class="rfc2119"> MAY be null or a sequence of values.
A delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-column" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-column" class="externalDFN"> column is defined in [ delete: <a class="bibref" href="#bib-tabular-data-model">insert: <a href="#bib-tabular-data-model" class="bibref"> tabular-data-model ] as a vertical arrangement of delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> cells within a delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> table .
delete: <dfn data-dfn-type="dfn" id="dfn-group-of-tables">insert: <dfn id="dfn-group-of-tables" data-dfn-type="dfn"> group of tables
A delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-group-of-tables" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-group-of-tables" class="externalDFN"> group of tables is defined in [ delete: <a class="bibref" href="#bib-tabular-data-model">insert: <a href="#bib-tabular-data-model" class="bibref"> tabular-data-model ] as comprising a set of delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> annotated tables and a set of annotations that relate to that group.
delete: <dfn data-dfn-type="dfn" id="dfn-group-of-tables-identifier">insert: <dfn id="dfn-group-of-tables-identifier" data-dfn-type="dfn"> group of tables identifier
The group of tables identifier is the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-table-group-id" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-table-group-id" class="externalDFN"> id annotation on a delete: <a href="#dfn-group-of-tables" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-group-of-tables"> group of tables . As defined in [ delete: <a class="bibref" href="#bib-tabular-data-model">insert: <a href="#bib-tabular-data-model" class="bibref"> tabular-data-model ].
A literal node is defined in [ delete: <a class="bibref" href="#bib-rdf11-concepts">insert: <a href="#bib-rdf11-concepts" class="bibref"> rdf11-concepts ] as a delete: <a href="#dfn-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-node"> node within an RDF graph that provides values such as strings, numbers, and dates.
A node is defined in [ delete: <a class="bibref" href="#bib-rdf11-concepts">insert: <a href="#bib-rdf11-concepts" class="bibref"> rdf11-concepts ] as a subject or an object of an RDF triple. When in subject position, it can be either a delete: <a href="#dfn-blank-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-blank-node"> blank node or identified with a URL; when in object position, it can be a delete: <a href="#dfn-blank-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-blank-node"> blank node , a delete: <a href="#dfn-literal-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-literal-node"> literal , or identified with a URL.
Core annotations are listed in [ delete: <a class="bibref" href="#bib-tabular-data-model">insert: <a href="#bib-tabular-data-model" class="bibref"> tabular-data-model ]; delete: <a data-lt="group of tables" href="#dfn-group-of-tables" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-group-of-tables" data-lt="group of tables"> groups of tables and delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> tables may also have other annotations that are not defined in that specification; these are known as delete: <a href="#dfn-non-core-annotations" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-non-core-annotations"> non-core annotations .
A list of delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-notes" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-table-notes" class="externalDFN"> notes , as defined in [ delete: <a class="bibref" href="#bib-tabular-data-model">insert: <a href="#bib-tabular-data-model" class="bibref"> tabular-data-model ], attached to an delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> annotated table or delete: <a href="#dfn-group-of-tables" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-group-of-tables"> group of tables using the notes property. This may be an empty list.
A predicate is defined in [ delete: <a class="bibref" href="#bib-rdf11-concepts">insert: <a href="#bib-rdf11-concepts" class="bibref"> rdf11-concepts ] as an IRI that denotes the property used to relate delete: <a href="#dfn-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-node"> nodes within an RDF triple.
delete: <dfn data-dfn-type="dfn" id="dfn-prefixed-name">insert: <dfn id="dfn-prefixed-name" data-dfn-type="dfn"> prefixed name
A prefixed name is an abbreviation for a URI, in the syntax prefix : name . See delete: <a href="http://www.w3.org/TR/2015/PR-tabular-metadata-20151117/#names-of-common-properties">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-metadata-20151217/#names-of-common-properties"> Names of Common Properties in [ delete: <a class="bibref" href="#bib-tabular-metadata">insert: <a href="#bib-tabular-metadata" class="bibref"> tabular-metadata ] for information on expansion.
The delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-row" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-row" class="externalDFN"> row is defined in [ delete: <a class="bibref" href="#bib-tabular-data-model">insert: <a href="#bib-tabular-data-model" class="bibref"> tabular-data-model ] as a horizontal arrangement of delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> cells within a delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> table .
delete: <dfn data-dfn-type="dfn" id="dfn-row-number">insert: <dfn id="dfn-row-number" data-dfn-type="dfn"> row number
A delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-row-number" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-row-number" class="externalDFN"> row number is defined in [ delete: <a class="bibref" href="#bib-tabular-data-model">insert: <a href="#bib-tabular-data-model" class="bibref"> tabular-data-model ] as the position of the delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row within the delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> table , starting from 1.
delete: <dfn data-dfn-type="dfn" id="dfn-row-source-number">insert: <dfn id="dfn-row-source-number" data-dfn-type="dfn"> row source number
A delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-row-source-number" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-row-source-number" class="externalDFN"> row source number is defined in [ delete: <a class="bibref" href="#bib-tabular-data-model">insert: <a href="#bib-tabular-data-model" class="bibref"> tabular-data-model ] as the position of the delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row within the source delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-tabular-data-files" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-tabular-data-file" class="externalDFN"> tabular data file . Provision of the delete: <a href="#dfn-row-source-number" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row-source-number"> row source number is dependent on parsing applications and may be reported as null .
Within this algorithm, a delete: <a href="#dfn-subject" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-subject"> subject is the resource that the value of a given delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> cell refers to. This may be specified using delete: <a href="#dfn-about-url" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-about-url"> about URL .
The table identifier is the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-table-id" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-table-id" class="externalDFN"> id annotation on an delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> annotated table . As defined in [ delete: <a class="bibref" href="#bib-tabular-data-model">insert: <a href="#bib-tabular-data-model" class="bibref"> tabular-data-model ].
delete: <dfn data-dfn-type="dfn" id="dfn-tabular-data-mapping">insert: <dfn id="dfn-tabular-data-mapping" data-dfn-type="dfn"> tabular data mapping
The mapping from tabular data to RDF, as defined by this Recommendation.
delete: <dfn data-dfn-type="dfn" id="dfn-value-url">insert: <dfn id="dfn-value-url" data-dfn-type="dfn"> value URL
The delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-value-url" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-value-url" class="externalDFN"> value URL annotation on the current delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell" class="externalDFN"> cell . As defined in [ delete: <a class="bibref" href="#bib-tabular-data-model">insert: <a href="#bib-tabular-data-model" class="bibref"> tabular-data-model ].
A conformant RDF conversion application delete: <em class="rfc2119" title="MUST">insert: <em title="MUST" class="rfc2119"> MUST emit triples conforming to those described in this algorithm according to the chosen mode of conversion: delete: <a href="#dfn-standard-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-standard-mode"> standard or delete: <a href="#dfn-minimal-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-minimal-mode"> minimal .
Unless specified otherwise, the steps in the algorithm defined herein apply to both delete: <a href="#dfn-standard-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-standard-mode"> standard and delete: <a href="#dfn-minimal-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-minimal-mode"> minimal modes.
Where an delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> annotated table is defined in isolation (e.g. in the absence of a delete: <a href="#dfn-group-of-tables" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-group-of-tables"> group of tables ), a default delete: <a href="#dfn-group-of-tables" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-group-of-tables"> group of tables is provided with a single delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-table-group-tables" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-table-group-tables" class="externalDFN"> tables annotation that refers to the given delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> table .
The [ delete: <a class="bibref" href="#bib-tabular-data-model">insert: <a href="#bib-tabular-data-model" class="bibref"> tabular-data-model ] specifies that string values within delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-tabular-data" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-tabular-data" class="externalDFN"> tabular data (such as delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-column-titles" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-column-titles" class="externalDFN"> column titles or delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-string-value" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-string-value" class="externalDFN"> cell string values ) delete: <em class="rfc2119" title="MUST">insert: <em title="MUST" class="rfc2119"> MUST contain only Unicode characters. No Unicode normalization (as specified in [ delete: <a class="bibref" href="#bib-UAX15">insert: <a href="#bib-UAX15" class="bibref"> UAX15 ]) is applied to these string values during the conversion to RDF.
If a CSV file is originally encoded as UTF-8, it should not go through Unicode normalization during parsing, nor in conversion to RDF. This can result in RDF literals that are not in Normal Form C as they should be according to [ delete: <a class="bibref" href="#bib-rdf11-concepts">insert: <a href="#bib-rdf11-concepts" class="bibref"> rdf11-concepts ].
In delete: <a href="#dfn-standard-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-standard-mode"> standard mode only, establish a new delete: <a href="#dfn-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-node"> node G . If the delete: <a href="#dfn-group-of-tables" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-group-of-tables"> group of tables has an delete: <a data-lt="group of tables identifier" href="#dfn-group-of-tables-identifier" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-group-of-tables-identifier" data-lt="group of tables identifier"> identifier then delete: <a href="#dfn-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-node"> node G delete: <em class="rfc2119" title="MUST">insert: <em title="MUST" class="rfc2119"> MUST be identified accordingly; else if delete: <a data-lt="group of tables identifier" href="#dfn-group-of-tables-identifier" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-group-of-tables-identifier" data-lt="group of tables identifier"> identifier is null , then delete: <a href="#dfn-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-node"> node G delete: <em class="rfc2119" title="MUST">insert: <em title="MUST" class="rfc2119"> MUST be a new delete: <a href="#dfn-blank-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-blank-node"> blank node .
In delete: <a href="#dfn-standard-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-standard-mode"> standard mode only, specify the type of delete: <a href="#dfn-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-node"> node G as csvw:TableGroup ; emit the following triple:
In delete: <a href="#dfn-standard-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-standard-mode"> standard mode only, emit the triples generated by running the algorithm specified in section 6. JSON-LD to RDF over any delete: <a href="#dfn-notes" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-notes"> notes and delete: <a href="#dfn-non-core-annotations" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-non-core-annotations"> non-core annotations specified for the delete: <a href="#dfn-group-of-tables" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-group-of-tables"> group of tables , with delete: <a href="#dfn-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-node"> node G as an initial subject , the delete: <a href="#dfn-notes" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-notes"> notes or delete: <a href="#dfn-non-core-annotations" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-non-core-annotations"> non-core annotation as property , and the value of the delete: <a href="#dfn-notes" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-notes"> notes or delete: <a href="#dfn-non-core-annotations" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-non-core-annotations"> non-core annotation as value .
For each delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> table where the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-table-suppress-output" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-table-suppress-output" class="externalDFN"> suppress output annotation is false :
In delete: <a href="#dfn-standard-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-standard-mode"> standard mode only, establish a new delete: <a href="#dfn-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-node"> node T which represents the current delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> table .
If the delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> table has an delete: <a data-lt="table identifier" href="#dfn-table-identifier" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-table-identifier" data-lt="table identifier"> identifier then delete: <a href="#dfn-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-node"> node T delete: <em class="rfc2119" title="MUST">insert: <em title="MUST" class="rfc2119"> MUST be identified accordingly; else if delete: <a data-lt="table identifier" href="#dfn-table-identifier" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-table-identifier" data-lt="table identifier"> identifier is null , then delete: <a href="#dfn-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-node"> node T delete: <em class="rfc2119" title="MUST">insert: <em title="MUST" class="rfc2119"> MUST be a new delete: <a href="#dfn-blank-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-blank-node"> blank node .
In delete: <a href="#dfn-standard-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-standard-mode"> standard mode only, relate the delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> table to the delete: <a href="#dfn-group-of-tables" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-group-of-tables"> group of tables ; emit the following triple:
In delete: <a href="#dfn-standard-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-standard-mode"> standard mode only, specify the type of delete: <a href="#dfn-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-node"> node T as csvw:Table ; emit the following triple:
In delete: <a href="#dfn-standard-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-standard-mode"> standard mode only, specify the source tabular data file URL for the current delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> table based on the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-url" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-table-url" class="externalDFN"> url annotation; emit the following triple:
In delete: <a href="#dfn-standard-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-standard-mode"> standard mode only, specify the type of delete: <a href="#dfn-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-node"> node R as csvw:Row ; emit the following triple:
In delete: <a href="#dfn-standard-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-standard-mode"> standard mode only, specify the delete: <a href="#dfn-row-number" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row-number"> row number n for the delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row ; emit the following triple:
a delete: <a href="#dfn-literal-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-literal-node"> literal n ; specified with datatype IRI xsd:integer
In delete: <a href="#dfn-standard-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-standard-mode"> standard mode only, specify the delete: <a href="#dfn-row-source-number" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row-source-number"> row source number n source for the delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row within the source tabular data file URL using a fragment-identifier as specified in [ delete: <a class="bibref" href="#bib-RFC7111">insert: <a href="#bib-RFC7111" class="bibref"> RFC7111 ]; if delete: <a href="#dfn-row-source-number" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row-source-number"> row source number is not null , emit the following triple:
a delete: <a href="#dfn-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-node"> node identified by URL #row= n source
In delete: <a href="#dfn-standard-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-standard-mode"> standard mode only, if delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-row-titles" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-row-titles" class="externalDFN"> row titles is not null , insert any delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-row-titles" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-row-titles" class="externalDFN"> titles specified for the delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row . For each value, t v , of the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-row-titles" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-row-titles" class="externalDFN"> row titles annotation, emit the following triple:
a delete: <a href="#dfn-literal-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-literal-node"> literal t v ; specified with the the appropriate language tag (as defined in [ delete: <a class="bibref" href="#bib-rdf11-concepts">insert: <a href="#bib-rdf11-concepts" class="bibref"> rdf11-concepts ]) for that delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-row-titles" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-row-titles" class="externalDFN"> row title annotation value
In delete: <a href="#dfn-standard-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-standard-mode"> standard mode only, emit the triples generated by running the algorithm specified in section 6. JSON-LD to RDF over any delete: <a href="#dfn-non-core-annotations" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-non-core-annotations"> non-core annotations specified for the delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row , with delete: <a href="#dfn-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-node"> node R as an initial subject , the delete: <a href="#dfn-non-core-annotations" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-non-core-annotations"> non-core annotation as property , and the value of the delete: <a href="#dfn-non-core-annotations" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-non-core-annotations"> non-core annotation as value .
Establish a new delete: <a href="#dfn-blank-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-blank-node"> blank node S def to be used as the default subject for delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> cells where delete: <a href="#dfn-about-url" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-about-url"> about URL is undefined.
A delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row delete: <em class="rfc2119" title="MAY">insert: <em title="MAY" class="rfc2119"> MAY describe multiple interrelated delete: <a href="#dfn-subject" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-subject"> subjects ; where the delete: <a href="#dfn-value-url" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-value-url"> value URL annotation on one delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> cell matches the delete: <a href="#dfn-about-url" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-about-url"> about URL annotation on another delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> cell in the same delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row .
For each delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> cell in the current delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row where the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-column-suppress-output" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-column-suppress-output" class="externalDFN"> suppress output annotation for the delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> column associated with that delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> cell is false :
Establish a delete: <a href="#dfn-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-node"> node S from delete: <a href="#dfn-about-url" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-about-url"> about URL if set, or from S def otherwise as the current delete: <a href="#dfn-subject" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-subject"> subject .
In delete: <a href="#dfn-standard-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-standard-mode"> standard mode only, relate the current delete: <a href="#dfn-subject" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-subject"> subject to the current delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row ; emit the following triple:
If the value of delete: <a href="#dfn-property-url" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-property-url"> property URL for the delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> cell is not null , then predicate P takes the value of delete: <a href="#dfn-property-url" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-property-url"> property URL .
Else, delete: <a href="#dfn-predicate" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-predicate"> predicate P is constructed by appending the value of the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-name" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-column-name" class="externalDFN"> name annotation for the delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> column associated with the delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> cell to the the tabular data file URL as a fragment identifier.
If the delete: <a href="#dfn-value-url" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-value-url"> value URL for the current delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> cell is not null , then delete: <a href="#dfn-value-url" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-value-url"> value URL identifies a delete: <a href="#dfn-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-node"> node V url that is related the current delete: <a href="#dfn-subject" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-subject"> subject using the delete: <a href="#dfn-predicate" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-predicate"> predicate P ; emit the following triple:
Else, if the delete: <a href="#dfn-cell-value" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell-value"> cell value is a delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-list" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-value-list" class="externalDFN"> list and the delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> cell delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-ordered" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-ordered" class="externalDFN"> ordered annotation is true , then the delete: <a href="#dfn-cell-value" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell-value"> cell value provides an ordered sequence of delete: <a href="#dfn-literal-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-literal-node"> literal nodes for inclusion within the RDF output using an instance of rdf:List V list as defined in [ delete: <a class="bibref" href="#bib-rdf-schema">insert: <a href="#bib-rdf-schema" class="bibref"> rdf-schema ]. This instance is related to the delete: <a href="#dfn-subject" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-subject"> subject using the delete: <a href="#dfn-predicate" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-predicate"> predicate P ; emit the triples defining list V list plus the following triple:
delete: <a href="#dfn-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-node"> node V list
Else, if the delete: <a href="#dfn-cell-value" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell-value"> cell value is a delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-list" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-value-list" class="externalDFN"> list , then the delete: <a href="#dfn-cell-value" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell-value"> cell value provides an unordered sequence of delete: <a href="#dfn-literal-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-literal-node"> literal nodes for inclusion within the RDF output, each of which is related to the delete: <a href="#dfn-subject" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-subject"> subject using the delete: <a href="#dfn-predicate" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-predicate"> predicate P . For each value provided in the sequence, add a delete: <a href="#dfn-literal-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-literal-node"> literal node V literal ; emit the following triple:
Else, if the delete: <a href="#dfn-cell-value" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell-value"> cell value is not null , then the delete: <a href="#dfn-cell-value" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell-value"> cell value provides a single delete: <a href="#dfn-literal-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-literal-node"> literal node V literal for inclusion within the RDF output that is related the current delete: <a href="#dfn-subject" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-subject"> subject using the delete: <a href="#dfn-predicate" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-predicate"> predicate P ; emit the following triple:
In the case when a delete: <a href="#dfn-cell-value" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell-value"> cell value does not have a delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-value-datatype" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-value-datatype" class="externalDFN"> datatype , the conversion delete: <em class="rfc2119" title="SHOULD">insert: <em title="SHOULD" class="rfc2119"> SHOULD default to string .
In the case where a sequence of values is provided, each value in the list has its own delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-value-datatype" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-value-datatype" class="externalDFN"> datatype ; the datatype may be different for different items in the sequence.
delete: <a href="#dfn-cell-value" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell-value"> Cell values are expressed in the RDF output according to the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-value-datatype" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-value-datatype" class="externalDFN"> cell value's datatype . The relationship between the value of the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-value-datatype" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-value-datatype" class="externalDFN"> cell value's datatype and the datatype IRI used in the RDF output is as follows:
if the datatype's delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-datatype-id" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-datatype-id" class="externalDFN"> id annotation is not null , then its value delete: <em class="rfc2119" title="MUST">insert: <em title="MUST" class="rfc2119"> MUST be used as the RDF datatype IRI ;
else, the datatype's delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-base" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-datatype-base" class="externalDFN"> base annotation value delete: <em class="rfc2119" title="MUST">insert: <em title="MUST" class="rfc2119"> MUST be mapped to the RDF datatype IRI as shown below:
A datatype's delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-format" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-datatype-format" class="externalDFN"> format annotation is irrelevant to the conversion procedure defined in this specification; the delete: <a href="#dfn-cell-value" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell-value"> cell value has already been parsed from the contents of the delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> cell according to the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-format" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-datatype-format" class="externalDFN"> format annotation.
delete: <a href="#dfn-cell-errors" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell-errors"> Cell errors delete: <em class="rfc2119" title="MUST">insert: <em title="MUST" class="rfc2119"> MUST be recorded by applications where the contents of a delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> cell cannot be parsed or validated (see delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#parsing-cells">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#parsing-cells"> Parsing Cells and delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#validating-tables">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#validating-tables"> Validating Tables in [ delete: <a class="bibref" href="#bib-tabular-data-model">insert: <a href="#bib-tabular-data-model" class="bibref"> tabular-data-model ] respectively). In cases where delete: <a href="#dfn-cell-errors" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell-errors"> cell errors are recorded, applications may attempt to determine the appropriate RDF datatype IRI during the subsequent conversion process according to local rules.
In the case of rdf:langString , the appropriate language tag (as defined in [ delete: <a class="bibref" href="#bib-rdf11-concepts">insert: <a href="#bib-rdf11-concepts" class="bibref"> rdf11-concepts ]) delete: <em class="rfc2119" title="MUST">insert: <em title="MUST" class="rfc2119"> MUST be provided for the string, based on the value of delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-language" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-value-language" class="externalDFN"> cell value's language . (See section on Graph Literals in [ delete: <a class="bibref" href="#bib-rdf11-concepts">insert: <a href="#bib-rdf11-concepts" class="bibref"> rdf11-concepts ] for further details on language tagged literals.)
According to [ delete: <a class="bibref" href="#bib-rdf11-concepts">insert: <a href="#bib-rdf11-concepts" class="bibref"> rdf11-concepts ] language tags cannot be combined with other xsd datatypes. If a cell has any datatype other than string , the value of lang delete: <em class="rfc2119" title="MUST">insert: <em title="MUST" class="rfc2119"> MUST be ignored. Also, all literals have a datatype; however, specific serializations, like [ delete: <a class="bibref" href="#bib-turtle">insert: <a href="#bib-turtle" class="bibref"> turtle ], delete: <em class="rfc2119" title="MAY">insert: <em title="MAY" class="rfc2119"> MAY provide a special syntax for literals with datatype xsd:string or rdf:langString .
In addition to the namespaces defined above , the following namespace is used in this section:
prov :
http://www.w3.org/ns/prov#
Conversion applications delete: <em class="rfc2119" title="MAY">insert: <em title="MAY" class="rfc2119"> MAY include provenance information in the RDF output describing how and when the output was created; e.g., using terms from the PROV Ontology [ delete: <a class="bibref" href="#bib-prov-o">insert: <a href="#bib-prov-o" class="bibref"> prov-o ]. Information that may be of interest to downstream applications includes:
the source tabular data file;
the metadata description file(s) used;
when the conversion to RDF occurred; and
the conversion application used.
In order to facilitate providing such information, this specification introduces two instances of prov:Role :
csvw:csvEncodedTabularData
Defines the role of the source tabular data file.
csvw:tabularMetadata
Defines the role of the metadata description file.
An illustrative example of provenance information is provided below in [ delete: <a class="bibref" href="#bib-turtle">insert: <a href="#bib-turtle" class="bibref"> turtle ] syntax, the conversion application used is identified as http://example.org/my-csv2rdf-application :
Example 2 insert: <span style="text-transform: none"> : http://example.org/prov-example.ttl insert: </span>
This section defines a mechanism for transforming the [ delete: <a class="bibref" href="#bib-json-ld">insert: <a href="#bib-json-ld" class="bibref"> json-ld ] delete: <a href="http://www.w3.org/TR/2015/PR-tabular-metadata-20151117/#json-ld-dialect">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-metadata-20151217/#json-ld-dialect"> dialect used for delete: <a href="#dfn-non-core-annotations" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-non-core-annotations"> non-core annotations and delete: <a href="#dfn-notes" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-notes"> notes originating from the processing of metadata (as defined in [ delete: <a class="bibref" href="#bib-tabular-metadata">insert: <a href="#bib-tabular-metadata" class="bibref"> tabular-metadata ]) into RDF in a manner consistent with the Deserialize JSON-LD to RDF Algorithm defined in [ delete: <a class="bibref" href="#bib-json-ld-api">insert: <a href="#bib-json-ld-api" class="bibref"> json-ld-api ]. Converters delete: <em class="rfc2119" title="MAY">insert: <em title="MAY" class="rfc2119"> MAY use any algorithm which results in equivalent triples.
Conversion applications may have other means to create delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> annotated tables , e.g. through some application specific APIs. In such cases the exact format for non-core annotations or notes may be different. Specifications for such annotation processes should specify how these annotations are converted into RDF.
Given a subject , property and value in delete: <a href="http://www.w3.org/TR/2015/PR-tabular-metadata-20151117/#normalization" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-metadata-20151217/#normalization" class="externalDFN"> normalized form:
Property is a term defined in the [ delete: <a class="bibref" href="#bib-csvw-context">insert: <a href="#bib-csvw-context" class="bibref"> csvw-context ], a delete: <a href="#dfn-prefixed-name" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-prefixed-name"> prefixed name , or an absolute URL; expand to an absolute URL by replacing a term with the URI from the term definition in [ delete: <a class="bibref" href="#bib-csvw-context">insert: <a href="#bib-csvw-context" class="bibref"> csvw-context ] or a delete: <a href="#dfn-prefixed-name" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-prefixed-name"> prefixed name as described in delete: <a href="http://www.w3.org/TR/2015/PR-tabular-metadata-20151117/#names-of-common-properties">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-metadata-20151217/#names-of-common-properties"> Names of Common Properties in [ delete: <a class="bibref" href="#bib-tabular-metadata">insert: <a href="#bib-tabular-metadata" class="bibref"> tabular-metadata ].
If value is an array, generate RDF by running this algorithm using subject , property using each array member as value .
If value is an object containing @value , create an RDF Literal lit using the string value of @value and language from @language , or datatype from @type if present, expanding @type as necessary using the procedure outlined for property , and emit the following triple:
If neither @language nor @type is present, the literal lit has the datatype xsd:string .
Else, if value is an object:
Establish a new delete: <a href="#dfn-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-node"> node S that is identified with the value of @id if defined, or else as a delete: <a href="#dfn-blank-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-blank-node"> blank node , and emit the following triple:
For every value of @type , either a term defined in the [ delete: <a class="bibref" href="#bib-csvw-context">insert: <a href="#bib-csvw-context" class="bibref"> csvw-context ], a delete: <a href="#dfn-prefixed-name" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-prefixed-name"> prefixed name , or an absolute URL; establish a new node T i by expanding the value to an absolute URL by replacing a term with the URI from the term definition in [ delete: <a class="bibref" href="#bib-csvw-context">insert: <a href="#bib-csvw-context" class="bibref"> csvw-context ] or a delete: <a href="#dfn-prefixed-name" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-prefixed-name"> prefixed name with its expanded value. For each T i , emit the following triple:
delete: <a href="#dfn-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-node"> node T i
For every key and val from value that does not start with @ ( U+0040 ) generate RDF by running this algorithm using S for subject , key for property and val for value .
Else, establish lit as an RDF Literal as follows:
If value is true or false , create an RDF Literal lit using the strings "true" or "false", accordingly with datatype xsd:boolean .
Else, if value is a JSON number with a non-zero fractional part, create an RDF Literal lit using the canonical representation for value with datatype xsd:double .
Else, if value is a JSON number with no non-zero fractional part, create an RDF Literal lit using the canonical representation for value with datatype xsd:integer .
Otherwise, create an RDF Literal lit using the canonical representation for value with datatype xsd:string .
In addition to the namespaces defined above , the examples provided here make use of the following namespaces:
dc :
http://purl.org/dc/terms/
foaf :
http://xmlns.com/foaf/0.1/
oa :
http://www.w3.org/ns/oa#
org :
http://www.w3.org/ns/org#
schema :
http://schema.org/
Furthermore, these examples also make use of the Turtle syntax @base declaration (as defined in [ delete: <a class="bibref" href="#bib-turtle">insert: <a href="#bib-turtle" class="bibref"> turtle ]). Where a single tabular data file is used in the example, the @base declaration is set to the URL of that tabular data file.
Each of the examples expresses more complex conversions - it is recommended that readers of this specification work through the examples in sequential order.
This example comprises a single delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> annotated table containing information attributes about countries; country code, position (latitude, longitude) and name. Whilst the input tabular data file, published at http://example.org/countries.csv , includes a delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-header-line" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-header-line" class="externalDFN"> header line , no further metadata annotations are given. The tabular data file is provided below:
Example 3 insert: <span style="text-transform: none"> : http://example.org/countries.csv insert: </span>
countryCode,latitude,longitude,name AD,42.5,1.6,Andorra AE,23.4,53.8,"United Arab Emirates" AF,33.9,67.7,Afghanistan
The delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> annotated table generated from parsing the tabular data file is shown below and provides the basis for the conversion to RDF.
Annotations for the resulting delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> table T , with 4 columns and 3 rows, are shown below:
id
core annotations
url
columns
rows
T
http://example.org/countries.csv
C1 , C2 , C3 , C4
R1 , R2 , R3
Annotations for the delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> columns , delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> rows and delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> cells in delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> table T are shown in the tables below:
The delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-about-url" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-about-url" class="externalDFN"> about URL annotation has not been set for cells in table T ( { "url": "http://example.org/countries.csv"} ); delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> cells in a given delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row where delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-about-url" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-about-url" class="externalDFN"> about URL has not been specified are assumed to refer to the same delete: <a href="#dfn-subject" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-subject"> subject . This unspecified delete: <a href="#dfn-subject" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-subject"> subject is treated as a delete: <a href="#dfn-blank-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-blank-node"> blank node .
Given that the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-property-url" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-property-url" class="externalDFN"> property URL is null for cells in table T ( { "url": "http://example.org/countries.csv"} ), the property URL defaults to the URI Template (see [ delete: <a class="bibref" href="#bib-RFC6570">insert: <a href="#bib-RFC6570" class="bibref"> RFC6570 ]) #{ [column-name] } , where [column-name] is the value of the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-name" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-column-name" class="externalDFN"> name annotation of the column associated with the cell. For example, the value of the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-property-url" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-property-url" class="externalDFN"> property URL annotation for all delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> cells in delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> column C1 ( "name": "countryCode" ) is http://example.org/countries.csv#countryCode .
delete: <a href="#dfn-standard-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-standard-mode"> Standard mode output for this example is provided in [ delete: <a class="bibref" href="#bib-turtle">insert: <a href="#bib-turtle" class="bibref"> turtle ] syntax below:
Example 5 insert: <span style="text-transform: none"> : http://example.org/countries-standard.ttl insert: </span>
Even though the delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> table was defined in isolation, the delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> annotated table is wrapped in a delete: <a href="#dfn-group-of-tables" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-group-of-tables"> group of tables .
The type of both delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> table and delete: <a href="#dfn-group-of-tables" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-group-of-tables"> group of tables objects is explicitly stated; csvw:TableGroup and csvw:Table respectively.
The csvw:url property provides reference to the original tabular data file and to specific delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> rows therein - noting the need to escape the Turtle-syntax reserved character = ( U+003D ) within the fragment identifier.
The delete: <a href="#dfn-row-number" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row-number"> row number is provided for each delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row using csvw:rownum property.
A delete: <a href="#dfn-subject" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-subject"> subject and delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row are related using the csvw:describes property.
7.2 Example with single table and rich annotations
This example is based on Use Case #11 - City of Palo Alto Tree Data and comprises a single delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> annotated table describing an inventory of tree maintenance operations. The input tabular data file, published at http://example.org/tree-ops-ext.csv , and the associated metadata description http://example.org/tree-ops-ext.csv-metadata.json are provided below:
Example 6 insert: <span style="text-transform: none"> : http://example.org/tree-ops-ext.csv insert: </span>
GID,On Street,Species,Trim Cycle,Diameter at Breast Ht,Inventory Date,Comments,Protected,KML 1,ADDISON AV,Celtis australis,Large Tree Routine Prune,11,10/18/2010,,,"<Point><coordinates>-122.156485,37.440963</coordinates></Point>" 2,EMERSON ST,Liquidambar styraciflua,Large Tree Routine Prune,11,6/2/2010,,,"<Point><coordinates>-122.156749,37.440958</coordinates></Point>" 6,ADDISON AV,Robinia pseudoacacia,Large Tree Routine Prune,29,6/1/2010,cavity or decay; trunk decay; codominant leaders; included bark; large leader or limb decay; previous failure root damage; root decay; beware of BEES,YES,"<Point><coordinates>-122.156299,37.441151</coordinates></Point>"
Example 7 insert: <span style="text-transform: none"> : http://example.org/tree-ops-ext.csv-metadata.json insert: </span>
The delete: <a href="#dfn-notes" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-notes"> notes annotation in the metadata description uses the Open Annotation data model currently under development within the Web Annotations Working Group . This is purely illustrative; no constraints are placed on the value of the delete: <a href="#dfn-notes" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-notes"> notes annotation.
The delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> annotated table generated from parsing the tabular data file and associated metadata is shown below and provides the basis for the conversion to RDF.
Core annotations for the resulting delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> table T , with 9 delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> columns and 3 delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> rows , are shown below:
id
core annotations
id
url
columns
rows
notes
T
<http://example.org/tree-ops-ext>
http://example.org/tree-ops-ext.csv
C1 , C2 , C3 , C4 , C5 , C6 , C7 , C8 , C9
R1 , R2 , R3
[{ "@type": "oa:Annotation", ... }]
Non-core annotations for the delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> table T are:
The value of the delete: <a href="#dfn-notes" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-notes"> notes annotation has been shortened for clarity in the table above.
Annotations for the delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> columns , delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> rows and delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> cells in delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> table T are shown in the tables below:
"cavity or decay; trunk decay; codominant leaders; included bark; large leader or limb decay; previous failure root damage; root decay; beware of BEES"
"cavity or decay" , "trunk decay" , "codominant leaders" , "included bark" , "large leader or limb decay" , "previous failure root damage" , "root decay" , "beware of BEES"
The lists of values from delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> cells in delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> column C7 ( "name": "comments" ) are assumed to be unordered as the boolean delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-ordered" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-ordered" class="externalDFN"> ordered annotation, which defaults to false , has not be set within the metadata description.
delete: <a href="#dfn-minimal-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-minimal-mode"> Minimal mode output for this example is provided in [ delete: <a class="bibref" href="#bib-turtle">insert: <a href="#bib-turtle" class="bibref"> turtle ] syntax below:
Example 8 insert: <span style="text-transform: none"> : http://example.org/tree-ops-ext-minimal.ttl insert: </span>
The delete: <a href="#dfn-subject" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-subject"> subject described by each delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row is explicitly defined using the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-about-url" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-about-url" class="externalDFN"> about URL annotation; e.g. the delete: <a href="#dfn-subject" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-subject"> subject of delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row R1 is http://example.org/tree-ops-ext#gid-1 .
Output for delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> column C1 ( { "name": "GID" } ) is not included as the delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> column delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-column-suppress-output" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-column-suppress-output" class="externalDFN"> suppress output annotation is true .
A language tag is specified for delete: <a data-lt="cell value" href="#dfn-cell-value" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell-value" data-lt="cell value"> values of delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> column C4 ( { "name": "trim_cycle" } ) as the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-language" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-value-language" class="externalDFN"> cell value language annotation is en .
The delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-column-datatype">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-column-datatype"> datatype annotation is set on delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> columns C5 , C6 , C8 and C9 ( { "name": "dbh"} , { "name": "inventory_date" } , { "name": "protected" } and { "name": "kml" } ); as integer , date , boolean and xml respectively. The delete: <a href="http://www.w3.org/TR/2015/PR-tabular-metadata-20151117/#cell-datatype">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-metadata-20151217/#cell-datatype"> datatype property is inherited by all delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> cells in each of those delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> columns , therefore the RDF output for those delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> cells includes the appropriate datatype IRI .
delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> Cells C1.7 and C2.7 ( delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> rows R1 and R2 ; delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> column , { "name": "comments" } ) have null delete: <a data-lt="cell value" href="#dfn-cell-value" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell-value" data-lt="cell value"> values - no output is included for these delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> cells .
delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> Cell C3.7 ( delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row R3 ; delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> column , { "name": "comments" } ) contains an unordered sequence of values; the set of values are included as a simple set of triples as opposed to an instance of rdf:List as the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-ordered" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-ordered" class="externalDFN"> ordered annotation has defaulted to false .
delete: <a href="#dfn-standard-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-standard-mode"> Standard mode output for this example is provided in [ delete: <a class="bibref" href="#bib-turtle">insert: <a href="#bib-turtle" class="bibref"> turtle ] syntax below:
Example 9 insert: <span style="text-transform: none"> : http://example.org/tree-ops-ext-standard.ttl insert: </span>
delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> Table T ( { "url": "http://example.org/tree-ops-ext.csv"} ) has been explicitly identified: { "@id": "<http://exmple.org/tree-ops-ext>"} .
delete: <a href="#dfn-non-core-annotations" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-non-core-annotations"> Non-core annotations and delete: <a href="#dfn-notes" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-notes"> notes specified for delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> table T ( { "url": "http://example.org/tree-ops-ext.csv"} ) are included in the output.
As the metadata description file http://example.org/tree-ops-ext.csv-metadata.json defines a default language within the context ( "@context": ["http://www.w3.org/ns/csvw", {"@language": "en"}] ), all delete: <a href="#dfn-non-core-annotations" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-non-core-annotations"> non-core annotations of type string (e.g. dc:title , dcat:keyword , dc:publisher , dc:license and dc:modified ) are expressed in the RDF output using the the appropriate language tag .
7.3 Example with single table and using virtual columns to produce multiple subjects per row
This example uses a single delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> annotated table describing a listing of music events. Each delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row from the tabular data file corresponds to three resources; the music event itself, the location where that event occurs and the offer to sell tickets for that event. The goal is to convert the CSV content into schema.org markup that a search engine such as Google can use to index music events. Details of how Google expects this information to be structured can be found here .
The input tabular data file, published at http://example.org/events-listing.csv , and the associated metadata description http://example.org/events-listing.csv-metadata.json are provided below:
Example 10 insert: <span style="text-transform: none"> : http://example.org/events-listing.csv insert: </span>
The CSV to RDF translation is limited to providing one statement, or triple, per delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> column in the delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> table . The target schema.org markup requires 10 statements to describe each event. As the base tabular data file contains 5 columns, an additional 5 virtual delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> columns have been added in order to provide for the full complement of statements—including the relationships between the 3 resources (event, location, and offer) described by each delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row of the delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> table . Note that the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-virtual" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-column-virtual" class="externalDFN"> virtual annotation is set to true for these virtual delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> columns .
Furthermore, note that no attempt is made to reconcile between locations or offers that may be associated with more than one event; every delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row in the delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> table will create both a new location resource and offer resource in addition to the event resource. If considered necessary, applications such as OpenRefine may be used to identify and reconcile duplicate location resources once the RDF output has been generated.
The delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> annotated table generated from parsing the tabular data file and associated metadata is shown below and provides the basis for the conversion to RDF.
Annotations for the resulting delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> table T , with 10 delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> columns and 2 delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> rows , are shown below:
id
core annotations
url
columns
rows
T
http://example.org/events-listing.csv
C1 , C2 , C3 , C4 , C5 , C6 , C7 , C8 , C9 , C10
R1 , R2
Annotations for the delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> columns , delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> rows and delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> cells in delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> table T are shown in the tables below:
Three resources are defined for each row within the table; event, location, and offer.
Each delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> column description in the metadata explicitly defines both delete: <a href="http://www.w3.org/TR/2015/PR-tabular-metadata-20151117/#cell-aboutUrl">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-metadata-20151217/#cell-aboutUrl"> aboutUrl and delete: <a href="http://www.w3.org/TR/2015/PR-tabular-metadata-20151117/#cell-propertyUrl">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-metadata-20151217/#cell-propertyUrl"> propertyUrl properties which are used to create the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-about-url" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-about-url" class="externalDFN"> about URL and delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-property-url" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-property-url" class="externalDFN"> property URL annotations on the column's delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> cells .
delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> Columns C6 , C7 and C8 ( { "name": "type_event"} , { "name": "type_place"} and { "name": "type_offer"} ) define the semantic types of the resources described by each delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row : schema:MusicEvent , schema:Place and schema:Offer respectively.
delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> Column C9 ( { "name": "location"} ) uses the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-about-url" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-about-url" class="externalDFN"> about URL , delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-property-url" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-property-url" class="externalDFN"> property URL and delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-value-url" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-value-url" class="externalDFN"> value URL to assert the relationship between the event and location resources.
delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> Column C10 ( { "name": "offer"} ) uses the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-about-url" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-about-url" class="externalDFN"> about URL , delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-property-url" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-property-url" class="externalDFN"> property URL and delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-value-url" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-value-url" class="externalDFN"> value URL to assert the relationship between the event and offer resources.
delete: <a href="#dfn-standard-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-standard-mode"> Standard mode output for this example is provided in [ delete: <a class="bibref" href="#bib-turtle">insert: <a href="#bib-turtle" class="bibref"> turtle ] syntax below:
Example 13 insert: <span style="text-transform: none"> : http://example.org/events-listing-standard.ttl insert: </span>
The resources described by each delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row are explicitly defined using the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-about-url" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-about-url" class="externalDFN"> about URL annotation this case three resources per delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row (event, location, and offer). The relationship between the delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row and each delete: <a href="#dfn-subject" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-subject"> subject resource is asserted using the csvw:describes property; e.g. for delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row R1 , a delete: <a href="#dfn-blank-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-blank-node"> blank node , we state the following triples:
7.4 Example with delete: <a href="#dfn-group-of-tables" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-group-of-tables"> group of tables comprising four interrelated tables
This example is based on Use Case #4 - Publication of public sector roles and salaries and uses four delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> annotated tables published as a delete: <a href="#dfn-group-of-tables" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-group-of-tables"> group of tables . Information about senior roles and junior roles within a government department or organization are published in CSV format by each department. These are validated against a centrally published delete: <a href="http://www.w3.org/TR/2015/PR-tabular-metadata-20151117/#dfn-schema" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-metadata-20151217/#dfn-schema" class="externalDFN"> schema to ensure that all the data published by departments is consistent. Additionally, lists of organizations and professions are also published centrally, providing controlled vocabularies against which departmental submissions are validated.
Information published about junior and senior roles provides summary information for each post within the government department or organization. Whilst the junior role information is anonymous, providing only an indication of the number of full-time-equivalent (FTE) staff occupying a given post, the senior role information specifies the named individual occupying each post. As such, each delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row from the tabular data file describing senior roles corresponds to two resources; the post and the person occupying that post.
This example is concerned only with converting the information provided by each government department or organization rather than the centrally published information listing organizations and professions.
The input tabular data files and associated metadata descriptions are provided below:
Example 14 insert: <span style="text-transform: none"> : http://example.org/gov.uk/data/organizations.csv insert: </span>
Organization Unique Reference,Organization Name,Department Reference hefce.ac.uk,Higher Education Funding Council for England,bis.gov.uk bis.gov.uk,"Department for Business, Innovation and Skills",xx
Example 15 insert: <span style="text-transform: none"> : http://example.org/gov.uk/data/professions.csv insert: </span>
Profession Finance Information Technology Operational Delivery Policy
Example 16 insert: <span style="text-transform: none"> : http://example.org/senior-roles.csv insert: </span>
Post Unique Reference,Name,Grade,Job Title,Reports to Senior Post,Profession,Organization Reference 90115,Steve Egan,SCS1A,Deputy Chief Executive,90334,Finance,hefce.ac.uk 90334,Sir Alan Langlands,SCS4,Chief Executive,xx,Policy,hefce.ac.uk
Example 17 insert: <span style="text-transform: none"> : http://example.org/junior-roles.csv insert: </span>
Reporting Senior Post,Grade,Payscale Minimum (£),Payscale Maximum (£),Generic Job Title,Number of Posts (FTE),Profession,Organization Reference 90115,4,17426,20002,Administrator,8.67,Operational Delivery,hefce.ac.uk 90115,5,19546,22478,Administrator,0.5,Operational Delivery,hefce.ac.uk
Example 18 insert: <span style="text-transform: none"> : http://example.org/csv-metadata.json insert: </span>
This example makes extensive use of the example.org domain. As described in [ delete: <a class="bibref" href="#bib-RFC6761">insert: <a href="#bib-RFC6761" class="bibref"> RFC6761 ], this domain is used for illustrative examples within documentation. In reality, the resources described here with the URL path /gov.uk would be centrally published by the UK Government at, say, the domain data.gov.uk .
Given that these resources are centrally published with an aspiration for reuse, the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-metadata-20151117/#dfn-schema-description" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-metadata-20151217/#dfn-schema-description" class="externalDFN"> schema descriptions have been factored out into separate resources. As such, the top-level metadata description resource metadata.json simply provides the list of delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-table" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-table" class="externalDFN"> tables and binds each of them to the appropriate delete: <a href="http://www.w3.org/TR/2015/PR-tabular-metadata-20151117/#dfn-schema" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-metadata-20151217/#dfn-schema" class="externalDFN"> schema that is defined elsewhere.
Finally, note that because the centrally published metadata descriptions are intended to be reused across many government departments and organizations, extra consideration has been given to defining URIs for the person and post resources defined in each row of the senior roles tabular data and subsequently referenced from the junior roles tabular data. To ensure that naming clashes are avoided, the unique reference for the organization to which the person or post belongs has been included in a path segment of the identifier. For example, the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-metadata-20151117/#dfn-uri-template-properties">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-metadata-20151217/#dfn-uri-template-property"> URI template property delete: <a href="http://www.w3.org/TR/2015/PR-tabular-metadata-20151117/#cell-aboutUrl">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-metadata-20151217/#cell-aboutUrl"> aboutUrl used to identify the senior post is specified as http://example.org/organization/{organizationRef}/post/{ref} , thus yielding the URI http://example.org/organization/hefce.ac.uk/post/90115 for the post described in the first delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row of the senior roles tabular data.
The delete: <a href="#dfn-group-of-tables" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-group-of-tables"> group of tables generated from parsing the tabular data files and associated metadata is shown below and provides the basis for the conversion to RDF.
Annotations for the delete: <a href="#dfn-group-of-tables" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-group-of-tables"> group of tables G and the four delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> tables Ta , Tb , Tc , and Td are shown below:
delete: <a href="#dfn-group-of-tables" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-group-of-tables"> Group of Tables annotations:
In this example, output for the centrally published lists of organizations and professions, tables Ta and Tb ( http://example.org/gov.uk/data/organizations.csv and http://example.org/gov.uk/data/professions.csv respectively), are not required; only information from the departmental submissions is to be translated to RDF. Note the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-table-suppress-output" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-table-suppress-output" class="externalDFN"> suppress output annotation on this delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> table .
The following foreign keys are defined:
id
columns in table
columns in referenced table
Fa1
Ca3
Ca1
Fc1
Cc5
Cc1
Fc2
Cc6
Cb1
Fc3
Cc7
Ca1
Fd1
Cd1
Cc1
Fd2
Cd7
Cb1
Fd3
Cd8
Ca1
Annotations for the delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> columns , delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> rows and delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> cells in delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> table T are shown in the tables below:
delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> Column Cc8 , with the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-metadata-20151117/#column-virtual">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-metadata-20151217/#column-virtual"> virtual annotation specified as true , is used to relate the person resource, whose name is provided in delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> column Cc2 , to the associated post resource within the current delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row of delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> table Tc ( { "url": "http://example.org/senior-roles.csv" } ).
Notice that delete: <a href="#dfn-value-url" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-value-url"> value URL is not specified for delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> cells Ca2.3 and Cc2.5 because in each case the delete: <a href="#dfn-cell-value" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell-value"> cell value is null and the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-virtual" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-column-virtual" class="externalDFN"> virtual annotation of delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> column Cb5 is not defined.
delete: <a href="#dfn-minimal-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-minimal-mode"> Minimal mode output for this example is provided in [ delete: <a class="bibref" href="#bib-turtle">insert: <a href="#bib-turtle" class="bibref"> turtle ] syntax below:
Example 23 insert: <span style="text-transform: none"> : http://example.org/public-sector-roles-and-salaries-minimal.ttl insert: </span>
Output for delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> tables Ta and Tb ( { "url": "http://example.org/gov.uk/data/organizations.csv" } and { "url": "http://example.org/gov.uk/data/professions.csv" } ) are not included as the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-table-suppress-output" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-table-suppress-output" class="externalDFN"> suppress output annotation is true .
The delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-property-url" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-property-url" class="externalDFN"> property URL is specified for all delete: <a href="#dfn-cell" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-cell"> cells in delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> tables Tc and Td .
delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> Columns Cc5 and Cd1 ( { "name": "reportsTo" } and { "name": "reportsToSenior" } ) use the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-about-url" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-about-url" class="externalDFN"> about URL , delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-property-url" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-property-url" class="externalDFN"> property URL and delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-value-url" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-value-url" class="externalDFN"> value URL annotations to assert the relationship between the post described by a given delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row and the senior post to which it reports.
Similarly, delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> columns Cc7 and Cd8 (both with { "name": "organizationRef" } ) use the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-about-url" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-about-url" class="externalDFN"> about URL , delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-property-url" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-property-url" class="externalDFN"> property URL and delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-value-url" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-value-url" class="externalDFN"> value URL annotations to assert the relationship between the post described by a given delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row and the organization to which it belongs.
Finally, note that two resources are created for each delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row within delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> table Tc ( { "url": "http://example.org/senior-roles.csv" } ): the person and the post they occupy. The relationship between these resources is specified via virtual delete: <a href="#dfn-column" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-column"> column Cc8 ( { "name": "post_holder" } ) using the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-about-url" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-about-url" class="externalDFN"> about URL , delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-property-url" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-property-url" class="externalDFN"> property URL and delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-cell-value-url" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-cell-value-url" class="externalDFN"> value URL annotations.
delete: <a href="#dfn-standard-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-standard-mode"> Standard mode output for this example is provided in [ delete: <a class="bibref" href="#bib-turtle">insert: <a href="#bib-turtle" class="bibref"> turtle ] syntax below:
Example 24 insert: <span style="text-transform: none"> : http://example.org/public-sector-roles-and-salaries-standard.ttl insert: </span>
delete: <a data-lt="group of tables" href="#dfn-group-of-tables" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-group-of-tables" data-lt="group of tables"> Table group G was explicitly defined, but has not been explicitly identified; the table group and table resources are treated as delete: <a href="#dfn-blank-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-blank-node"> blank nodes .
The person and post resources described by each delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row of delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> table Tc ( { "url": "http://example.org/senior-roles.csv"} ) are explcitly defined using the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-metadata-20151117/#cell-aboutUrl">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-metadata-20151217/#cell-aboutUrl"> aboutUrl property; therefore, say, for delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row Rc1 we state the following triples:
Conversely, the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-metadata-20151117/#cell-aboutUrl">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-metadata-20151217/#cell-aboutUrl"> aboutUrl property has not been defined for resources described by each delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row of delete: <a href="#dfn-annotated-table" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-annotated-table"> table Td ( { "url": "http://example.org/junior-roles.csv"} ); therefore delete: <a href="#dfn-blank-node" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-blank-node"> blank nodes are used, e.g. for delete: <a href="#dfn-row" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-row"> row Rd1 we state the following triple:
The "Direct Mapping of Relational Data to RDF" W3C Recommendation [ delete: <a class="bibref" href="#bib-rdb-direct-mapping">insert: <a href="#bib-rdb-direct-mapping" class="bibref"> rdb-direct-mapping ] defines a simple transformation (referred to as delete: <dfn data-dfn-type="dfn" id="dfn-direct-mapping">insert: <dfn id="dfn-direct-mapping" data-dfn-type="dfn"> direct mapping ) from a relational representation of data to RDF. The direct mapping takes as input a relational database (data and schema), and generates an RDF graph called the delete: <dfn data-dfn-type="dfn" id="dfn-direct-graph">insert: <dfn id="dfn-direct-graph" data-dfn-type="dfn"> direct graph . Tables in a relational databases bear a strong resemblance to tabular data as defined in [ delete: <a class="bibref" href="#bib-tabular-data-model">insert: <a href="#bib-tabular-data-model" class="bibref"> tabular-data-model ]; this section highlights the similarities and differences between the delete: <a href="#dfn-direct-mapping" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-direct-mapping"> direct mapping and the delete: <a href="#dfn-tabular-data-mapping" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-tabular-data-mapping"> tabular data mapping defined by this document. The following statements summarize the relationships:
It is possible, for a single table in a relational database, to provide an annotation to the corresponding tabular data (i.e., the CSV export of the table from the database) such that the output of the delete: <a href="#dfn-direct-mapping" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-direct-mapping"> direct mapping is semantically equivalent to the output of the ( delete: <a href="#dfn-minimal-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-minimal-mode"> minimal ) delete: <a href="#dfn-tabular-data-mapping" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-tabular-data-mapping"> tabular data mapping . See the example with a single table .
If the database consists of several interrelated tables it is not always possible to provide an annotation to the corresponding tabular data to achieve the same level of semantic equivalence. Examples are provided indicating where delete: <a href="#dfn-tabular-data-mapping" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-tabular-data-mapping"> tabular data mapping can and cannot match delete: <a href="#dfn-direct-mapping" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-direct-mapping"> direct mapping : the example with two tables and the example with three tables respectively.
The rest of this section will provide some examples. These are somewhat simplified forms of the examples as used in the [ delete: <a class="bibref" href="#bib-rdb-direct-mapping">insert: <a href="#bib-rdb-direct-mapping" class="bibref"> rdb-direct-mapping ] document.
Consider a simple table in a relational database, called People :
PK
ID
fname
addr
7
Bob
18
A relational table always has a schema that the delete: <a href="#dfn-direct-mapping" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-direct-mapping"> direct mapping makes use of. In this example, the schema defines that:
The table has three columns named ID , fname , and addr .
Values in ID are the primary keys in the table, and the corresponding cells contain integers.
Cells in the fname column contain strings.
Cells in the addr column contain integers.
Using the schema information, the delete: <a href="#dfn-direct-graph" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-direct-graph"> direct graph is as follows (see [ delete: <a class="bibref" href="#bib-rdb-direct-mapping">insert: <a href="#bib-rdb-direct-mapping" class="bibref"> rdb-direct-mapping ] for further details):
where http://foo.example.org/DB/ is the URL for the database containing the People table.
When exporting the table into CSV the column names would naturally be mapped on the titles of the respective columns. The ( delete: <a href="#dfn-minimal-mode" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-minimal-mode"> minimal ) delete: <a href="#dfn-tabular-data-mapping" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-tabular-data-mapping"> tabular data mapping yields:
where http://foo.example.org/CSV/People is the URL of the CSV file exported from the relational database.
Comparing the two conversion results:
The delete: <a href="#dfn-tabular-data-mapping" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-tabular-data-mapping"> tabular data mapping does not have the information that the first column provides unique identifiers for the rows (i.e., that it is a primary key); consequently, a blank node must be used for the common row subject.
The delete: <a href="#dfn-tabular-data-mapping" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-tabular-data-mapping"> tabular data mapping does not have information on the data types and, therefore, cannot presume that the first and the third columns contain integers.
The delete: <a href="#dfn-direct-mapping" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-direct-mapping"> direct mapping adds a triple with predicate rdf:type to the delete: <a href="#dfn-direct-graph" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-direct-graph"> direct graph . However, by default (e.g., without additional annotation), the delete: <a href="#dfn-tabular-data-mapping" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-tabular-data-mapping"> tabular data mapping has insufficient information to make such an assertion.
It is, however, possible to add annotation to the tabular data so that the two graphs would be semantically equivalent. Indeed, consider the following metadata using the definitions of the [ delete: <a class="bibref" href="#bib-tabular-metadata">insert: <a href="#bib-tabular-metadata" class="bibref"> tabular-metadata ] specification:
The metadata adds annotations on datatypes, adds the RDF typing triple explicitly (using a delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-virtual-columns" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-column-virtual" class="externalDFN"> virtual column ), and uses the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-metadata-20151117/#cell-aboutUrl" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-metadata-20151217/#cell-aboutUrl" class="externalDFN"> aboutUrl URL template property to provide the common subject. Essentially, the metadata provides the information that the delete: <a href="#dfn-direct-mapping" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-direct-mapping"> direct mapping retrieves from the table schema.
The [ delete: <a class="bibref" href="#bib-tabular-metadata">insert: <a href="#bib-tabular-metadata" class="bibref"> tabular-metadata ] specification includes an annotation for delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-primary-key" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-row-primary-key" class="externalDFN"> primary keys . However, that annotation is used for validation and does not influence the delete: <a href="#dfn-tabular-data-mapping" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-tabular-data-mapping"> tabular data mapping , hence it is not included in the example metadata.
Consider a two interrelated simple tables in a relational database, called People and Addresses , respectively:
PK
→ Addresses(ID)
ID
fname
addr
7
Bob
18
PK
ID
city
state
18
Cambridge
MA
Beyond what is already specified for the People table the corresponding relational schema also specifies that:
The Addresses table has three columns named ID , city , and state .
Values of ID are primary keys in the Addresses table, and the corresponding cells contain integers.
Cells in both the city and state columns in the Addresses table contain strings.
Cells in the addr column of the People table are foreign keys that reference the ID field of the Addresses table.
Using the schema information, the delete: <a href="#dfn-direct-graph" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-direct-graph"> direct graph is as follows (see [ delete: <a class="bibref" href="#bib-rdb-direct-mapping">insert: <a href="#bib-rdb-direct-mapping" class="bibref"> rdb-direct-mapping ] for further details):
Note the highlighted RDF triple linking to the relevant row of the Addresses table; this corresponds to the foreign key in the schema.
Using the following metadata the delete: <a href="#dfn-tabular-data-mapping" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-tabular-data-mapping"> tabular data mapping yields a semantically equivalent result:
Consider a case with three, interrelated simple tables in a relational database, called People , Addresses , and Departments , respectively:
PK
→ Addresses(ID)
→ Department(name,city)
ID
fname
addr
deptName
deptCity
7
Bob
18
accounting
Cambridge
PK
ID
city
state
18
Cambridge
MA
PK
Unique Key
ID
name
city
23
accounting
Cambridge
The corresponding relational schema specifies that:
For the People table
The table has five columns, named ID , name , addr , deptName , and deptCity .
Values in ID are the primary keys in the table, and the corresponding cells contain integers.
Cells in the name , deptName , and deptCity columns contain strings.
Cells in the addr columns contains integers.
For the Addresses table
The table has three columns, named ID , city , and state .
Values in ID are the primary keys in the table, and the corresponding cells contain integers.
Cells in both the city and state columns contain strings.
For the Departments table
The table has three columns, named ID , name , and city .
Values in ID are the primary keys in the table, and the corresponding cells contain integers.
Cells in both the name and city columns contain strings.
The combination of name and city are unique keys.
The cells in the addr column of the People table are foreign keys that reference the ID field of the Addresses table.
The cells in the deptName and deptCity columns in the People table are combined foreign keys referencing candidate keys for the name and city pairs of the Departments table.
Using the schema information, the delete: <a href="#dfn-direct-graph" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-direct-graph"> direct graph is as follows (see [ delete: <a class="bibref" href="#bib-rdb-direct-mapping">insert: <a href="#bib-rdb-direct-mapping" class="bibref"> rdb-direct-mapping ] for further details):
To generate the correct object URI in the highlighted statement of the delete: <a href="#dfn-direct-graph" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-direct-graph"> direct graph ( above ) the processor has to:
Extract the values of columns deptName and deptCity for the current row in the People table in order to determine the value of the compound unique key to the Departments table for that row.
Find the associated row in the Departments table that matches that compound unique key value and determine the subject for that row.
This can be done because the delete: <a href="#dfn-direct-mapping" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-direct-mapping"> direct mapping processor has simultaneous access to several tables within the same relational database. It is therefore straightforward to access all the tables in parallel and establish the necessary relationships to generate the triples.
However, this combination cannot be handled by the delete: <a href="#dfn-tabular-data-mapping" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-tabular-data-mapping"> tabular data mapping . The situation for tabular data is indeed different: tables are typically generated from single and, potentially, very large CSV files, meaning that a delete: <a href="#dfn-tabular-data-mapping" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-tabular-data-mapping"> tabular data mapping processor cannot be expected to handle several tables in parallel. That is the reason why the [ delete: <a class="bibref" href="#bib-tabular-data-model">insert: <a href="#bib-tabular-data-model" class="bibref"> tabular-data-model ] does not include features that would require such parallel access. As a consequence, the output of the delete: <a href="#dfn-direct-mapping" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-direct-mapping"> direct mapping for such tables cannot be reproduced by the delete: <a href="#dfn-tabular-data-mapping" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-tabular-data-mapping"> tabular data mapping .
Note that the [ delete: <a class="bibref" href="#bib-tabular-data-model">insert: <a href="#bib-tabular-data-model" class="bibref"> tabular-data-model ] includes an annotation for delete: <a href="http://www.w3.org/TR/2015/PR-tabular-metadata-20151117/#transformation-definitions">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-metadata-20151217/#transformation-definitions"> transformations ; implementations may include scripts or templates to transform the output of the delete: <a href="#dfn-tabular-data-mapping" class="internalDFN" data-link-type="dfn">insert: <a data-link-type="dfn" class="internalDFN" href="#dfn-tabular-data-mapping"> tabular data mapping and generate the required RDF graph.
At the time of publication, the following individuals had participated in the Working Group, in the order of their first name: Adam Retter, Alf Eaton, Anastasia Dimou, Andy Seaborne, Axel Polleres, Christopher Gutteridge, Dan Brickley, Davide Ceolin, Eric Stephan, Erik Mannens, Gregg Kellogg, Ivan Herman, Jeni Tennison, Jeremy Tandy, Jürgen Umbrich, Rufus Pollock, Stasinos Konstantopoulos, William Ingram, and Yakov Shafranovich.
C.2 Changes since the working draft of 16 April 2015
Added an appendix describing the relationships to the "Direct Mapping to RDF Specification" [ delete: <a class="bibref" href="#bib-rdb-direct-mapping">insert: <a href="#bib-rdb-direct-mapping" class="bibref"> rdb-direct-mapping ].
The section on datatype has been changed to allow for the reference to externally defined datatypes (as datatype IRI-s in RDF Literals) using the new @id annotation in the model.
The section on generating RDF has been amended to include the provision of delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/#dfn-row-titles" class="externalDFN">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/#dfn-row-titles" class="externalDFN"> row title annotation values in standard mode.
The section on generating RDF has been amended to include a note on the fact that no Unicode normalization is necessary during conversion.
Removed the separate section on "Mapping Core Tabular Data" (to be in line with the latest version of the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/"> tabular model specification).
Reformulated the mappings in terms of table "annotations" (i.e., based on the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/"> tabular model ) rather than table "properties" (i.e., not based on the specificities of the delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/">insert: <a href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/"> metadata vocabulary ).
Provided a set of standard mappings from the general datatypes and the corresponding JSON types.
S. Bradner. delete: <a href="https://tools.ietf.org/html/rfc2119" property="dc:requires">insert: <a property="dc:requires" href="https://tools.ietf.org/html/rfc2119"> Key words for use in RFCs to Indicate Requirement Levels . March 1997. Best Current Practice. URL: delete: <a href="https://tools.ietf.org/html/rfc2119" property="dc:requires">insert: <a property="dc:requires" href="https://tools.ietf.org/html/rfc2119"> https://tools.ietf.org/html/rfc2119
[json-ld-api]
Markus Lanthaler; Gregg Kellogg; Manu Sporny. delete: <a href="http://www.w3.org/TR/json-ld-api/" property="dc:requires">insert: <a property="dc:requires" href="http://www.w3.org/TR/json-ld-api/"> JSON-LD 1.0 Processing Algorithms and API . 16 January 2014. W3C Recommendation. URL: delete: <a href="http://www.w3.org/TR/json-ld-api/" property="dc:requires">insert: <a property="dc:requires" href="http://www.w3.org/TR/json-ld-api/"> http://www.w3.org/TR/json-ld-api/
[rdf11-concepts]
Richard Cyganiak; David Wood; Markus Lanthaler. delete: <a href="http://www.w3.org/TR/rdf11-concepts/" property="dc:requires">insert: <a property="dc:requires" href="http://www.w3.org/TR/rdf11-concepts/"> RDF 1.1 Concepts and Abstract Syntax . 25 February 2014. W3C Recommendation. URL: delete: <a href="http://www.w3.org/TR/rdf11-concepts/" property="dc:requires">insert: <a property="dc:requires" href="http://www.w3.org/TR/rdf11-concepts/"> http://www.w3.org/TR/rdf11-concepts/
[tabular-data-model]
Jeni Tennison; Gregg Kellogg. delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/" property="dc:requires">insert: <a property="dc:requires" href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/"> Model for Tabular Data and Metadata on the Web . W3C Proposed Recommendation. URL: delete: <a href="http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/" property="dc:requires">http://www.w3.org/TR/2015/PR-tabular-data-model-20151117/ insert: <a property="dc:requires" href="http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/">http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/
J. Gregorio; R. Fielding; M. Hadley; M. Nottingham; D. Orchard. delete: <a href="https://tools.ietf.org/html/rfc6570" property="dc:references">insert: <a property="dc:references" href="https://tools.ietf.org/html/rfc6570"> URI Template . March 2012. Proposed Standard. URL: delete: <a href="https://tools.ietf.org/html/rfc6570" property="dc:references">insert: <a property="dc:references" href="https://tools.ietf.org/html/rfc6570"> https://tools.ietf.org/html/rfc6570
[RFC6761]
S. Cheshire; M. Krochmal. delete: <a href="https://tools.ietf.org/html/rfc6761" property="dc:references">insert: <a property="dc:references" href="https://tools.ietf.org/html/rfc6761"> Special-Use Domain Names . February 2013. Proposed Standard. URL: delete: <a href="https://tools.ietf.org/html/rfc6761" property="dc:references">insert: <a property="dc:references" href="https://tools.ietf.org/html/rfc6761"> https://tools.ietf.org/html/rfc6761
[RFC7111]
M. Hausenblas; E. Wilde; J. Tennison. delete: <a href="https://tools.ietf.org/html/rfc7111" property="dc:references">insert: <a property="dc:references" href="https://tools.ietf.org/html/rfc7111"> URI Fragment Identifiers for the text/csv Media Type . January 2014. Informational. URL: delete: <a href="https://tools.ietf.org/html/rfc7111" property="dc:references">insert: <a property="dc:references" href="https://tools.ietf.org/html/rfc7111"> https://tools.ietf.org/html/rfc7111
[UAX15]
Mark Davis; Ken Whistler. delete: <a href="http://www.unicode.org/reports/tr15" property="dc:references">insert: <a property="dc:references" href="http://www.unicode.org/reports/tr15"> Unicode Normalization Forms . 31 August 2012. Unicode Standard Annex #15. URL: delete: <a href="http://www.unicode.org/reports/tr15" property="dc:references">insert: <a property="dc:references" href="http://www.unicode.org/reports/tr15"> http://www.unicode.org/reports/tr15
Marcelo Arenas; Alexandre Bertails; Eric Prud'hommeaux; Juan Sequeda. delete: <a href="http://www.w3.org/TR/rdb-direct-mapping/" property="dc:references">insert: <a property="dc:references" href="http://www.w3.org/TR/rdb-direct-mapping/"> A Direct Mapping of Relational Data to RDF . 27 September 2012. W3C Recommendation. URL: delete: <a href="http://www.w3.org/TR/rdb-direct-mapping/" property="dc:references">insert: <a property="dc:references" href="http://www.w3.org/TR/rdb-direct-mapping/"> http://www.w3.org/TR/rdb-direct-mapping/