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

Re: Question on annotation of HTML content

From: Robert Sanderson <azaroth42@gmail.com>
Date: Fri, 6 Nov 2015 10:56:13 -0800
Message-ID: <CABevsUGvDpypQWvB0JwUKAfJKJdrkH_UcpaZ5JZKiXPwsEgT2w@mail.gmail.com>
To: Ivan Herman <ivan@w3.org>
Cc: Felix Sasaki <fsasaki@w3.org>, W3C Public Annotation List <public-annotation@w3.org>
I don't *disagree* but I'm not sure that it's the best way either, as the
interpretation is ambiguous as to what should not be translated.

To add an explicit id to the body, another property and anonymize the
itsrdf assertion:

{
  "body": {
    "id": "_:b0",
    "format": "text/plain",
    "some:property": "some value"
  }
}

The property and value are about the body, not about the target, just like
format is.  Now if you put back the translate: no ... you would be saying
not to translate the body. However, you want to say that the *target*
should not be translated.

In natural language you would do:

{
  "body": {
    "format": "text/plain",
    "content": "This string should not be translated"
  }
}

So in machine readable form, you could say:

{
  "body": {
    "format": "text/turtle",
    "content": "<uri-of-specific-resource> itsrdf:translate \"no\" . "
  }
}

Does that help?

Rob


On Fri, Nov 6, 2015 at 8:32 AM, Ivan Herman <ivan@w3.org> wrote:

> Hm.
>
> I believe that, in fact, what you wrote is almost correct as it is,
> provided that you have added an additional context for that namespace. Ie,
> in terms of JSON-LD, what you would do is:
>
> {
> "@context" :  [
> "http://www.w3.org/ns/anno.jsonld",
> {
> "itsrdf" : "http://www.w3.org/2005/11/its/rdf#"
> }
> ],
> "target" : "A URI TO THE TARGET",
>         "body" : {
> "itsrdf:translate" : "no"
>         }
> }
>
> The trick is that JSON-LD allows multiple contexts to be mixed in. I
> believe that should be a bona fide (albeit unusual) annotation in the
> model, but maybe Rob will disagree.
>
> However, if it actually *is* a correct annotation, we may want to call out
> this type of example somewhere in the document… Annotations may want to use
> terms from other vocabularies after all…
>
> Ivan
>
>
>
> On 6 Nov 2015, at 17:07, Felix Sasaki <fsasaki@w3.org> wrote:
>
>
> Am 06.11.2015 um 16:31 schrieb Ivan Herman <ivan@w3.org>:
>
>
> On 6 Nov 2015, at 15:35, Felix Sasaki <fsasaki@w3.org> wrote:
>
> Hello all,
>
> apologies for this newbie question. I am looking for an example of
> annotating HTML content. Imagine I have the following document:
>
> <!DOCTYPE html>
> <html lang="en">
> <head>
>   <meta charset="utf-8">
>   <title>some html doc</title>
>
> </head>
> <body>
>  <p>Welcome to <strong>Berlin</strong>!</p>
> </body>
> </html>
>
> I want to create an annotation that uses the web annotation model, uses a
> text selector for the string „Berlin“ and adds an annotation body
> containing a triple with the „translate“ predicate from the ITS 2.0
> ontology, see
>
> http://www.essepuntato.it/lode/https://raw.githubusercontent.com/w3c/itsrdf/master/its-rdf.rdf#d4e52
> expressing that the string should not be translated. How would this look
> like?
>
>
> I am not sure what you intend to do. Do you mean that the target should be
> a graph containing a specific triple?
>
>
>
> the target should be a selector selecting the string „Berlin“. The
> annotation body should contain a tripe like
>
> "body": {
>
> "itsrdf:translate" : "no",
>
> … }
>
> So I am wondering how to express this target and how the body should look
> like.
>
> - Felix
>
>
>
> Ivan
>
>
>
> Thanks for the feedback in advance,
>
> Felix
>
>
>
> ----
> Ivan Herman, W3C
> Digital Publishing 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 Lead
> Home: http://www.w3.org/People/Ivan/
> mobile: +31-641044153
> ORCID ID: http://orcid.org/0000-0003-0782-2704
>
>
>
>
>


-- 
Rob Sanderson
Information Standards Advocate
Digital Library Systems and Services
Stanford, CA 94305
Received on Friday, 6 November 2015 18:56:41 UTC

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