Fork me on GitHub

JSKOS data format for Knowledge Organization Systems

Jakob Voß

2023-07-03 (version 0.5.1)

Table of Contents

1 Introduction

JSKOS (JavaScript Object Notation for Simple Knowledge Organization Systems) defines a JavaScript Object Notation (JSON) structure to encode knowledge organization systems (KOS), such as classifications, thesauri, and authority files. JSKOS supports encoding of concepts, concept schemes, concept occurrences, and concept mappings with their common properties. It further defines application profiles for registries, distributions, and annotations. See object types for an outline.

The main part of JSKOS is compatible with Simple Knowledge Organisation System (SKOS) and JavaScript Object Notation for Linked Data (JSON-LD) but JSKOS can be used without having to be experienced in any of these technologies. A simple JSKOS document can be mapped to SKOS expressed in the Resource Description Framework (RDF), and vice versa. JSKOS further supports closed world statements to express incomplete information about knowledge organization systems to facilitate use in dynamic web applications.

1.1 Status of this document

JSKOS is currently being developed as part of project coli-conc. The JSKOS specification is hosted at http://gbv.github.io/jskos/ in the public GitHub repository https://github.com/gbv/jskos. Feedback is appreciated! See https://github.com/gbv/jskos/issues for a list of open issues.

1.2 Conformance requirements

The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119.

2 Data types

JSKOS is based on JSON which consists of objects with pairs of fields and values, arrays with members, strings, numbers, and the special values true, false, and null. All strings and fields of a JSKOS document MUST be normalized to Unicode Normalization Form C (NFC). Applications processing JSON MAY accept JSON documents not normalized in NFC by performing NFC normalization. JSKOS further restricts JSON with reference to the following data types:

2.1 URI

An URI is a syntactically correct IRI (RFC 3987).

2.2 URL

An URL is a syntactically correct URL with HTTPS (RECOMMENDED) or HTTP scheme. Note that URLs can contain international characters allowed in IRIs.

2.3 Non-negative integer

A non-negative integer is a JSON number without preceding minus part, without fractional part, or exponent.

Examples of valid JSON values which are not non-negative integers: "42", "", null, -1, 6e-3.

2.4 percentage

A percentage is a JSON number with value between zero (0.0 = 0%) and one (1.0 = 100%).

2.5 date

A date is a date or datetime as defined with XML Schema datatype datetime (-?YYYY-MM-DDThh:mm:ss(\.s+)?(Z|[+-]hh:mm)?) date (-?YYYY-MM-DD(Z|[+-]hh:mm)?), gYearMonth (-?YYYY-MM), or gYear (-?YYYY).

2.6 list

A list is a possibly empty array of strings and an optional last member null. Applications MAY ignore or disallow the value null in lists. If null is allowed, lists MUST be interpreted as following to support closed world statements:

A list MUST NOT contain the empty string except if part of a language map.

2.7 set

A set is a possibly empty array where all members

Member objects SHOULD have a field uri. Applications MAY restrict sets to require the field uri for all non-null members. Applications MAY ignore or disallow the value null in sets. If null is allowed, sets MUST be interpreted as following to support closed world statements:

The following JSON values are JSKOS sets:

  • []
  • [null]
  • [{"uri":"http://example.org/123"}]
  • [{"uri":"http://example.org/123"},null]
  • [{"uri":"http://example.org/123"},{"uri":"http://example.org/456"}]
  • [{"uri":"http://example.org/123"},{"notation":["xyz"]}]

The following JSON values are not valid JSKOS sets:

  • [null,{"uri":"http://example.org/123"}]
    (null only allowed as last member)
  • [{"uri":"http://example.org/123"},{"uri":"http://example.org/123"}]
    (field uri must be unique)

It is not defined yet whether and when the order of elements is relevant or not.

2.8 language range

A language range is

A language range “x-”, where x is a possibly empty string, refers to the set of RFC 3066 language tags that start the string x. For instance language range en- includes language tag en, en-US, and en-GB among others. The language range - refers to all possible language tags.

A language range MUST conform to the following ABNF grammar (RFC 5234):

language-range = [language-tag] "-"
language-tag   = 1*8alpha *("-" 1*8(alpha / DIGIT))
alpha          = %x61-7A  ; a-z

JSKOS language ranges can be mapped to and from basic language ranges as defined in RFC 4647. The main difference of JSKOS language ranges is they can be distinguished from RFC 3066 based on their string value (always ending with “-”). For instance “en” could be an RFC 3066 language tag or a [RFC 3647] language range but in JSKOS it is always a language tag only:

JSKOS RFC 3066 RFC 4647
language tag for English en en
languag range for all English variants en- en

2.9 language map

A language map is a JSON object in which every fields is

and

and

Applications MAY ignore or disallow language ranges in language maps. JSKOS data providers SHOULD make clear whether their data can contain language ranges or not.

If language ranges are allowed, language maps MUST be interpreted as following to support closed world statements:

The following language maps make use of language ranges and placeholders:

  • {"-":""}, {"-":""}, {"-":[]}, and {"-":[""]} all denote non-empty language maps with unknown language tags and values.

  • {"en":"bird","-":""} denotes a language map with an English value and additional values in other language tags.

  • {"en":"bird"} denotes a language map with an English value only.

  • {"en-":""} denotes a language map that only contains values with language tags starting with en.

JSON-LD disallows language map fields ending with "-" so all fields that are language ranges MUST be removed before reading JSKOS as JSON-LD.

The language tag “und” can be used to include strings of unknown or unspecified language.

2.10 location

A location is a JSON object conforming to the GeoJSON specification (RFC 7946) with GeoJSON type being one of Point, MultiPoint, LineString, MultiLineString, Polygon, or MultiPolygon. Applications MAY restrict the location data type to GeoJSON objects of GeoJSON type Point.

Position of the RMS Titanic as point:

{
  "type": "Point",
  "coordinates": [-49.946944, 41.7325, -3803]
}

2.11 address

An address is a JSON object with any of the following field, each mapped to a string:

field description
street the street address
ext the extended address (e.g., apartment or suite number)
pobox the post office box
locality the locality (e.g., city)
region the region (e.g., state or province)
code the postal code
country the country name

2.12 checksum

A checksum is a JSON object with two fields:

field type description
algorithm URI checksum algorithm
value string lower case hexidecimal encoded digest value

The value of SHOULD be specified by a URI from SPDX vocabulary, e.g. http://spdx.org/rdf/terms#checksumAlgorithm_sha256 for SHA-2 with 256 Bit (SHA-256).

2.13 media

A media is a reference to digital content such as images or other audiovisual data. The data model of JSKOS media follows the manifest resource type of IIIF Presentation API 3.0.

A media is a JSON object with at least the following fields:

field type description
type string the value “Manifest”
items array list of IIIF Canvas objects

Additional properties MUST follow the IIIF Presentation API specification. In contrast to IIIF, the fields label and id are not required but RECOMMENDED by JSKOS. JSKOS applications MAY limit the set of supported fields instead of fully implementing all IIIF capabilities.

For example a thumbnail image can be specified as media like this:

{
  "type": "Manifest",
  "items": [],
  "thumbnail": [
    {
      "type": "Image",
      "id": "http://example.org/1/thumbnail.jpg",
      "format": "image/jpeg"
    }
  ]
}

3 Object types

JSKOS defines the following types of JSON objects:

In addition there are concept bundles as part of mappings, occurrences, and composed concepts.

3.1 Resource

An resource is a JSON object with the following optional fields:

field type description
@context URI reference to a JSON-LD context document
uri URI primary globally unique identifier
identifier list additional identifiers
type list of URIs URIs of types
created date date of creation
issued date date of publication
modified date date of last modification
creator set agent primarily responsible for creation of resource
contributor set agent responsible for making contributions to the resource
source set sources from which the described resource is derived
publisher set agent responsible for making the resource available
partOf set resources which this resource is part of (if no other field applies)

It is RECOMMENDED to always include the fields uri, type, and @context. The value of field @context SHOULD be https://gbv.github.io/jskos/context.json.

Resources can be tested for sameness based on field uri.

3.2 Item

An item is a resource with the following optional fields (in addition to the optional fields @context, contributor, created, creator, identifier, issued, modified, partOf, publisher, source, type, and uri):

field type description
url URL URL of a page with information about the item
notation list list of notations
prefLabel language map of strings preferred labels, index by language
altLabel language map of list alternative labels, indexed by language
hiddenLabel language map of list hidden labels, indexed by language
scopeNote language map of list see SKOS Documentary Notes
definition language map of list see SKOS Documentary Notes
example language map of list see SKOS Documentary Notes
historyNote language map of list see SKOS Documentary Notes
editorialNote language map of list see SKOS Documentary Notes
changeNote language map of list see SKOS Documentary Notes
note language map of list see SKOS Documentary Notes
startDate date date of birth, creation, or estabishment of the item
endDate date date death or resolution of the item
relatedDate date other date somehow related to the item
startPlace set where an item started (e.g. place of birth)
endPlace set where an item ended (e.g. place of death)
place set other relevant place(s) of the item
location location geographic location of the item
address address postal address of the item
subject set what this item is about (e.g. topic)
subjectOf set resources about this item (e.g. documentation)
depiction list of URL list of image URLs depicting the item
media list of media audiovisual or other digital content representing the item

Applications MAY limit the fields notation and/or depiction to lists of a single element or ignore all preceding elements of these lists.

3.3 Concept

A concept is an item and concept bundle with the following optional fields (in addition to the optional fields @context, address, altLabel, changeNote, contributor, created, creator, definition, depiction, editorialNote, endDate, endPlace, example, hiddenLabel, historyNote, identifier, issued, location, modified, notation, note, partOf, place, prefLabel, publisher, scopeNote, source, startDate, startPlace, subjectOf, subject, type, uri, url, memberSet, memberList, memberChoice, and memberRoles):

field type description
narrower set narrower concepts
broader set broader concepts
related set generally related concepts
previous set related concepts ordered somehow before the concept
next set related concepts ordered somehow after the concept
ancestors set list of ancestors, possibly up to a top concept
inScheme set of concept schemes concept schemes the concept belongs to
topConceptOf set of concept schemes concept schemes the concept is a top concept of
mappings set of mappings mappings from and/or to this concept
occurrences set of occurrences occurrences with this concept

The first element of field type, if given, MUST be the item type URI http://www.w3.org/2004/02/skos/core#Concept.

Applications MAY limit the inScheme and/or topConceptOf to sets of a single element or ignore all but one element of these sets.

If both fields broader and ancestors are given, the set broader MUST include the same concept as the first element of ancestors.

The concept bundle fields memberSet, memberList, memberChoice, and memberRoles can be used to express the parts of a composed concept (also known as combined or synthesized concepts) unsorted or sorted. The field memberChoice SHOULD NOT be used without proper documentation because its meaning in this context is unclear. A concept MUST NOT include more than one of concept bundle fields. A concept SHOULD NOT reference itself as part of its concept bundle.

The “ancestors” field is useful in particular for monohierarchical classifications but it’s not forbidden to choose just one arbitrary path of concepts that are connected by the broader relation.

{
  "uri": "http://example.org/terminology/P",
  "type": ["http://www.w3.org/2004/02/skos/core#Concept"],
  "scopeNote": {
    "en": ["state of harmony characterized by lack of violent conflict and freedom from fear of violence"],
    "de": ["Abwesenheit von Gewalt, Angst und anderen Störungen"]
  },
  "prefLabel": {
    "en": "peace",
    "de": "Frieden"
  },
  "altLabel": {
    "de": ["Friede"]
  },
  "notation": ["P"],
  "narrower": [
    {
      "prefLabel": {
        "en": "world peace",
        "de": "Weltfrieden"
      } 
    }
  ],
  "related": [
    { 
      "prefLabel": { "en": "war", "de": "Krieg" } 
    }
  ]
}
{
  "uri": "http://d-nb.info/gnd/7507432-1",
  "prefLabel": { "de": "Drei-Sektoren-Hypothese" },
  "memberSet": [
    { 
      "uri": "http://d-nb.info/gnd/4126823-4",
      "prefLabel": { "de": "Sektoraler Strukturwandel" }
    },
    {
      "uri": "http://d-nb.info/gnd/4161152-4",
      "prefLabel": { "de": "Hypothese" }
    }
  ]
}
{
  "notation": [ "305.40941109033" ],
  "prefLabel": { "en": "Women — Scotland — 18th century" },
  "memberList": [
    {
      "uri": "http://dewey.info/class/305.4/e23/",
      "notation": ["305.4"],
      "prefLabel": { "en": "Women" }
    },
    {
      "uri": "http://dewey.info/class/2--411/e23/",
      "notation": ["T2--411"],
      "prefLabel": { "en": "Scotland" }
    },
    {
      "uri": "http://dewey.info/class/1--09033/e23/",
      "notation": ["T1--09033"],
      "prefLabel": { "en": "18th century, 1700-1799" }
    }
  ]
}

3.4 Concept Schemes

A concept scheme is an item with the following optional fields (in addition to the optional fields @context, address, altLabel, changeNote, contributor, created, creator, definition, depiction, editorialNote, endDate, endPlace, example, hiddenLabel, historyNote, identifier, issued, location, modified, notation, note, partOf, place, prefLabel, publisher, scopeNote, source, startDate, startPlace, subjectOf, subject, type, uri, and url):

property type definition
topConcepts set of concepts top concepts of the scheme
versionOf set of concept schemes concept scheme which this scheme is a version or edition of
namespace URI URI namespace that all concepts URIs are expected to start with
uriPattern string regular expression that all concept URIs are expected to match
notationPattern string regular expression that all primary notations should follow
notationExamples list of string list of some valid notations as examples
concepts set of concepts concepts in the scheme
types set of concepts concept types of concepts in this scheme
distributions set of distributions Distributions to access the content of the concept scheme
extent string Size of the concept scheme
languages list of language tags Supported languages
license set Licenses which the full scheme can be used under

The first element of field type, if given, MUST be the item type URI http://www.w3.org/2004/02/skos/core#ConceptScheme.

The value of field uriPattern MUST conform to the regular expression syntax used by XML Schema (Appendix F) and be anchored with ^ as first character.

If concepts is a set, all its member concepts SHOULD contain a field inScheme and all MUST contain the same concept scheme in field inScheme if this field is given.

If types and concepts are sets, the types set SHOULD include all concept types for each concept’s type other than http://www.w3.org/2004/02/skos/core#Concept.

3.5 Concept Occurrences

An occurrence is a resource and concept bundle with the following optional fields (in addition to the optional fields @context, contributor, created, creator, identifier, issued, modified, partOf, publisher, source, type, uri, memberSet, memberList, memberChoice, and memberRoles):

field type definition
count non-negative integer number of times the concepts are used
database item database in which the concepts are used
frequency percentage count divided by total number of possible uses
relation URI type of relation between concepts and entities
url URL URL of a page with information about the occurrence

An occurrence gives the number of a times a concept (“occurrence”) or combination of concepts (“co-occurrence”) is used in a specific relation to entities from a particular database. For instance the occurrence could give the number of documents indexed with some term in a catalog. The field url typically includes a deep link into the database.

If both count and frequency are given, the total size of the database can derived by multiplication. In this case either both or none of the two fields MUST be zero.

A timestamp, if given, should be stored in field modified.

The actual concept or concepts MAY be given implictly, for instance if the occurrence is part of a concept in field occurrences.

Two occurrences and their combined co-occurrence from GBV Union Catalogue (GVK) as of November 22th, 2017: 3657 records are indexed with class 08.22 (medieval philosophy) from Basisklassifikation, 144611 with DDC notation 610 (Medicine & health) and 2 records with both.

[
  {
    "database": { "uri": "http://uri.gbv.de/database/gvk" },
    "memberSet": [
      {
        "uri": "http://uri.gbv.de/terminology/bk/08.22",
        "prefLabel": { "de": "Mittelalterliche Philosophie" }
      }
    ],
    "count": 3657,
    "modified": "2017-11-22",
    "url": "https://gso.gbv.de/DB=2.1/CMD?ACT=SRCHA&IKT=1016&SRT=YOP&TRM=bkl+08.22"
  },
  {
    "database": { "uri": "http://uri.gbv.de/database/gvk" },
    "memberSet": [
      {
        "uri": "http://dewey.info/class/610/e23/",
        "prefLabel": { "en": "Medicine & health" }
      }
    ],
    "count": 144611,
    "modified": "2017-11-22",
    "url": "https://gso.gbv.de/DB=2.1/CMD?ACT=SRCHA&IKT=1016&SRT=YOP&TRM=ddc+610"
  },
  {
    "database": { "uri": "http://uri.gbv.de/database/gvk" },
    "memberSet": [
      { "uri": "http://uri.gbv.de/terminology/bk/08.22" },
      { "uri": "http://dewey.info/class/610/e23/" }
    ],
    "count": 2,
    "modified": "2017-11-22",
    "url": "https://gso.gbv.de/DB=2.1/CMD?ACT=SRCHA&IKT=1016&SRT=YOP&TRM=bkl+08.22+ddc+610"
  }
]

The Wikidata concept of an individual human is linked to 206 Wikimedia sites (mostly Wikipedia language editions) and more than 3.7 million people (instances of http://www.wikidata.org/entity/P31) at November 15th, 2017.

{
  "type": ["http://www.w3.org/2004/02/skos/core#Concept"],
  "uri": "http://www.wikidata.org/entity/Q5",
  "prefLabel": { "en": "human" },
  "occurrences": [
    {
      "relation": "http://schema.org/about",
      "count": 206,
      "modified": "2017-11-15T14:00:58.796Z"
    },
    {
      "relation": "http://www.wikidata.org/entity/P31",
      "count": 3706347,
      "modified": "2017-11-15T14:00:58.796Z"
    }
  ]
}

3.6 Registries

A registry is an item with the following optional fields (in addition to the optional fields @context, address, altLabel, changeNote, contributor, created, creator, definition, depiction, editorialNote, endDate, endPlace, example, hiddenLabel, historyNote, identifier, issued, location, modified, notation, note, partOf, place, prefLabel, publisher, scopeNote, source, startDate, startPlace, subjectOf, subject, type, uri, and url):

field type definition
concepts set of concepts concepts in this registry
schemes set of concept schemes concept schemes in this registry
types set of concepts concept types in this registry
mappings set of mappings mappings in this registry
registries set of registries other registries in this registry
concordances set of concordances concordances in this registry
occurrences set of occurrences occurrences in this registry
extent string Size of the registry
languages list Supported languages
license set Licenses which the full registry content can be used under

The first element of field type, if given, MUST be the item type URI http://purl.org/cld/cdtype/CatalogueOrIndex.

Registries are collection of concepts, concept schemes, concept types, concept mappings, and/or other registries.

Registries are the top JSKOS entity, followed by concordances, mappings, and on the lowest level concepts and concept types. See Distributions for an alternative.

Additional integrity rules for registries will be defined.

3.7 Distributions

A distribution is an item with the following fields (in addition to the optional fields @context, address, altLabel, changeNote, contributor, created, creator, definition, depiction, editorialNote, endDate, endPlace, example, hiddenLabel, historyNote, identifier, issued, location, modified, notation, note, partOf, place, prefLabel, publisher, scopeNote, source, startDate, startPlace, subjectOf, subject, type, uri, and url):

Distributions mostly cover the class Distribution from Data Catalog Vocabulary.

property type definition
download URL location of a file with distribution content in given format
accessURL URL URL of an API or landing page to retrieve the distribution content
format URI data format identifier of the distribution content
mimetype URI or string Internet Media Type (also known as MIME type)
compressFormat URI compression format of the distribution
packageFormat URI packaging format when multiple files are grouped together
license set license which the data can be used under
size string Size of a distribution in bytes or literal such as “1.5 MB”
checksum checksum Checksum of the download (algorithm and digest value)

The format field SHOULD reference a content format rather than its serialization and possible wrapping. The URI of JSKOS is http://format.gbv.de/jskos.

Fields mimetype, compressFormat, and packageFormat SHOULD be IANA media type URIs, if available. Field mimetype MAY be a string for backwards-compatibility.

The first element of field type, if given, MUST be the item type URI http://www.w3.org/ns/dcat#Distribution.

Access to concept schemes and concordances can also be specified with fields concepts, types, and mappings, respectively. Distributions provide an alternative and extensible method to express access methods.

Distribution of a newline-delimited JSKOS file:

{
  "download": "http://example.org/data/dump.ndjson",
  "mimetype": "application/x-ndjson",
  "format": "http://format.gbv.de/jskos"
}

Distribution of a RDF/XML with SKOS data:

{
  "prefLabel": { "en": "SKOS in RDF/XML" },
  "download": "http://example.org/data/dump.rdf",
  "mimetype": "application/rdf+xml",
  "format": "http://www.w3.org/2004/02/skos/core"
}

Distribution of a gzip-compressed MARC/XML file in MARC 21 Format for Authority Data:

{
  "download": "http://example.org/data/dump.xml.gz",
  "mimetype": "application/xml",
  "format": "http://format.gbv.de/marc/authority",
  "compressFormat": "http://www.iana.org/assignments/media-types/application/gzip"
}

3.8 Concordances

A concordance is an item with the following fields (in addition to the optional fields @context, address, altLabel, changeNote, contributor, created, creator, definition, depiction, editorialNote, endDate, endPlace, example, hiddenLabel, historyNote, identifier, issued, location, modified, notation, note, partOf, prefLabel, publisher, scopeNote, source, startDate, startPlace, subjectOf, subject, type, uri, and url). All fields except fromScheme and toScheme are optional.

property type definition
mappings set of mappings mappings in this concordance
distributions set of distributions distributions to access the concordance
fromScheme concept scheme Source concept scheme
toScheme concept scheme Target concept scheme
extent string Size of the concordance
license set License which the full concordance can be used under

The first element of field type, if given, MUST be the item type URI http://rdfs.org/ns/void#Linkset.

Concordances are collections of mappings from one concept scheme to another. If mappings is a set then

There is an additional integrity constraint refering to field inScheme if concepts in mappings in concordances.

3.9 Concept Mappings

A mapping is an item with the following fields (in addition to the optional fields @context, address, altLabel, changeNote, contributor, created, creator, definition, depiction, editorialNote, endDate, endPlace, example, hiddenLabel, historyNote, identifier, issued, location, modified, notation, note, partOf, prefLabel, publisher, scopeNote, source, startDate, startPlace, subjectOf, subject, type, uri, and url). All fields except from and to are optional.

field type definition
from concept bundle concepts mapped from
to concept bundle concepts mapped to
fromScheme concept scheme source concept scheme
toScheme concept scheme target concept scheme
mappingRelevance number numerical value between 0 and 1 (experimental)

A mapping represents a mapping between concepts of two concept schemes. It consists two concept bundles with additional metadata not fully defined yet.

The first element of field type, if given, MUST be one of the item types

from SKOS mapping properties. The field type MAY contain additional values but MUST NOT contain multiple of these values.

When mappings are dynamically created it can be useful to assign a non-HTTP URI such as urn:uuid:687b973c-38ab-48fb-b4ea-2b77abf557b7.

Applications MAY use concept mappings to derive simple statements with SKOS Mapping Properties but SKOS integrity rules for mappings do not apply automatically.

3.10 Concept Bundles

A concept bundle is a group of concepts. Concept bundles can be used for mappings, composed concepts, and occurrences.

A concept bundle is a JSON object with at most one of the following fields:

field type definition
memberSet set of concepts concepts in this bundle (unordered)
memberList ordered set of concepts concepts in this bundle (ordered)
memberChoice set of concepts concepts in this bundle to choose from
memberRoles object Object mapping role URIs to sets of concepts

Keys of a memberRoles object MUST be URIs and their values MUST be of type set.

{
  "prefLabel": { "en": "knights armor"},
  "memberRoles": {
    "http://example.org/personality": [
      { "prefLabel": { "en": "knight" } }
    ],
    "http://example.org/matter": [
      { "prefLabel": { "en": "workwear" } }
    ],
    "http://example.org/energy": [
      { "prefLabel": { "en": "fight" } }
    ],
    "http://example.org/time": [
      { "prefLabel": { "en": "Middle Ages" } }
    ]
  }
}
  • Concept bundles could also be used for SKOS concept collections, see https://github.com/gbv/jskos/issues/7 for discussion.

  • Concepts from a bundle may also come from different concept schemes!

  • A concept bundle may be empty, for instance to indicate that no appropriate concepts exists for a given concept scheme:

    {
      ...
      "to": { "memberSet": [] },
      "toScheme": {"uri": "http://dewey.info/scheme/ddc/"}
    }

Normalization rules may be added to prefer one kind of expressing an empty concept bundle.

3.11 Annotations

An annotation links a JSKOS resource or another annotation with a review, comment or similar document. An annotation is a JSON object that conforms to the Web Annotation Data Model and further contains the following fields as defined:

field type definition
@context URL the value http://www.w3.org/ns/anno.jsonld
type string the value Annotation
id URI globally unique identifier of the annotation
target URI, Resource or Annotation object being annotated, or its URI

4 Item and concept types

An item type is an URI used to distinguish the different kinds of JSKOS items:

item item type
concept http://www.w3.org/2004/02/skos/core#Concept
concept scheme http://www.w3.org/2004/02/skos/core#ConceptScheme
registry http://purl.org/cld/cdtype/CatalogueOrIndex
distribution http://www.w3.org/ns/dcat#Distribution
concordance http://rdfs.org/ns/void#Linkset
mapping http://www.w3.org/2004/02/skos/core#mappingRelation and sup-properties

A concept type is concept used to distinguish different kinds of concepts or other resources. Concept types are referred to by their URI in field type of a resource.

Item types MAY be expressed with the following concept types:

[
  {
    "uri": "http://www.w3.org/2004/02/skos/core#Concept",
    "prefLabel": { "en": "concept" }
  },
  {
    "uri": "http://www.w3.org/2004/02/skos/core#ConceptScheme",
    "prefLabel": { "en": "concept scheme" }
  },
  {
    "uri": "http://purl.org/cld/cdtype/CatalogueOrIndex",
    "prefLabel": { "en": "registry" },
    "altLabel": { "en": [ "catalog", "Catalogue or Index" ] }
  },
  {
    "uri": "http://www.w3.org/ns/dcat#Distribution",
    "prefLabel": { "en": "distribution" }
  },
  {
    "uri": "http://rdfs.org/ns/void#Linkset",
    "identifier": [
      "http://purl.org/spar/fabio/VocabularyMapping",
      "http://rdf-vocabulary.ddialliance.org/xkos#Correspondence"
    ],
    "prefLabel": { "en": "concordance" },
    "altLabel": { "en": [ "linkset" ] }
  },
  {
    "uri": "http://www.w3.org/2004/02/skos/core#mappingRelation",
    "prefLabel": { "en": "is in mapping relation with" }
  },
  {
    "uri": "http://www.w3.org/2004/02/skos/core#closeMatch",
    "prefLabel": { "en": "has close match" },
    "broader": [ { "uri": "http://www.w3.org/2004/02/skos/core#mappingRelation" } ]
  },
  {
    "uri": "http://www.w3.org/2004/02/skos/core#exactMatch",
    "prefLabel": { "en": "has exact match" },
    "broader": [ { "uri": "http://www.w3.org/2004/02/skos/core#closeMatch" } ]
  },
  {
    "uri": "http://www.w3.org/2004/02/skos/core#broadMatch",
    "prefLabel": { "en": "has broader match" },
    "broader": [ { "uri": "http://www.w3.org/2004/02/skos/core#mappingRelation" } ],
    "related": [ { "uri": "http://www.w3.org/2004/02/skos/core#narrowMatch" } ]
  },
  {
    "uri": "http://www.w3.org/2004/02/skos/core#narrowMatch",
    "prefLabel": { "en": "has narrower match" },
    "broader": [ { "uri": "http://www.w3.org/2004/02/skos/core#mappingRelation" } ],
    "related": [ { "uri": "http://www.w3.org/2004/02/skos/core#broadMatch" } ]
  },
  {
    "uri": "http://www.w3.org/2004/02/skos/core#relatedMatch",
    "prefLabel": { "en": "has related match" },
    "broader": [ { "uri": "http://www.w3.org/2004/02/skos/core#mappingRelation" } ]
  }
]

5 Additional rules

5.1 Resource sameness

Two resources are same if and only if they both contain field uri with the same value. A resource without field uri is not same to any other resource.

The following resources are same:

{ "uri": "http://example.org/123", "created": "2007" }
{ "uri": "http://example.org/123", "created": "2015" }

5.2 Closed world statements

By default, a JSKOS document should be interpreted as possibly incomplete: a missing property does not imply that no value exists for this property: this assumption is also known as open-world assumption. Applications SHOULD support closed world statements to explicitly disable the open world assumption for selected properties and explicitly state the known absence or existence of unknown values:

data type open world closed world explicit negation explicit existence
list no field [...] [] [null] or [..., null]
set no field [...] [] [null] or [..., null]
language map no field {...} no language tag {"-":""} or {"-":[""]}
resource no field {...} - {}
URI/URL no field "..." - -
date no field "..." - -

The following concept has preferred labels and narrower concepts. but no alternative labels nor notations. Nothing is known about broader concepts, related concepts, and other possible concept properties:

{
  "type": ["http://www.w3.org/2004/02/skos/core#Concept"],
  "prefLabel": { "-": "..." },
  "altLabel": { },
  "notation": [],
  "narrower": [ null ]
}

5.3 Inference rules and integrity constraints

5.3.1 Inference rules

JSKOS records can automatically be expanded with the following inference rules:

  • Object types of set elements can be derived from fields the set is used in. For instance members of a set referenced by field inScheme can be assumed to be concept schemes (SKOS integritry rule S4) and members of a set referenced by field topConcepts can be assumed to be concepts (SKOS integritry rule S6).
  • If a concept scheme S is in set topConceptOf of a concept C then S can be assumed to also be in the set inScheme of C (SKOS integrity rule S7)
  • If a concept C is in set topConcept of a concept scheme S then C can be assumed to be in the set topConceptOf of S and vice versa (SKOS integrity rule S8)

5.3.2 Integritry constraints

Integrity constraints of SKOS SHOULD be respected. Applications MAY reject JSKOS data violating the constraints.

this list is not complete yet

5.4 Extension with custom fields

A JSKOS record MAY contain additional fields for custom usage. These fields MUST start with and underscore (_) or consist of uppercase letters and digits only (A-Z, 0-1). The fields SHOULD be ignored by generic JSKOS applications.

The fields PARTS and _id in the following example can be ignored:

{
  "_id": "e5fa44f2b31c1fb553b6021e7360d07d5d91ff5e",
  "uri": "http://www.wikidata.org/entity/Q34095",
  "prefLabel": { "en": "bronze" },
  "PARTS": ["copper", "tin"]
}

References

Normative references

Informative references

Appendices

The following appendices are non-normative.

Glossary

JSON
JavaScript Object Notation
JSON-LD
JavaScript Object Notation for Linked Data
KOS
Knowledge Organization System
RDF
Resource Description Framework

JSON-LD context

The following JSON-LD context document can be used to map JSKOS without closed world statements to RDF triples.

{
  "uri": "@id",
  "type": {
    "@id": "http://www.w3.org/1999/02/22-rdf-syntax-ns#type",
    "@type": "@id",
    "@container": "@set"
  },
  "created": {
    "@id": "http://purl.org/dc/terms/created",
    "@type": "xsd:date"
  },
  "issued": {
    "@id": "http://purl.org/dc/terms/issued",
    "@type": "xsd:date"
  },
  "modified": {
    "@id": "http://purl.org/dc/terms/modified",
    "@type": "xsd:date"
  },
  "creator": {
    "@id": "http://purl.org/dc/terms/creator",
    "@container": "@set"
  },
  "contributor": {
    "@id": "http://purl.org/dc/terms/contributor",
    "@container": "@set"
  },
  "publisher": {
    "@id": "http://purl.org/dc/terms/publisher",
    "@container": "@set"
  },
  "partOf": {
    "@id": "http://purl.org/dc/terms/isPartOf",
    "@container": "@set"
  },

  "url": {
    "@id": "http://xmlns.com/foaf/0.1/page",
    "@type": "@id"
  },
  "identifier": {
    "@id": "http://purl.org/dc/terms/identifier",
    "@container": "@set"
  },
  "notation": {
    "@id": "http://www.w3.org/2004/02/skos/core#notation",
    "@container": "@set"
  },
  "prefLabel": {
    "@id": "http://www.w3.org/2004/02/skos/core#prefLabel",
    "@container": "@language"
  },
  "altLabel": {
    "@id": "http://www.w3.org/2004/02/skos/core#altLabel",
    "@container": "@language"
  },
  "hiddenLabel": {
    "@id": "http://www.w3.org/2004/02/skos/core#hiddenLabel",
    "@container": "@language"
  },
  "note": {
    "@id": "http://www.w3.org/2004/02/skos/core#note",
    "@container": "@language"
  },
  "scopeNote": {
    "@id": "http://www.w3.org/2004/02/skos/core#scopeNote",
    "@container": "@language"
  },
  "definition": {
    "@id": "http://www.w3.org/2004/02/skos/core#definition",
    "@container": "@language"
  },
  "example": {
    "@id": "http://www.w3.org/2004/02/skos/core#example",
    "@container": "@language"
  },
  "historyNote": {
    "@id": "http://www.w3.org/2004/02/skos/core#historyNote",
    "@container": "@language"
  },
  "editorialNote": {
    "@id": "http://www.w3.org/2004/02/skos/core#editorialNote",
    "@container": "@language"
  },
  "changeNote": {
    "@id": "http://www.w3.org/2004/02/skos/core#changeNote",
    "@container": "@language"
  },
  "subject": {
    "@id": "http://purl.org/dc/terms/subject",
    "@container": "@set"
  },
  "subjectOf": {
    "@reverse": "http://purl.org/dc/terms/subject",
    "@container": "@set"
  },
  "source": {
    "@id": "http://purl.org/dc/terms/source",
    "@container": "@set"
  },
  "depiction": {
    "@id": "http://xmlns.com/foaf/0.1/depiction",
    "@type": "@id",
    "@container": "@set"
  },
  "startPlace": {
    "@id": "https://schema.org/location",
    "@container": "@set"
  },
  "endPlace": {
    "@id": "https://schema.org/location",
    "@container": "@set"
  },

  "narrower": {
    "@id": "http://www.w3.org/2004/02/skos/core#narrower",
    "@container": "@set"
  },
  "broader": {
    "@id": "http://www.w3.org/2004/02/skos/core#broader",
    "@container": "@set"
  },
  "related": {
    "@id": "http://www.w3.org/2004/02/skos/core#related",
    "@container": "@set"
  },
  "previous": {
    "@id": "http://rdf-vocabulary.ddialliance.org/xkos#previous",
    "@container": "@set"
  },
  "next": {
    "@id": "http://rdf-vocabulary.ddialliance.org/xkos#next",
    "@container": "@set"
  },
  
  "startDate": "http://schema.org/startDate",
  "endDate": "http://schema.org/endDate",
  "relatedDate": "http://www.w3.org/2000/01/rdf-schema#seeAlso",
  "location": "http://schema.org/location",
  "address": "https://schema.org/address",
  "street": "https://schema.org/streetAddress",
  "ext": "https://schema.org/streetAddress",
  "pobox": "https://schema.org/postOfficeBoxNumber",
  "locality": "https://schema.org/addressLocality",
  "region": "https://schema.org/addressRegion",
  "code": "https://schema.org/postalCode",
  "country": "https://schema.org/addressCountry",

  "ancestors": {
    "@id": "http://www.w3.org/2004/02/skos/core#broaderTransitive",
    "@container": "@set"
  },
  "inScheme": {
    "@id": "http://www.w3.org/2004/02/skos/core#inScheme",
    "@container": "@set"
  },
  "topConceptOf": {
    "@id": "http://www.w3.org/2004/02/skos/core#topConceptOf",
    "@container": "@set"
  },

  "topConcepts": {
    "@id": "http://www.w3.org/2004/02/skos/core#hasTopConcept",
    "@container": "@set"
  },
  "versionOf": {
    "@id": "http://purl.org/dc/terms/isVersionOf",
    "@container": "@set"
  },
  "extent": "http://purl.org/dc/terms/extent",
  "languages": {
    "@id": "http://purl.org/dc/terms/language",
    "@container": "@set"
  },
  "license": {
    "@id": "http://purl.org/dc/terms/license",
    "@container": "@set"
  },
  "namespace": "http://rdfs.org/ns/void#uriSpace",
  "uriPattern": "http://rdfs.org/ns/void#voidRegexPattern",

  "fromScheme": "http://rdfs.org/ns/void#subjectsTarget",
  "toScheme": "http://rdfs.org/ns/void#objectsTarget",

  "memberList": {
    "@id": "http://www.loc.gov/mads/rdf/v1#componentList",
    "@container": "@list"
  },
  "memberSet": {
    "@id": "http://www.w3.org/2004/02/skos/core#member",
    "@container": "@set"
  },
  "memberChoice": {
    "@id": "http://www.w3.org/2004/02/skos/core#member",
    "@container": "@set"
  },

  "count": "http://rdfs.org/ns/void#entities",

  "distributions": {
    "@id": "http://www.w3.org/ns/dcat#distribution",
    "@container": "@set"
  },
  "download": "http://www.w3.org/ns/dcat#downloadURL",
  "accessURL": "http://www.w3.org/ns/dcat#accessURL",
  "checksum": "http://spdx.org/rdf/terms#checksum",
  "mimetype": "http://www.w3.org/ns/dcat#mediaType",
  "packageFormat": "http://www.w3.org/ns/dcat#packageFormat",
  "compressFormat": "http://www.w3.org/ns/dcat#compressFormat",
  "format": "http://purl.org/dc/terms/format",
  "size": "http://www.w3.org/ns/dcat#byteSize",
  "value": "http://spdx.org/rdf/terms#checksumValue"  
}

JSKOS with closed world statements can be mapped to RDF by ignoring all boolean values and/or by mapping selected boolean values to RDF triples with blank nodes.

Applications should further add implicit RDF triples, such as $someConcept rdf:type skos:Concept, if such information can be derived from JSKOS by other means.

JSON Schemas and validation

Experimental JSON Schemas exist but don’t cover all aspects of JSKOS:

See NodeJS library jskos-validate for an implementation.

Public services to validate JSKOS data are included in instances of [jskos-server] and at https://format.gbv.de/validate/.

Changelog

Next

0.5.1 (2023-07-03)

  • More precise type of inScheme, topConceptOf, mappings, occurrences
  • Add some inference rules and integrity constraints
  • Fix JSON Schema files to allow negative dates and strict annotation dates
  • Add item fields place and media

0.5.0 (2022-08-29)

  • Make clear concordance field name distributions (plural)
  • Add license, compressFormat, packageFormat, size, checksum, accessURL to distribution
  • Remove fields for undefined JSKOS-API URLs

0.4.9 (2022-01-18)

  • Change format of URI in JSON Schema from URI to IRI
  • Change base format of URL in JSON Schema from URI to IRI

0.4.8 (2021-02-18)

  • Add concept scheme field notationExamples

0.4.7 (2021-02-10)

  • Add resource field source
  • Add item field address
  • Move startPlace/endPlace to Item and map them to schema:location

0.4.6 (2019-12-02)

  • Add memberRoles

0.4.5 (2019-04-08)

  • Add annotations (basic support)

0.4.4 (2018-11-02)

  • Add concept scheme fields notationPattern and uriPattern
  • Add concept fields startPlace and endPlace

0.4.2 (2018-08-22)

  • Move identifier field from item to resource
  • Add SKOS documentation field note to item
  • Add optional JSON Schemas

0.4.1 (2018-06-26)

  • Rename distribution field to distributions
  • Allow digits in custom fields

0.4.0 (2018-06-22)

  • Add Registry field occurrences
  • Add Distribution object type
  • Change rule for custom fields

0.3.2 (2018-05-29)

  • Add Concept Scheme field namespace

0.3.1 (2017-11-22)

  • Extend ocurrences to co-occurrences

0.3.0 (2017-11-15)

  • Add occurrences

0.2.2 (2017-11-06)

  • Add mappings field to Concept

0.2.1 (2017-09-27)

  • Disallow empty strings except as mandatory placeholder with language ranges
  • Support composed concepts with memberSet and memberList

0.2.0 (2017-09-21)

  • Rename object to resource
  • Move startDate, endDate, relatedDate, and location from Concept to Item
  • Add item types
  • Update JSON-LD context document

0.1.4 (2016-12-02)

  • Update JSON-LD context document
  • Change definition of concept bundles to use fields memberSet/List/Choice instead of members

0.1.3 (2016-10-03)

  • Change definition of “location” field to subset of GeoJSON (RFC 7946)

0.1.2 (2016-06-13)

  • Add “location” field for geographic coordinates

0.1.1 (2016-05-20)

  • Make field “license” a set instead of a single URI
  • Add field “extent”
  • Update reference to RFC 5646 instead of obsoleted RFC 4646

SKOS features not supported in JSKOS

JSKOS is aligned with SKOS but all references to SKOS are informative only. The following features of SKOS are not supported in JSKOS:

JSKOS features not supported in SKOS

The following features of JSKOS have no corresponce in SKOS:

Examples

Integrated Authority File (GND)

The Integrated Authority File (German: Gemeinsame Normdatei) is an authority file managed by the German National Library.

GND as JSKOS concept scheme. This example includes explicit knowledge about existence of more identifiers, definitions, and preferred labels:

{
   "definition" : {
      "-" : ["…"],
      "de" : ["Von der DNB in Kooperation mit den Verbundpartnern geführte gemeinsame Normdatei"],
      "en" : ["international authority file for personal names, subject headings and corporate bodies"]
   },
   "identifier" : [
      "http://bartoc.org/en/node/430",
      "http://d-nb.info/gnd/7749153-1",
      "http://viaf.org/viaf/188136221",
      "http://www.wikidata.org/entity/Q36578",
      null
   ],
   "namespace" : "http://d-nb.info/gnd/",
   "notation" : [
      "GND"
   ],
   "notationPattern" : "[0-9X-]+",
   "prefLabel" : {
      "-" : "…",
      "ar" : "ملف استنادي متكامل",
      "de" : "Gemeinsame Normdatei",
      "en" : "Integrated Authority File",
      "ko" : "게마인자메 노름다타이"
   },
   "type" : [
      "http://www.w3.org/2004/02/skos/core#ConceptScheme"
   ],
   "uri" : "http://d-nb.info/gnd/7749153-1",
   "uriPattern" : "^http://d-nb\\.info/gnd/([0-9X-]+)$"
}

A concept from GND:

{
    "uri": "http://d-nb.info/gnd/4074195-3",
    "type": ["http://www.w3.org/2004/02/skos/core#Concept"],
    "prefLabel": {
        "de": "Leukozyt"
    },
    "altLabel": {
        "de": [ "Leukocyt", "Weißes Blutkörperchen", "Leukozyten", "Leukocyten" ]
    },
    "broader": [ {
        "uri": "http://d-nb.info/gnd/4130604-1",
        "prefLabel": { "de": "Blutzelle" }
      } ],
    "narrower": [ {
        "uri": "http://d-nb.info/gnd/4036762-9",
        "prefLabel": { "de": "Lymphozyt" }
      }, {
        "uri": "http://d-nb.info/gnd/4158047-3",
        "prefLabel": { "de": "Granulozyt" }
      }, {
        "uri": "http://d-nb.info/gnd/4285013-7",
        "prefLabel": { "de": "Monozyt" }
     } ]
}

Dewey Decimal Classification (DDC)

A concept from the Dewey Decimal Classification, German edition 22:

{
    "uri": "http://dewey.info/class/612.112/e22/", 
    "type": ["http://www.w3.org/2004/02/skos/core#Concept"],
    "notation": ["612.112"],
    "prefLabel": { "de": "Leukozyten (Weiße Blutkörperchen)" },
    "broader": [ {
        "notation": ["612.11"],
        "prefLabel": { "de": "Blut" },
        "uri": "http://dewey.info/class/612.11/e22/"
      } ],
    "narrower": [ {
        "notation": ["612.1121"], 
        "prefLabel": { "de": "Biochemie" },
        "uri": "http://dewey.info/class/612.1121/e22/" 
      },{
        "notation": ["612.1127"],
        "prefLabel": { "de": "Anzahl und Auszählung" },
        "uri": "http://dewey.info/class/612.1127/e22/" 
      } ],
    "ancestors": [ { 
        "notation": ["612.11"], 
        "prefLabel": { "de": "Blut" }, 
        "uri": "http://dewey.info/class/612.11/e22/"
      },{
        "notation": ["612.1"],
        "prefLabel": { "de": "Blut und Kreislauf" },
        "uri": "http://dewey.info/class/612.1/e22/"
      },{
        "notation": ["612"],
        "prefLabel": { "de": "Humanphysiologie" },
        "uri": "http://dewey.info/class/612/e22/"
      },{
        "notation": ["61"],
        "prefLabel": { "de": "Medizin & Gesundheit" },
        "uri": "http://dewey.info/class/61/e22/"
      },{
        "notation": ["6"],
        "prefLabel": { "de": "Technik, Medizin, angewandte Wissenschaften" },
        "uri": "http://dewey.info/class/6/e22/"
      } ],
    "inScheme": [ {
        "uri":"http://dewey.info/scheme/version/e22/"
      },{
        "uri": "http://dewey.info/scheme/edition/e22/"
      },{
        "uri": "http://dewey.info/scheme/ddc/"
      } ]
}

A concept from the abbridget Dewey Decimal Classification, edition 23, in three languages:

{
    "uri": "http://dewey.info/class/641.5/e23/",
    "type": ["http://www.w3.org/2004/02/skos/core#Concept"],
    "notation": ["641.5"],
    "inScheme": [{"uri":"http://dewey.info/edition/e23/"}],
    "prefLabel": {
        "en": "Cooking",
        "de": "Kochen",
        "it": "Cucina"
    },
    "broader": [
        {
            "uri": "http://dewey.info/class/641/e23/",
            "notation": ["641"],
            "prefLabel": {
                "en": "Food and drink",
                "de": "Essen und Trinken",
                "it": "Cibi e bevande"
            }
        }
    ],
    "narrower": [
        {
            "uri": "http://dewey.info/class/641.502/e23/",
            "notation": ["641.502"],
            "prefLabel": {
                "en": "Miscellany",
                "de": "Verschiedenes",
                "it": "Miscellanea"
            }
        },
        {
            "uri": "http://dewey.info/class/641.508/e23/",
            "notation": ["641.508"],
            "prefLabel": {
                "en": "Cooking with respect to kind of persons",
                "de": "Kochen im Hinblick auf Personengruppen",
                "it": "Cucina in riferimento a categorie di persone"
            }
        },
        {
            "uri": "http://dewey.info/class/641.509/e23/",
            "notation": ["641.509"],
            "prefLabel": {
                "en": "Historical, geographic, persons treatment",
                "de": "Hostorische, geographische, personenbezogene Behandlung",
                "it": "Storia, geografia, persone"
            },
            "narrower": [
                {
                    "uri": "http://dewey.info/class/641.5092/e23/",
                    "notation": ["641.5092"],
                    "prefLabel": {
                        "en": "Cooks",
                        "de": "Köche",
                        "it": "Cuochi"
                    }
                }
            ]
        },
        {
            "uri": "http://dewey.info/class/641.59/e23/",
            "notation": ["641.59"],
            "prefLabel": {
                "en": "Cooking characteristic of specific geographic environments, ethnic cooking",
                "de": "Merkmale der Küche einzelner geografischer Umgebungen, ethnische Küche",
                "it": "Cucina tipica di specifici ambienti geografici, cucina etnica"
            }
        }
    ]
}

A decomposed DDC number for medieval cooking:

{
  "uri": "http://dewey.info/class/641.50902/e23/",
  "type": ["http://www.w3.org/2004/02/skos/core#Concept"],
  "notation": ["641.50902"],
  "inScheme": [{"uri":"http://dewey.info/edition/e23/"}],
  "memberList": [
    {
      "uri": "http://dewey.info/class/641.5/e23/",
      "notation": ["641.5"],
      "prefLabel": {"en": "Cooking"}
    },
    {
      "uri": "http://dewey.info/class/1--0902/e23",
      "notation": ["T1--0902"],
      "prefLabel": {"en": "*6th-15th centuries, 500-1499"}
    }
  ]
}

Mappings

Multiple mappings from one concept (612.112 in DDC) to GND.

{
    "type": ["http://www.w3.org/2004/02/skos/core#closeMatch"],
    "fromScheme": {"uri":"http://dewey.info/scheme/edition/e22/"},    
    "toScheme": {"uri":"http://d-nb.info/gnd/7749153-1"},
    "from": {
        "memberSet": [ {
            "uri": "http://dewey.info/class/612.112/e22/",
            "notation": ["612.112"]
        } ]
    },
    "to": {
        "memberSet": [ {
            "uri": "http://d-nb.info/gnd/4074195-3",
            "prefLabel": { "de": "Leukozyt" }
        } ]
    }
}
{
    "fromScheme": {"uri":"http://dewey.info/scheme/edition/e22/"},
    "from": {
        "memberSet": [ {
            "uri": "http://dewey.info/class/612.112/e22/",
            "notation": ["612.112"]
        } ]
    },
    "toScheme": {"uri":"http://d-nb.info/gnd/7749153-1"},
    "to": {
        "memberChoice": [ {
            "uri": "http://d-nb.info/gnd/4074195-3",
            "prefLabel": { "de": "Leukozyt" }
          },{
            "uri": "http://d-nb.info/gnd/4141893-1",
            "prefLabel": { "de": "Alkalische Leukozytenphosphatase" }
          },{
            "uri": "http://d-nb.info/gnd/7606617-4",
            "prefLabel": { "de": "Blutlymphozyt" }
          },{
            "uri": "http://d-nb.info/gnd/4158047-3",
            "prefLabel": { "de": "Granulozyt" }
          },{
            "uri": "http://d-nb.info/gnd/4227943-4",
            "prefLabel": { "de": "Leukozytenadhäsion" }
          },{
            "uri": "http://d-nb.info/gnd/4166696-3",
            "prefLabel": { "de": "Leukozytenphosphatase" }
          },{
            "uri": "http://d-nb.info/gnd/4285013-7",
            "prefLabel": { "de": "Monozyt" }
        } ]
    },
    "mappingRelevance": 0.5
}

Latest version: http://gbv.github.io/jskos/

Created with makespec