Skip to content

ET requirement: editor adds a preferred label #2

@jblom

Description

@jblom

It is possible that an editor wants to avoid using the label (rdfs:label) of a concept (i.e. annotation body) e.g:

The DBPedia concept http://de.dbpedia.org/resource/Turks was detected based on the word (label) "Turkse". The editor likes this concept, but wants this concept to be labeled "Turks (taal)" (in the front-end).

It was suggested that the ontology is extended with an (skos:)prefLabel to facilitate this requirement. Whenever querying for curated annotations, the client simply requests the prefLabel to get the curated label. (if it does not exist, the rdfs:label is used)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions