Re: New Specification Published!

I can agree on changing it - but only if it's done pretty soon - ie.
before the OA Manchester meeting. I would also be OK with it staying
as it is.

We've started telling people that the OA specs are stabilizing, so we
can't delay such a change longer.


If we change, I would propose http://www.w3.org/ns/oa/  or
http://www.w3.org/ns/openannotation/

The first is nice because it should give tools who pick the last term
"oa" as a suggest prefix, while the second is nice because it is more
obvious what the vocabulary is for someone who has never heard about
OA before. (Just like it took me years to learn what this mythical
SKOS was. There I would have preferred say.. ).


( Personally I prefer and use the / style in namespaces because it
gives me HTTP control per term. It could for instance be that a HTTP
resolving by a HTML browser of
http://www.w3.org/ns/oa/SpecificResource would resolve to the
equivalent of
http://www.openannotation.org/spec/core/20130205/specific.html#Specific
.  With the # solution at best you can do a redirection to the front
page or a landing page (as found on http://www.w3.org/ns/prov# )

The / solution also allows us flexibility to declare any extension
properties/classes in the same namespace without including them in the
same ontology. Users prefer less namespaces - but they also prefer
unclutted ontologies. )



For University of Manchester/Wf4Ever usage of OA, we've not completely
moved over from AO yet, so we're flexible. The only code that uses OA
now is of "snapshot" status and OK to change, but it will be frozen
over the next months. We are also updating our vocabularies and APIs
to refer to the OA spec over the next 2 months or so, so I would
kindly request the namespace to be stable by then.



-- 
Stian Soiland-Reyes, myGrid team
School of Computer Science
The University of Manchester

Received on Thursday, 7 February 2013 12:54:52 UTC