W3C home > Mailing lists > Public > public-annotation@w3.org > November 2015

[web-annotation] Make Selectors available for the wide world?

From: Ivan Herman via GitHub <sysbot+gh@w3.org>
Date: Fri, 20 Nov 2015 04:53:19 +0000
To: public-annotation@w3.org
Message-ID: <issues.opened-117965262-1447995199-sysbot+gh@w3.org>
iherman has just created a new issue for 

== Make Selectors available for the wide world? ==
Selectors (and its subclasses) are very powerful. I can envisage other
 applications needing something similar. Actually, similar in two 
different ways: either as they are, as a description to select part of
 a resource; or to have a powerful fragment ID that can express the 
Selector concepts.  

Can we make steps for reuse of these specifications without disturbing
 too much our work? Here are the alternatives I see.

1. Separate the Selectors' part into a separate namespace. The oa 
namespace would be used for what is really annotation specific, and we
 could have the "select" (or whatever) namespace for the Selector 
class and all its subclasses. This change would affect only the RDF 
document, obviously, as well as the JSON-LD `@context` file. It would 
be invisible for the pure JSON-LD usage and document.
2. Separate the Selectors' section (essentially 4.2 in the current 
model document) into a document on its own. I believe that this is 
only really necessary for the separate JSON document, the RDF document
 can stay as it is if we also adopt (1) above (RDF people are used to 
using part different vocabularies or part of an existing vocabulary).
3. Define a fragment ID that reflects the current selectors.

I think that (1) and (2) are just minor editorial changes that we can 
do easily. The only downside of (1) is that it may be a strong 
departure from the Community Group document; I am not sure whether it 
is indeed a big issue.

What I meant for (3) is to define something like:

 is an",suffix="that has some") 

etc. It may be relatively easy to mechanically define these things 
based on the document we would produce anyway. However, it does raise 
issues related to the standard definition of fragment ID-s. However, 
even if we do not do it in this Working Group, by doing (1) and (2) we
 would facilitate other groups (Community or Working Groups) to pick 
this up.

Please view or discuss this issue at 
https://github.com/w3c/web-annotation/issues/110 using your GitHub 
Received on Friday, 20 November 2015 04:53:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:54:42 UTC