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

Re: ITS 2.0 example in web annotation

From: Felix Sasaki <fsasaki@w3.org>
Date: Thu, 19 Nov 2015 09:06:45 +0100
Cc: W3C Public Annotation List <public-annotation@w3.org>, Benjamin Young <bigbluehat@hypothes.is>, Paolo Ciccarese <paolo.ciccarese@gmail.com>
Message-Id: <11592077-7071-4B3A-906B-A89A8BF3B5E6@w3.org>
To: Ivan Herman <ivan@w3.org>
Thank you for the feedback, Ivan. Would it help to add e.g. a motivation, e.g. see below:

{
"@id": "http://example.com/myannotations/a1",
"@type": "Annotation",
"target": {
"source": "http://example.com/myfile.xml",
"selector": {
"@type": "FragmentSelector",
"conformsTo": "http://www.w3.org/TR/xpath/",
"value": "/itsProcessingInput"
}
},
"body": {
"motivation": "tagging",
"itsrdf:translate": "yes",
"itsrdf:dir": "ltr",
"itsrdf:withinText": "no",
"itsrdf:term": "no",
"itsrdf:localeFilterList": "*",
"itsrdf:localeFilterType": "included"
}
}


„tagging“ could be seen as subsuming all ITS related annotations.

- Felix

> Am 19.11.2015 um 06:30 schrieb Ivan Herman <ivan@w3.org>:
> 
> Felix, others,
> 
> I just try to locate where the problem might be when combining it with the annotation model…
> 
> The json file, whether seen as pure JSON  (JSON-LD) is technically correct. However, if the annotation gets into a special annotation system, that may find itself in an edge case: indeed, the body of the annotation does not use any of the properties that are defined in the annotation model. We would have to check whether there is any constraints defined in the model whereby certain things must be present ('content', etc). But systems might still fall over on such edge cases… Benjamin, Paolo, what would your annotation server do?
> 
> Thanks
> 
> Ivan
> 
> 
>> On 12 Nov 2015, at 19:52, Felix Sasaki <fsasaki@w3.org <mailto:fsasaki@w3.org>> wrote:
>> 
>> Following the meeting at TPAC and the discussion we had recently on this list, I created an example of how a set of ITS 2.0 information stored following the web annotation data model could look like:
>> 
>> 1) Counterpart of web annotation: storage of ITS information as markup in the XML document itself (note that the annotated document is an XML document):
>> https://github.com/w3c/itsrdf/blob/master/its-in-markup.xml <https://github.com/w3c/itsrdf/blob/master/its-in-markup.xml>
>> 2) Storage using the web annotation model:
>> https://github.com/w3c/itsrdf/blob/master/its-via-web-annotation.json <https://github.com/w3c/itsrdf/blob/master/its-via-web-annotation.json>
>> (I decided to use the FragmentSelector)
>> 
>> Feedback of course more than welcome. 
>> 
>> - Felix
> 
> 
> ----
> Ivan Herman, W3C 
> Digital Publishing Lead
> Home: http://www.w3.org/People/Ivan/ <http://www.w3.org/People/Ivan/>
> mobile: +31-641044153
> ORCID ID: http://orcid.org/0000-0003-0782-2704 <http://orcid.org/0000-0003-0782-2704>
> 
> 
> 
> 


Received on Thursday, 19 November 2015 08:07:18 UTC

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