8000 SpecificResource instead of TextualBody when using tag URI · Issue #94 · recogito/recogito-client-core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
SpecificResource instead of TextualBody when using tag URI #94
Closed
@LvanWissen

Description

@LvanWissen

Currently, if you use a vocabulary that includes URIs for tags in the tag widget, they are added as instances of TextualBody in the annotation data. Example of some parts I used in Recogito-JS:

  myVocab = [
      {
        label: "material",
        uri: "http://vocab.getty.edu/aat/300010358",
      }
  ]

  const r = new Recogito({
    widgets: [
      {
        widget: "TAG",
        vocabulary: myVocab,
      },
    ],
   // etc.
  });
  {
    "type": "TextualBody",
    "value": "material",
    "purpose": "tagging",
    "source": "http://vocab.getty.edu/aat/300010358"
  }

But, according to the Web Annotation Model (https://www.w3.org/TR/annotation-model/, see under "4.1 Purpose for External Web Resources") this is a SpecificResource, since an external URI is used as source value. The body should therefore be:

  {
    "type": "SpecificResource",
    "value": "material",
    "purpose": "tagging",
    "source": "http://vocab.getty.edu/aat/300010358"
  }

Or is it an option to make such a body both a TextualBody (to keep the value) as well as a SpecificResource (for the source)?

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    0