Confusing about relation between meta data and annotations

[marcverhagen]

This is taken from a comment by Fazleh.

Sometimes metadata information of view and annotation in LIF do not match. In the metadata we can have

"metadata": {
   "contains": {
      "http://vocab.lappsgrid.org/Token#pos": {
         "producer": "edu.brandeis.cs.uima.dkpro.StanfordNlpPOSTagger:0.0.1-SNAPSHOT",
         "type": "postagger:dkpro_stanford"   }}}

but the annotations look like

{  
   "@type": "http://vocab.lappsgrid.org/Token",
   "id": "40",
   "start": 25,
   "end": 28,
   "features": { "word": "was",  "pos": "VBD" }}

Fazleh remarked that

The metadata information in view (http://vocab.lappsgrid.org/Token#pos) is correct but in annotation it is not the same (http://vocab.lappsgrid.org/Token)

This is actually correct, but confusing nevertheless. The meta data says that the view contains pos attributes on the Token annotation elements. The @type attribute refers to the type of the annotation element, which is a Token. Since the meta data uses Token#pos we know that the features dictionary of the Token is supposed to have a value for the pos attribute, we do not have an explicit mechanism to map the attribute directly to a type.

Update the LIF specifications so this is clear.

[keighrim]

Just to clarify, is this a suggestion for the @type in the above example to be replaced with"http://vocab.lappsgrid.org/Token#pos" in line with the metadata? Or is this issue about updating the documentation to warn about this (possibly) confusing notation?

[marcverhagen]

As far as I am concerned this is not about changing the @type in the annotation, since the type really is expressed at the annotation element level, which is the Token. It is about updating the documentation. So I have assigned myself to it.

[ksuderman]

I will need to check our taggers here at Vassar, I believe some of them may (incorrectly) set the @type to http://.../Token#pos