- From: Ivan Herman <ivan@w3.org>
- Date: Wed, 3 Dec 2014 17:12:30 +0100
- To: Frederick Hirsch <w3c@fjhirsch.com>
- Cc: Robert Sanderson <azaroth42@gmail.com>, W3C Public Annotation List <public-annotation@w3.org>
- Message-Id: <506ABB43-A4B2-41DA-952A-A50310E55F65@w3.org>
> On 03 Dec 2014, at 16:57 , Frederick Hirsch <w3c@fjhirsch.com> wrote: > > Ivan > > Thanks for noting this. > > It seems to me (personally not as chair) that the right thing to do is the following > > 1. Keep oa as 'http://www.w3.org/ns/oa for the Web Annotation Data Model we are producing, as in the FPWD > > 2. Update the landing page appropriately > > 3. Add a clear warning to the Community Group Open Annotation Data Model ‘community draft’ that there is an update underway in the Web Annotation WG, with a pointer to our new draft and home page > > It seems better to focus on the new work with the same URL as implementations are changing along with the specification. > > JSON-LD is new work so we don’t have a backward compatibility issue, right? Actually, there is a oa.jsonld file right now which is the @context AND the full vocabulary. In other words, it is a JSON-LD serialization of the full vocabulary. And what we need is a separate file for the @context only on, probably, a separate URI. Ivan > > regards, Frederick > > Frederick Hirsch, Nokia > Co-Chair W3C Web Annotation WG > @fjhirsch > > > > On Dec 3, 2014, at 4:37 AM, Ivan Herman <ivan@w3.org> wrote: > >> Rob, >> >> one thing I realized, while looking at the FPWD text: the text refers to oa as 'http://www.w3.org/ns/oa. At this moment that URI exists and refers to the Community Group's output, with the vocabulary set up as an HTML+RDFa and other formats like turtle or json-ld. >> >> If we decide to keep that URI, we should update its landing page. It also means that this WG will override the various vocabularies that are already there. Do we want to do that? If so, we should check whether a new version should be put at those places while publishing the FPWD. >> >> We should also put up on the site a proper JSON-LD @context file; the current document has a phony URI for that purpose, and http://www.w3.org/ns/oa.jsonld has the full vocabulary (I am not sure whether we want that to be the @context file, it is probably too big for that purpose) >> >> Cheers >> >> Ivan >> >> >> ---- >> 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
Received on Wednesday, 3 December 2014 16:12:40 UTC