- From: Stian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk>
- Date: Sun, 22 May 2016 23:53:41 +0200
- To: Robert Sanderson <azaroth42@gmail.com>
- Cc: Sarven Capadisli <info@csarven.ca>, Web Annotation <public-annotation@w3.org>
I don't think that is incompatible or a reason to change the namespace. In my suggested oa.ttl (I don't know what happened to the merging of that) I simply marked those classes and properties as deprecated. I suggest we re-add them to the vocab-document in a "deprecated" section at the end. Adding forward-pointers from the OA specs to WA specs is very much a good idea. On 20 May 2016 at 16:40, Robert Sanderson <azaroth42@gmail.com> wrote: > > Hi Sarven, > > Yes, there are backwards incompatible changes such as the removal of > SemanticTag and oa:serializedBy (etc) replacements. The new ontology should > thus replace the OA CG *draft* namespace. > > Rob > > > On Fri, May 20, 2016 at 4:15 PM, Sarven Capadisli <info@csarven.ca> wrote: >> >> On 2016-05-20 03:50, Robert Sanderson wrote: >>> >>> >>> This is what I was saying on Wednesday ... if we change the namespace, >>> rather than creating a new one, we force the update to the new model. >>> This is why we left the CG work as a draft. We should put a warning into >>> the OA drafts regardless. >>> >>> There is a lot of brand name recognition for Open Annotation, far far >>> more than "web annotation" which seems more like a generic class of >>> annotations. This was also discussed when OAC and AO merged -- we >>> dropped the "Collaboration" and the "Ontology" to try and be more >>> inclusive. >>> >>> OA has had a lot of time and outreach to gain traction and mindshare, >>> which I feel we should capitalize on. The split helps no one. >>> >>> Note that the presentation that followed the NaCTeM one from EMBL-EBI >>> said "web annotation data model" but was actually the open annotation >>> model (it used oa:SemanticTag, which no longer exists). >>> >>> Rob >> >> >> Are there fundamental differences besides deprecation, e.g., redefinition >> of the terms? >> >> Would retaining oa:SemanticTag (and whatever else) have any conflict with >> WA? >> >> What if WA subsumes OA, mark outstanding OA stuff as deprecated, and keep >> the OA ns? Yes, there is still the concern with https. >> >> -Sarven >> http://csarven.ca/#i >> > > > > -- > Rob Sanderson > Semantic Architect > The Getty Trust > Los Angeles, CA 90049 -- Stian Soiland-Reyes, eScience Lab School of Computer Science The University of Manchester http://soiland-reyes.com/stian/work/ http://orcid.org/0000-0001-9842-9718
Received on Sunday, 22 May 2016 21:54:29 UTC