GTT FIWARE core vocabulary

Namespace: https://gtt-project.org/ns/fiware# · Machine-readable: fiware.jsonld · Emitted by redmine_gtt_fiware

The redmine_gtt_fiware plugin publishes Redmine issues into NGSI-LD context brokers as Issue entities, so any system on the broker can see whether a problem is being handled, in what state, and where. This page defines the frozen core: the terms every emitting instance uses with the same meaning. It is deliberately small; anything here changing would break consumers, so nothing here changes.

Each instance extends this core with its own vocabulary, published as a JSON-LD context at <instance>/fiware/context.jsonld: subtypes (declared rdfs:subClassOf the core Issue) and custom-field terms. Dereference an instance's context to learn its full schema.

Class

Term	Meaning
Issue	A tracked unit of work in a Redmine instance, published as shared context. Entity ids are `urn:ngsi-ld:Issue:redmine:<instance>:<issue>` and stay stable for the life of the issue.

Core properties (always present)

Term	Kind	Meaning
title	Property	The issue subject.
status	Property	Normalized lifecycle state: `open` or `closed`.
statusLabel	Property	The instance's own status name, unnormalized.
subtype	Property	The instance-defined subtype term for the issue's tracker (for example `WorkOrder`). Declared as a class in the instance's context; travels as a property because common brokers reject multi-type entities.
source	Property	The canonical URL of the issue in its system of record.
refersTo	Relationship	The entity that triggered the issue, when it originated from a broker notification. Correlates a problem with the work addressing it.

Entities also carry the NGSI-LD core-context terms location (the issue geometry as GeoJSON), dateCreated and dateModified.

Standard properties (exposed per tracker by the instance administrator)

Term	Kind	Meaning
description	Property	The issue description.
priority	Property	The priority name.
category	Property	The issue category name.
targetVersion	Property	The target version or milestone name.
startDate	Property	The planned start date.
dueDate	Property	The due date.
estimatedTime	Property	Estimated effort in hours.
percentDone	Property	Completion in percent, 0 to 100.
parent	Relationship	The parent issue's entity.
assignee	Property	The assignee's display name. Publishing it to a shared broker is an explicit administrator decision.

Everything beyond the core defaults to unexposed. Journals, watchers and private issues are never emitted.

Task profile (datamodels.jp)

An instance can also emit its issues as Task entities of the neutral datamodels.jp task vocabulary, so consumers written against that vocabulary read them without a GTT-specific context. The frozen core above does not change; the instance administrator chooses one of the two.

Machine-readable: fiware-task.jsonld. It imports the datamodels.jp task context and adds only what Task lacks:

Term	Kind	Meaning
category	Property	The issue category name (`gttfiware:category`, as in the core).

Each instance publishes its own task-mode context at <instance>/fiware/task-context.jsonld: subtypes, declared rdfs:subClassOf Task, and custom-field terms.