Case of language tags
mercurial
handling rdf:langString according to previous WG discussion and consistently between Concepts and Semantics
handling rdf:langString according to previous WG discussion and consistently between Concepts and Semantics
Test submission instructions in implementation report
my list of changes needed to Semantics and Concepts
Minutes telecon 2013-02-27 published
other changes in Semantics
Regrets for Next 3 Weeks
WG resolutions pointer on Wiki home page
proposal to close Issue 109 (ill-typed literals)
JSON-LD Telecon Minutes for 2013-02-26
RDF errors
datatype maps in Semantics and Concepts
status of rdf:langString
change needed in RDF concepts
simple literals in concrete RDF syntaxes
Regrets for Next 3 Weeks
agenda 27 Feb telecon
Re: Turtle tests blank ID patches, and EARL report for Serd
Blank Nodes as Graph Identifiers are NOT required for Normalization
Agenda: JSON-LD Telecon - Tuesday, February 26th 2013
JSON-LD 1.0 Ready for Last Call
status of RDF Concepts and Semantics
Update EARL rollup for CR Turtle
RDF-ISSUE-119 (Test-Suite): Spec should reference the test suite [RDF Turtle]
Minutes of the RDF WG telecon of 2013-02-20
new uri schemes for dataset normalization
- Re: Blank Node Identifiers and RDF Dataset Normalization
- Re: Blank Node Identifiers and RDF Dataset Normalization
- Re: Blank Node Identifiers and RDF Dataset Normalization
- Re: Blank Node Identifiers and RDF Dataset Normalization
- Re: Blank Node Identifiers and RDF Dataset Normalization
- Re: Blank Node Identifiers and RDF Dataset Normalization
- RE: Blank Node Identifiers and RDF Dataset Normalization
- Re: Blank Node Identifiers and RDF Dataset Normalization
- Re: Blank Node Identifiers and RDF Dataset Normalization
- Re: Blank Node Identifiers and RDF Dataset Normalization
- Re: Blank Node Identifiers and RDF Dataset Normalization
- Re: Blank Node Identifiers and RDF Dataset Normalization
- Re: Blank Node Identifiers and RDF Dataset Normalization
- Re: Blank Node Identifiers and RDF Dataset Normalization
- Re: Blank Node Identifiers and RDF Dataset Normalization
- Re: Blank Node Identifiers and RDF Dataset Normalization
- Re: Blank Node Identifiers and RDF Dataset Normalization
- Re: Blank Node Identifiers and RDF Dataset Normalization
- Re: Blank Node Identifiers and RDF Dataset Normalization
- RE: Blank Node Identifiers and RDF Dataset Normalization
- Re: Blank Node Identifiers and RDF Dataset Normalization
Agenda for 20 Feb 2013
Additions to Agenda tomorrow
JSON-LD Telecon Minutes for 2013-02-19
Fwd: Turtle is a W3C Candidate Recommendation (Call for Implementations)
- Re: Turtle is a W3C Candidate Recommendation (Call for Implementations)
- Re: Turtle is a W3C Candidate Recommendation (Call for Implementations)
Turtle CR / editorial
Agenda: JSON-LD Telecon - Tuesday, February 18th 2013
Intent to close ISSUE-204
RDF-ISSUE-118 (Simplifying datatypes): Simplifying datatype semantics [RDF Semantics]
RDF-ISSUE-117 (i18n comments): LC Comments: i18n WG [RDF Turtle]
ACTIO-229: finding the evidence
Turle LC comments
minutes 13 Feb telecon available
RDF-ISSUE-116: LC Comment: revised reponse to 'Comments regarding "Turtle and N-Triples Synaxes for RDF" ' [RDF Turtle]
RDF-ISSUE-115: LC Comment: Unsetting @base and @prefix [RDF Turtle]
Intent to close ISSUE-213
Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- RE: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- RE: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- RE: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- RE: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- RE: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- RE: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- RE: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- RE: Problem with auto-generated fragment IDs for graph names
- Re: Problem with auto-generated fragment IDs for graph names
- RE: Problem with auto-generated fragment IDs for graph names
(very) first draft of semantics available
- Re: (very) first draft of semantics available
- Re: (very) first draft of semantics available
- Re: (very) first draft of semantics available
- Re: (very) first draft of semantics available
- Re: (very) first draft of semantics available
JSON-LD Telecon Minutes for 2013-02-12
agenda 13 Feb telecon
Mercurial toxic spill
Agenda: JSON-LD Telecon - Tuesday, February 12th 2013
Regrets for 13 Feb Telecon
regrets Feb 13
Workgroup Issue Tracking Data in RDF based Linked Data Form
JSON Resource Description ?
If the editors use respec…
Resolution of ISSUE-105
Draft minutes for 2013-02-06 telecon
Fwd: RDF Working Group Requests Extension
JSON-LD Telecon Minutes for 2013-02-05
Intent to close ISSUE-214
Intent to close ISSUE-216
Agenda: JSON-LD Telecon - Tuesday, February 5th 2013
Agenda for 6 Feb 2013
JSON-LD 1.0: Final Community Group Specification v2
Re: Using bnode identifiers for predicates, graph names
- Re: Using bnode identifiers for predicates, graph names
- Re: Using bnode identifiers for predicates, graph names