Pre-release. Until the official launch, content may change, including published files.
Skip to content

Source: https://datamodels.jp/en/models/task/Task/ · Text CC BY 4.0

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.

Kindentity
Type IRIhttps://datamodels.jp/ns/task/Task
@contexthttps://datamodels.jp/context/task/v1.jsonld
JSON Schema/schema/task/Task/v1.json
DownloadCSV template Table Schema Structured output for AI PostgreSQL / PostGIS table About these files
LicenceCC0 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 ​

Types and their relationshipsprojectmilestonerefersToassignee, authorlocationGeometryGeometry8 more links →MilestoneMilestone1 more link →ProjectProject3 more links →TaskTask↻ parent, relatedToperson,organisation or teamany entity

Relationship (attribute name)used as a value type↻ Relationship to the same typeother subjectN more links: continued on that type's page

Attributes ​

AttributeDescriptionValue
name*Name or subject
https://uri.etsi.org/ngsi-ld/name
Property, string
descriptionDescription
http://purl.org/dc/terms/description
Property, string
projectThe project this belongs to, when the source system has projects
https://datamodels.jp/ns/task/project
Relationship → Project
milestoneThe milestone (version, release) this is planned for
https://datamodels.jp/ns/task/milestone
Relationship → Milestone
parentParent task (RFC 8984 relatedTo parent)
https://datamodels.jp/ns/task/parent
Relationship → Task
relatedToRelated tasks. Always an array in the key-values form, even with one target. The kind of relation (blocks, precedes, duplicates) is left to extensions
https://datamodels.jp/ns/task/relatedTo
Relationship → Task (multiple)
refersToThe entity this task is about (a report, an asset, a road)
https://datamodels.jp/ns/task/refersTo
Relationship → any entity
progressNormalised 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
statusLabelThe source system's own status name, unchanged (for example "In progress", "Resolved"). Required when progress is left out
https://datamodels.jp/ns/task/statusLabel
Property, string
subtypeThe source system's kind, for example a tracker, an issue type or a category
https://datamodels.jp/ns/task/subtype
Property, string
priorityPriority 0 to 9: 1 highest, 9 lowest, 0 undefined (RFC 8984)
https://datamodels.jp/ns/task/priority
Property, integer, ≥ 0, ≤ 9
assigneeAssignees: person, organisation or team entities, possibly outside this subject. Always an array in the key-values form, even with one target
https://datamodels.jp/ns/task/assignee
Relationship → person, organisation or team (multiple)
authorCreator (a person, organisation or team entity)
https://schema.org/author
Relationship → person, organisation or team
startPlanned start: a date, or a date and time (RFC 8984 start)
https://datamodels.jp/ns/task/start
Property, string (date or date-time)
dueDue: a date, or a date and time (RFC 8984 due)
https://datamodels.jp/ns/task/due
Property, string (date or date-time)
completedAtWhen progress became completed
https://datamodels.jp/ns/task/completedAt
Property, string (date-time)
estimatedDurationEstimated effort as an ISO 8601 duration, e.g. PT1H30M (RFC 8984 estimatedDuration)
https://datamodels.jp/ns/task/estimatedDuration
Property, string
percentCompleteCompletion 0 to 100 (RFC 8984 percentComplete)
https://datamodels.jp/ns/task/percentComplete
Property, integer, ≥ 0, ≤ 100
keywordsKeywords or labels
https://schema.org/keywords
Property, array
locationLocation as any GeoJSON geometry: point, line, polygon or a collection
https://uri.etsi.org/ngsi-ld/location
GeoProperty (Geometry)
spatialIdSpatial IDs (ZFXY) covering the task. Optional
https://datamodels.jp/ns/task/spatialId
Property, array
isPrivatetrue when private; default false
https://datamodels.jp/ns/task/isPrivate
Property, boolean
sourceURL of this object in the system of record
https://smart-data-models.github.io/data-models/terms.jsonld#/definitions/source
Property, string (uri)
externalIdIdentifier in the system of record
https://datamodels.jp/ns/task/externalId
Property, string
dateCreatedCreation 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)
dateModifiedLast modification time in the system of record
https://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:

    http
    Link: <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)15 of 26 fields

GitHub issues have no priority, due date or completion percentage (Projects custom fields are extensions). progress is derived from state and state_reason.

This modelMaps toNote
nametitle
descriptionbody
projectrepositoryProject.identifier = owner/repo
milestonemilestone
parentno counterpartsub-issues are an extension candidate
relatedTono counterpart
refersTono counterpart
progressstate + state_reasonopen → needs-action or in-process; closed+completed → completed; closed+not_planned or duplicate → cancelled
statusLabelstate (+ state_reason)
subtypetypeissue type (organisation feature) or one of the labels
priorityno counterpart
assigneeassignees
authoruser
startno counterpart
dueno counterpartthe milestone due date (milestone.due_on) goes to Milestone.due
completedAtclosed_atonly when state is closed and state_reason is completed; closed_at of not_planned or duplicate issues is not mapped
estimatedDurationno counterpart
percentCompleteno counterpart
keywordslabels[].name
locationno counterpart
spatialIdno counterpart
isPrivateno counterpartfollows the repository visibility
sourcehtml_url
externalIdnumber
dateCreatedcreated_at
dateModifiedupdated_at

Mapping file (YAML) for this standard: github-issues.yaml (see Mapping files)

IssueReporting (Smart Data Models dataModel.IssueTracking, from IUDX)8 of 10 fields

An Indian citizen grievance record (ward, department, landmark). A correspondence for interoperability, not an adoption.

This modelMaps toNote
nametitle
descriptionno counterpart
subtypecategory / subCategory
progressresolutionStatusvalues are deployment-specific; resolved → completed
statusLabelresolutionStatus
assigneedepartmentIda department identifier, not an entity reference
startobservationDateTime
locationlocationlandmark and wardId are extensions
externalIdreportId
keywordsno counterpart

Mapping file (YAML) for this standard: iudx-issuereporting.yaml (see Mapping files)

JSCalendar Task (RFC 8984)19 of 25 fields

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 modelMaps toNote
nametitle
descriptiondescription
projectno counterpartJSCalendar has no project; calendars group objects
parentrelatedTo[parent]
relatedTorelatedTofirst, next and child relations are extensions
refersTono counterpart
progressprogressidentical value set (cancelled is a standard RFC 8984 value)
statusLabelno counterpart
subtypeno counterpart
prioritypriority
assigneeparticipantsparticipants with role attendee or owner
authorno counterpartJSCalendar expresses the owner as a participant role
startstartJSCalendar 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
duedueJSCalendar due is a LocalDateTime (no offset); here it is a date, or a date-time with an offset
completedAtprogressUpdatedonly when progress is completed
estimatedDurationestimatedDuration
percentCompletepercentComplete
keywordskeywords
locationlocationsa point maps to coordinates (geo URI); lines and polygons have no counterpart
spatialIdno counterpart
isPrivateprivacyprivacy private or secret
sourcelinksa link with rel alternate
externalIduid
dateCreatedcreated
dateModifiedupdated

Mapping file (YAML) for this standard: jscalendar.yaml (see Mapping files)

Open311 GeoReport v2 service_requests (Smart Data Models dataModel.IssueTracking)13 of 16 fields

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 modelMaps toNote
nameservice_name
descriptiondescription
projectno counterpartjurisdiction_id is the closest
refersTono counterpart
progressstatusopen → needs-action, closed → completed
statusLabelstatus_notes
subtypeservice_code
assigneeagency_responsiblea string, not an entity reference
startrequested_datetime
dueexpected_datetime
completedAtupdated_datetimeapproximation when closed
locationlat, longpoint only; address, address_id and zipcode are address fields (candidate for a common JapaneseAddress extension)
sourceno counterpart
externalIdservice_request_id
dateCreatedrequested_datetime
dateModifiedupdated_datetime

Mapping file (YAML) for this standard: open311.yaml (see Mapping files)

Redmine issue (including redmine_gtt_fiware output)23 of 26 fields

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 modelMaps toNote
namesubject
descriptiondescription
projectproject_id
milestonefixed_version_idtarget version
parentparent_issue_id
relatedTorelations[].issue_to_idrelation_type is not in the core
refersTono counterpartcorresponds to GTT refersTo (the subscribed entity)
progressstatus.is_closedclosed → completed, otherwise needs-action or in-process
statusLabelstatus.name
subtypetracker.name
prioritypriority.positionposition mapped onto 1 to 9
assigneeassigned_to_id
authorauthor_id
startstart_datea date (YYYY-MM-DD), kept as it is
duedue_datea date (YYYY-MM-DD), kept as it is
completedAtclosed_on
estimatedDurationestimated_hourshours converted to an ISO 8601 duration (1.5 → PT1H30M)
percentCompletedone_ratio
keywordsno counterpartnot in Redmine core; tag plugins are extensions
locationgeomredmine_gtt geometry (point, line, polygon, 3D)
spatialIdno counterpart
isPrivateis_private
source<base_url>/issues/<id>
externalIdid
dateCreatedcreated_on
dateModifiedupdated_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 organisationModelRelationAdded attributes
GTT ProjectIssue
@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"), unchanged
https://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.