Chasing the Copy-Edit Use Case annotation

Doug Schepers <schepers@w3.org> Tue, Jun 16, 2015 at 11:59 PM:
-------------------------------------
Given this passage:

"The feeling that you are stupider than you were is what finally
interests you in the really complex subjects of life: in change, in
experience, in the ways other people have adjusted to disappointment
and narrowed ability. You realize that you are no prodigy, your
shoulders relax, and you begin to look around you, seeing local color
unrivaled by blue glows of algebra and abstraction.”
– Nicholson Baker, The Mezzanine

Let's pretend it's found at (the fictional URL):
 http://www.nicholsonbaker.com/TheMezzanine/

Let's further pretend that I'm Mr. Baker's editor, and strain the
bounds of credulity by supposing that my suggestion to change the word
"change" to something more grandiose is well-considered.

I select the word, and a little box pops up for my comment; I type,
"'Change' is a bit dry, why don't you punch it up a bit?", and select
the "suggest" option, which opens another text field for the
substitution text, in which I type, "transformation".

The annotation app represents this in the following JSON-LD:
ds:
{
  "@id": "http://example.org/anno1",
  "@type": "oa:Annotation",
  "body": [
    {
      "@id": "http://example.org/body1"
      "motivation": "oa:commenting",
      "value" : "'Change' is a bit dry, why don't you punch it up a bit?",
    },
    {
      "@id": "http://example.org/body2"
      "motivation": "oa:editing",
      "value" : "transformation",
    }
  ],
  "target": {
    "source": "http://www.nicholsonbaker.com/TheMezzanine/",
    "selector": {
      "@id": "http://example.org/selector1",
      "@type": "oa:TextQuoteSelector",
      "exact": "change",
      "prefix": "subjects of life: in ",
      "suffix": ", in experience, in t"
    }
  }
}

--------------------------------------------
This and a number of other examples suggest followup annotations, so why not
consider that *annotations are resources*. Using this approach, if we can think
of how the above example will be and we get sets of annotations.
(this is not to say we dont need multiple targets and multiple bodies,
but to say that this and the tweeting example of Doug maybe better
represented by annotating annotations).

Here is an attempt to split ds into an annotation set:

acset:  %annotation of a comment
{
 a1: {
  "@id": "http://example.org/anno1",
  "@type": "annotation",
  "body": [
    { "@id": "http://example.org/body1"
      "motivation": "comment",
      "value" : "'Change' is a bit dry, why don't you punch it up a bit?",
    }
  ],
  "target": {
    "source": "http://www.nicholsonbaker.com/TheMezzanine/",
    "selector": {
      "@id": "http://example.org/selector1",
      "@type": "oa:TextQuoteSelector",
      "exact": "change",
      "prefix": "subjects of life: in ",
      "suffix": ", in experience, in t"
    }
  }
 },
a2: {
  "@id": "http://example.org/anno1-1",
  "@type": "annotation",
  "body": [
    {
      "@id": "http://example.org/body2"
      "motivation": "edit",
      "value" : "transformation",
    }
  "target": a1.target
 }
}

OR equivalently?

aeset: %annotation of an edit (read as edit-suggestion)
{
 a1: {
  "@id": "http://example.org/anno1-1",
  "@type": "oa:Annotation",
  "body": [
    {
      "@id": "http://example.org/body2"
      "motivation": "edit",
      "value" : "transformation",
    }
  ],
  "target": {
    "source": "http://www.nicholsonbaker.com/TheMezzanine/",
    "selector": {
      "@id": "http://example.org/selector1",
      "@type": "oa:TextQuoteSelector",
      "exact": "change",
      "prefix": "subjects of life: in ",
      "suffix": ", in experience, in t"
    }
  }
 },
a2: {
  "@id": "http://example.org/anno1",
  "@type": "annotation",
  "body": [
  { "@id": "http://example.org/body1"
      "motivation": "comment",
      "value" : "'Change' is a bit dry, why don't you punch it up a bit?",
    },
  "target": a1.target
 }
}


a1.target persists as a robust identification of target through 1st
and 2nd annotation
and later as through before and after edit.

To start with we can claim that acset and aeset are functionally similar.

Then the edit-action may have a follow-up like:

ahset: %history of target
{ a1: ...,                                                 %% (same as above),
  a3: {
  "@id": "http://example.org/anno3",
  "@type": "oa:Annotation",
  "body": [
    {
      "@id": "http://example.org/body3"
      "motivation": "history",                       %% post-edit
(request is accepted)
      "value" : a1.value,
    }
  ],
  "target": {
    "source": "http://www.nicholsonbaker.com/TheMezzanine/",
    "selector": {
      "@id": "http://example.org/selector1",
      "@type": "oa:TextQuoteSelector",
      "exact": "transformation",                   %% post edit the
target is transformed for future needs
      "prefix": "subjects of life: in ",
      "suffix": ", in experience, in t"
    }
  }
 }
}

and we will be able to discuss/use sub-sets {a1.a2.a3} = acset + ahset

symbolically (need to polish) the above copy-edit use case maybe discussed as:

a4 comment a3, a3 history a2, a1 comment a1.target, a2 edit a1

assuming that the someone further comments after the edit (a3)

---

Is there a reason we do not think of annotations as specific resources?
I know Ivan talked about the problem of id-ing RDF triples, but in our
case the the "@id" of the annotation is the id of the triple. No?

-d

Received on Wednesday, 24 June 2015 10:48:29 UTC