English
Task draft
A tracked unit of work: a ticket or issue in a tracker, a calendar to-do, a municipal work order. State and priority follow RFC 8984 (JSCalendar); the source system's own status name and kind are kept in statusLabel and subtype. Location may be any geometry.
| Kind | entity |
| Type IRI | https://datamodels.jp/ns/task/Task |
| @context | https://datamodels.jp/context/task/v1.jsonld |
| JSON Schema | /schema/task/Task/v1.json |
| Download | CSV template Table Schema Structured output for AI PostgreSQL / PostGIS table About these files |
| Licence | CC0 1.0: the files (@context, JSON Schema, examples) can be used without conditions |
These @context and JSON Schema URLs (version aliases) always point to the latest compatible version.
For URLs that never change, see Versions. More in URLs and versions.
Types and relationships
Relationship (attribute name)used as a value type↻ Relationship to the same typeother subjectN more links: continued on that type's page
Attributes
| Attribute | Description | Value |
|---|---|---|
name* | Name or subjecthttps://uri.etsi.org/ngsi-ld/name | Property, string |
description | Descriptionhttp://purl.org/dc/terms/description | Property, string |
project | The project this belongs to, when the source system has projectshttps://datamodels.jp/ns/task/project | Relationship → Project |
milestone | The milestone (version, release) this is planned forhttps://datamodels.jp/ns/task/milestone | Relationship → Milestone |
parent | Parent task (RFC 8984 relatedTo parent)https://datamodels.jp/ns/task/parent | Relationship → Task |
relatedTo | Related tasks. Always an array in the key-values form, even with one target. The kind of relation (blocks, precedes, duplicates) is left to extensionshttps://datamodels.jp/ns/task/relatedTo | Relationship → Task (multiple) |
refersTo | The entity this task is about (a report, an asset, a road)https://datamodels.jp/ns/task/refersTo | Relationship → any entity |
progress | Normalised state (RFC 8984 progress): needs-action = not started, in-process = in progress, completed = done, failed = failed, cancelled = cancelled. When no value fits, leave it out and give the local wording in statusLabel.https://datamodels.jp/ns/task/progress | Property, string: needs-action | in-process | completed | failed | cancelled |
statusLabel | The source system's own status name, unchanged (for example "In progress", "Resolved"). Required when progress is left outhttps://datamodels.jp/ns/task/statusLabel | Property, string |
subtype | The source system's kind, for example a tracker, an issue type or a categoryhttps://datamodels.jp/ns/task/subtype | Property, string |
priority | Priority 0 to 9: 1 highest, 9 lowest, 0 undefined (RFC 8984)https://datamodels.jp/ns/task/priority | Property, integer, ≥ 0, ≤ 9 |
assignee | Assignees: person, organisation or team entities, possibly outside this subject. Always an array in the key-values form, even with one targethttps://datamodels.jp/ns/task/assignee | Relationship → person, organisation or team (multiple) |
author | Creator (a person, organisation or team entity)https://schema.org/author | Relationship → person, organisation or team |
start | Planned start: a date, or a date and time (RFC 8984 start)https://datamodels.jp/ns/task/start | Property, string (date or date-time) |
due | Due: a date, or a date and time (RFC 8984 due)https://datamodels.jp/ns/task/due | Property, string (date or date-time) |
completedAt | When progress became completedhttps://datamodels.jp/ns/task/completedAt | Property, string (date-time) |
estimatedDuration | Estimated effort as an ISO 8601 duration, e.g. PT1H30M (RFC 8984 estimatedDuration)https://datamodels.jp/ns/task/estimatedDuration | Property, string |
percentComplete | Completion 0 to 100 (RFC 8984 percentComplete)https://datamodels.jp/ns/task/percentComplete | Property, integer, ≥ 0, ≤ 100 |
keywords | Keywords or labelshttps://schema.org/keywords | Property, array |
location | Location as any GeoJSON geometry: point, line, polygon or a collectionhttps://uri.etsi.org/ngsi-ld/location | GeoProperty (Geometry) |
spatialId | Spatial IDs (ZFXY) covering the task. Optionalhttps://datamodels.jp/ns/task/spatialId | Property, array |
isPrivate | true when private; default falsehttps://datamodels.jp/ns/task/isPrivate | Property, boolean |
source | URL of this object in the system of recordhttps://smart-data-models.github.io/data-models/terms.jsonld#/definitions/source | Property, string (uri) |
externalId | Identifier in the system of recordhttps://datamodels.jp/ns/task/externalId | Property, string |
dateCreated | Creation time in the system of record (distinct from the broker attribute createdAt)https://smart-data-models.github.io/data-models/terms.jsonld#/definitions/dateCreated | Property, string (date-time) |
dateModified | Last modification time in the system of recordhttps://smart-data-models.github.io/data-models/terms.jsonld#/definitions/dateModified | Property, string (date-time) |
* required
Using this model
How to validate data and send it to a broker: Using the models.
To add attributes of your own to this model, the extension builder writes the @context and JSON Schema.
Extended this model? If you publish it on a site made with the toolkit, it shows on this page once your site is on the list of sites. Without a site, list your extension so others can reuse your names (how it works).
Files that particular brokers and tools can load as they are, made from this model: Adapters
The Link header, for sending data without @context in the body:
httpLink: <https://datamodels.jp/context/task/v1.jsonld>; rel="http://www.w3.org/ns/json-ld#context"; type="application/ld+json"
Example
Most examples are a fictional scenario (heavy rain in Chiyoda, Tokyo). Place names and codes are real; the events, people and teams are invented. Some examples copy a real row of a published list instead; their notes name the source. See writing examples.
json
{
"id": "urn:ngsi-ld:Task:1234",
"type": "Task",
"name": "靖国通りのアンダーパスの冠水を確認する",
"description": "住民からの通報の現地確認。水位と通行可否を報告すること。",
"project": "urn:ngsi-ld:Project:heavy-rain-2026-07",
"milestone": "urn:ngsi-ld:Milestone:heavy-rain-2026-07-initial",
"parent": "urn:ngsi-ld:Task:1200",
"relatedTo": [
"urn:ngsi-ld:Task:1198"
],
"refersTo": "urn:ngsi-ld:RoadRestriction:0001",
"progress": "in-process",
"statusLabel": "対応中",
"subtype": "現地確認",
"priority": 2,
"assignee": [
"urn:ngsi-ld:Team:field-team-a"
],
"author": "urn:ngsi-ld:Person:staff-0012",
"start": "2026-07-08T10:30:00+09:00",
"due": "2026-07-08T12:00:00+09:00",
"estimatedDuration": "PT1H30M",
"percentComplete": 40,
"keywords": [
"冠水",
"現地確認"
],
"location": {
"type": "Point",
"coordinates": [
139.7512,
35.6953
]
},
"spatialId": [
"/25/0/29802971/13211383"
],
"isPrivate": false,
"source": "https://tracker.example.jp/issues/1234",
"externalId": "1234",
"dateCreated": "2026-07-08T10:20:00+09:00",
"dateModified": "2026-07-08T11:05:00+09:00"
}Files: example.json · example-normalized.jsonld · Open in the JSON-LD Playground: see the full IRI behind every attribute (expanded form).
Something missing or wrong?
Open an issue, or propose new attributes or models with the proposal form. How it works: Contributing. The source files (notes, mapping tables) are on GitHub.
Referenced standards
The standards this model corresponds to, field by field. Open one to see its table.
GitHub Issues (REST API)
GitHub issues have no priority, due date or completion percentage (Projects custom fields are extensions). progress is derived from state and state_reason.
| This model | Maps to | Note |
|---|---|---|
name | title | |
description | body | |
project | repository | Project.identifier = owner/repo |
milestone | milestone | |
parent | no counterpart | sub-issues are an extension candidate |
relatedTo | no counterpart | |
refersTo | no counterpart | |
progress | state + state_reason | open → needs-action or in-process; closed+completed → completed; closed+not_planned or duplicate → cancelled |
statusLabel | state (+ state_reason) | |
subtype | type | issue type (organisation feature) or one of the labels |
priority | no counterpart | |
assignee | assignees | |
author | user | |
start | no counterpart | |
due | no counterpart | the milestone due date (milestone.due_on) goes to Milestone.due |
completedAt | closed_at | only when state is closed and state_reason is completed; closed_at of not_planned or duplicate issues is not mapped |
estimatedDuration | no counterpart | |
percentComplete | no counterpart | |
keywords | labels[].name | |
location | no counterpart | |
spatialId | no counterpart | |
isPrivate | no counterpart | follows the repository visibility |
source | html_url | |
externalId | number | |
dateCreated | created_at | |
dateModified | updated_at |
Mapping file (YAML) for this standard: github-issues.yaml (see Mapping files)
IssueReporting (Smart Data Models dataModel.IssueTracking, from IUDX)
An Indian citizen grievance record (ward, department, landmark). A correspondence for interoperability, not an adoption.
| This model | Maps to | Note |
|---|---|---|
name | title | |
description | no counterpart | |
subtype | category / subCategory | |
progress | resolutionStatus | values are deployment-specific; resolved → completed |
statusLabel | resolutionStatus | |
assignee | departmentId | a department identifier, not an entity reference |
start | observationDateTime | |
location | location | landmark and wardId are extensions |
externalId | reportId | |
keywords | no counterpart |
Mapping file (YAML) for this standard: iudx-issuereporting.yaml (see Mapping files)
JSCalendar Task (RFC 8984)
Value spaces follow this standard. JSCalendar locations are a set of named places with geo-URI coordinates while location here is a GeoJSON geometry; participants carry roles, assignee corresponds to attendee/owner.
| This model | Maps to | Note |
|---|---|---|
name | title | |
description | description | |
project | no counterpart | JSCalendar has no project; calendars group objects |
parent | relatedTo[parent] | |
relatedTo | relatedTo | first, next and child relations are extensions |
refersTo | no counterpart | |
progress | progress | identical value set (cancelled is a standard RFC 8984 value) |
statusLabel | no counterpart | |
subtype | no counterpart | |
priority | priority | |
assignee | participants | participants with role attendee or owner |
author | no counterpart | JSCalendar expresses the owner as a participant role |
start | start | JSCalendar start is a LocalDateTime (no offset; the time zone is in timeZone). Here it is a date, or a date-time with an offset; a date corresponds to a start at 00:00:00 with showWithoutTime: true |
due | due | JSCalendar due is a LocalDateTime (no offset); here it is a date, or a date-time with an offset |
completedAt | progressUpdated | only when progress is completed |
estimatedDuration | estimatedDuration | |
percentComplete | percentComplete | |
keywords | keywords | |
location | locations | a point maps to coordinates (geo URI); lines and polygons have no counterpart |
spatialId | no counterpart | |
isPrivate | privacy | privacy private or secret |
source | links | a link with rel alternate |
externalId | uid | |
dateCreated | created | |
dateModified | updated |
Mapping file (YAML) for this standard: jscalendar.yaml (see Mapping files)
Open311 GeoReport v2 service_requests (Smart Data Models dataModel.IssueTracking)
A correspondence for interoperability, not an adoption. Open311 is the record of a North American 311 hotline report; it has no assignee, due date, completion or hierarchy.
| This model | Maps to | Note |
|---|---|---|
name | service_name | |
description | description | |
project | no counterpart | jurisdiction_id is the closest |
refersTo | no counterpart | |
progress | status | open → needs-action, closed → completed |
statusLabel | status_notes | |
subtype | service_code | |
assignee | agency_responsible | a string, not an entity reference |
start | requested_datetime | |
due | expected_datetime | |
completedAt | updated_datetime | approximation when closed |
location | lat, long | point only; address, address_id and zipcode are address fields (candidate for a common JapaneseAddress extension) |
source | no counterpart | |
externalId | service_request_id | |
dateCreated | requested_datetime | |
dateModified | updated_datetime |
Mapping file (YAML) for this standard: open311.yaml (see Mapping files)
Redmine issue (including redmine_gtt_fiware output)
Redmine priorities are an ordered list (low, normal, high, urgent, immediate) mapped onto 1 to 9. Status maps through is_closed to needs-action or completed; in-process is assigned by the operator's status configuration. Custom fields are extensions. GTT (redmine_gtt_fiware) can align its frozen Issue vocabulary to Task by alias (Issue → tm:Task) or by declaring Issue a subclass.
| This model | Maps to | Note |
|---|---|---|
name | subject | |
description | description | |
project | project_id | |
milestone | fixed_version_id | target version |
parent | parent_issue_id | |
relatedTo | relations[].issue_to_id | relation_type is not in the core |
refersTo | no counterpart | corresponds to GTT refersTo (the subscribed entity) |
progress | status.is_closed | closed → completed, otherwise needs-action or in-process |
statusLabel | status.name | |
subtype | tracker.name | |
priority | priority.position | position mapped onto 1 to 9 |
assignee | assigned_to_id | |
author | author_id | |
start | start_date | a date (YYYY-MM-DD), kept as it is |
due | due_date | a date (YYYY-MM-DD), kept as it is |
completedAt | closed_on | |
estimatedDuration | estimated_hours | hours converted to an ISO 8601 duration (1.5 → PT1H30M) |
percentComplete | done_ratio | |
keywords | no counterpart | not in Redmine core; tag plugins are extensions |
location | geom | redmine_gtt geometry (point, line, polygon, 3D) |
spatialId | no counterpart | |
isPrivate | is_private | |
source | <base_url>/issues/<id> | |
externalId | id | |
dateCreated | created_on | |
dateModified | updated_on |
Mapping file (YAML) for this standard: redmine.yaml (see Mapping files)
Built on by others
Models on other sites that build on this one, and extensions that organisations listed. Site models are read from each site's index (catalog.json) and reviewed when they are taken in; extensions are listed as their owners reported them. datamodels.jp does not review the models or attributes themselves. If you need an attribute with the same meaning, you can use a name listed here. All sites: Data model sites. An organisation without a site of its own can list its extension with the form.
| Site or organisation | Model | Relation | Added attributes |
|---|---|---|---|
| GTT Project | Issue@context: https://models.gtt-project.org/context/redmine/v0.jsonld | same type, another name (v1.0.0) | category: The Redmine issue category, a name that the project defines (for example "Pothole"), unchangedhttps://models.gtt-project.org/ns/redmine#category |
Notes
- Upstream considered (2026-09-18): Smart Data Models dataModel.IssueTracking (Open311 service_requests/services; IUDX IssueReporting), both citizen-complaint records shaped by one country's municipal process, not task models; dataModel.Transportation CityWork and dataModel.PredictiveMaintenance, domain-specific. RFC 8984 (JSCalendar Task) is the universal reference and supplies the value spaces used here. See issue #22.
- The core is deliberately small. System-specific data (time spent, watchers, custom fields, map rotation) belongs in extensions.
- progress uses the RFC 8984 value set unchanged: needs-action, in-process, completed, failed, cancelled. statusLabel keeps the source system’s own status name; subtype its tracker, issue type or category.
- relatedTo and assignee are multi-valued Relationships (one instance per target, distinguished by datasetId). In the key-values form they are always arrays, even with a single target. The kind of a relation (blocks, precedes, duplicates) is not in the core.
- A source system keeps its own type and attribute names through a JSON-LD alias context (see the guide "Your own names"); its vocabulary can also declare its types subclasses of these.
- project is optional: RFC 8984 has no project, and a calendar to-do or a stand-alone work order should not have to invent one; trackers whose issues always belong to a project can require it in their own model. name and progress are required.
- Notes and files are not task concepts: they attach to any entity. If an application needs them, they belong in the common subject, reusing schema.org (Comment, MediaObject) and linkable to any entity. Milestone is what Redmine (versions), GitHub and GitLab (milestones) and Jira (fix versions) share: a name, a description, a due date, open or closed, a project. The original design is in issue #22.
- start and due accept a date (YYYY-MM-DD) or a date-time. Redmine (start date, due date, version due date), GitHub milestones (a date in the UI), GitLab and many municipal work orders have only dates; turning a date into a date-time would invent a time of day that is not in the data. The first implementation, the GTT Redmine plugin, emits plain dates. This differs from RFC 8984, whose start and due are LocalDateTime values (a date and time without offset). In the normalized form a date is an NGSI-LD Date value and a date-time a DateTime value.
Change history (2)
- 2026-10-09 (team decision; a pre-release correction of 1.0.0 in place): Comment and Attachment were removed from this subject and Milestone was added. The two came from Redmine journals and attachments and from the former models of a municipal disaster-response application, removed on 2026-09-24; GTT itself never emits journals or attachments.
- 2026-10-09 (team decision; a pre-release correction of 1.0.0 in place): start and due changed to accept a date or a date-time.