Re: JSON-LD Context

Note that, as an aside, if we need the csvw namespace, we should do at least some sort of a landing page for it, to be installed on /ns/, to avoid unresolved links in our publications.

Ivan

> On 02 Dec 2014, at 09:24 , Ivan Herman <ivan@w3.org> wrote:
> 
> I am happy to put it on /ns/, and this should probably happen before, or together with, publication. But I would like to wait until a first comment round on it, if any.
> 
> Ivan
> 
>> On 02 Dec 2014, at 03:25 , Gregg Kellogg <gregg@greggkellogg.net> wrote:
>> 
>> I created a JSON-LD context based on the Vocabulary document (likely with many errors) [1]. Note that this document would likely go at http://www.w3.org/ns/csvm/context.jsonld and be served using content-negotiation from http://www.w3.org/ns/csvm.
>> 
>> I added terms for all XSD elements as indicated in DataTypes [2]. However, it’s not clear to me that these were intended as terms, or should be used using the xsd: prefix. If they are terms, note that xsd:language conflicts with our own cdvm:language property.
>> 
>> Also, the “schema” property conflicts with the “schema” prefix for http://schema.org/. We import all prefix definitions from the RDFa Core initial context [3]. There may be other conflicts.
>> 
>> There should also be an RDFS/OWL vocabulary for this, which could be included in the context, and using other RDF formats. This may require discussion.
>> 
>> Gregg Kellogg
>> gregg@greggkellogg.net
>> 
>> [1] http://w3c.github.io/csvw/ns/context.jsonld
>> [2] http://w3c.github.io/csvw/metadata/index.html#datatypes
>> [3] http://www.w3.org/2011/rdfa-context/rdfa-1.1
>> 
>> 
> 
> 
> ----
> Ivan Herman, W3C
> Digital Publishing Activity Lead
> Home: http://www.w3.org/People/Ivan/
> mobile: +31-641044153
> ORCID ID: http://orcid.org/0000-0003-0782-2704
> 
> 
> 
> 


----
Ivan Herman, W3C
Digital Publishing Activity Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
ORCID ID: http://orcid.org/0000-0003-0782-2704