From RDF Working Group Wiki
Jump to: navigation, search
Wednesdays at 11am US Eastern time for 75 minutes
  17:00 Paris/Berlin/A'dam; 16:00 London
Telephone US: +1.617.761.6200
  Zakim code: 73394
IRC channel: #rdf-wg on on port 6665
Zakim instructions:
RRSAgent instructions:


  • Chair: Guus Schreiber
  • Scribe: Ted Thibodeau

Minutes of last meeting

PROPOSED to accept the minutes of the 11 Dec telecon:

Review of action items

New publications

FPWDs of Primer, New & Datasets Notes published:


Jan-Feb 2014: to be decided.

WG activity plan

Draft PR request:


  • 18 Dec: PR decision
  • 9 Jan: target publication date
  • end of Feb: Rec

PROPOSED: to Request W3M to extend for 2/3 months

  • WG will meet in a voluntary fashion in Jan-Feb to discuss WG notes et al.

PROPOSED: the RDF WG petition the Director to take JSON-LD to Recommendation immediately after the publication of the Proposed Recommendations for the rest of the RDF 1.1 work.

CR implementations

Implementation reports:

Only outstanding issue are two tests in Semantics:

PROPOSED: the WG decides it has met the CR Exit Criteria for RDF 1.1 Turtle, TriG, NiTriples, and N-Quads (see statistics in PR Request [1])

PROPOSED: the WG decides to rescinded the two tests below as they are not helpful to interoperability, for the reasons outlined in [2]:

PROPOSED: the WG decides it it has met the CR Exit Criteria for RDF 1.1 Semantics (see implementation report)

Should we publish RDF 1.1 Test Cases as WG Note?

  • all test suite links in the Rec documents could point to this document
  • also one link for combined implementation reports? (otherwise Concepts has no link to Implmentation report)

Status of Syntax documents


  • ISSUE-119: Spec should reference the test suite
  • Include decision about version naming in Changes section
  • Include link to implementation report in preamble


  • Include changes section
  • List the following changes:
    • A normative reference to RDF Concepts has been added
    • A section mentioning that text/x-nquads with encoding US-ASCII was in the original work has been added.


  • List the change: A normative reference to RDF Concepts has been added

Concepts & Semantics

Background: CR comments

ISSUE-148: IRIs do *not* always denote the same resource

Proposal 1 (message with s/identify/denote):

  • Resolve ISSUE-148 by changing the "IRIs have global scope" bullet point in section 1.3 in Concepts to "IRIs have global scope by definition. Thus, two different appearances of an IRI denote the same resource. RDF is based on this principle and violations of it might lead to inconsistencies or interoperability problems."

Proposal 2 (message):

  • Suggested wording: "By design, IRIs have global scope. Thus, two different appearances of an IRI denote the same resource. Violating this principle constitutes an IRI collision [WEBARCH]."

ISSUE-165 datatype map

PROPOSED: the WG resolves to close this issue, with the rationale stated in the last response to the commenter (, noting the objection from the commenter in the Transition Request.

Marking rdf:HTML and rdf:XMLLiteral as non-normative?!

PROPOSED: to accept the resolution text in

Normative references Concepts <=> Semantics


PR decision

PROPOSED: to request the Director to advance Concepts and Semantics to Proposed Recommendation.

RDF Schema

Draft version of Edited Rec:

  • decide whether the sections on rdf:HTML and rdf:XMLLiteral should be marked as non-normative



Changes required for XMLLiteral:

Review Ivan:

PROPOSED: to request the Director to advance RDF 1.1 XML Syntax to Proposed Edited Recommendation.

Status of PR request

See PR request page

  • missing: link to Turtle features-at-risk resolution

Open issues (other than CR comments)



  • Namespace documents
  • Work to be done in Jan/Feb