English
Project draft
A grouping of tasks: a project in a tracker, one disaster-response operation, a campaign. Called differently in different settings, with the same common attributes.
| Kind | entity |
| Type IRI | https://datamodels.jp/ns/task/Project |
| @context | https://datamodels.jp/context/task/v1.jsonld |
| JSON Schema | /schema/task/Project/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 |
identifier | Short handle: a slug or code, unique within the source systemhttps://schema.org/identifier | Property, string |
parent | Parent projecthttps://datamodels.jp/ns/task/parent | Relationship → Project |
projectStatus | State: active = in progress, closed = finished, archived = no longer used but kept; status is protected in the core context, hence projectStatushttps://datamodels.jp/ns/task/projectStatus | Property, string: active | closed | archived |
isPublic | true when publichttps://datamodels.jp/ns/task/isPublic | Property, boolean |
homepage | Homepagehttps://schema.org/url | Property, string (uri) |
start | Planned start: a date, or a date and timehttps://datamodels.jp/ns/task/start | Property, string (date or date-time) |
end | Planned end: a date, or a date and timehttps://datamodels.jp/ns/task/end | Property, string (date or date-time) |
location | Location as any GeoJSON geometry: point, line, polygon or a collectionhttps://uri.etsi.org/ngsi-ld/location | GeoProperty (Geometry) |
keywords | Keywords or labelshttps://schema.org/keywords | Property, array |
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:Project:heavy-rain-2026-07",
"type": "Project",
"name": "令和8年7月大雨 災害対応",
"description": "7/8〜 大雨に伴う区の災害対応オペレーション",
"identifier": "heavy-rain-2026-07",
"projectStatus": "active",
"isPublic": false,
"homepage": "https://tracker.example.jp/projects/heavy-rain-2026-07",
"start": "2026-07-08T07:00:00+09:00",
"location": {
"type": "Polygon",
"coordinates": [
[
[
139.73,
35.67
],
[
139.78,
35.67
],
[
139.78,
35.705
],
[
139.73,
35.705
],
[
139.73,
35.67
]
]
]
},
"keywords": [
"大雨",
"災害対応"
],
"source": "https://tracker.example.jp/projects/heavy-rain-2026-07",
"externalId": "42",
"dateCreated": "2026-07-08T06:00: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 repository
| This model | Maps to | Note |
|---|---|---|
name | name | |
description | description | |
identifier | full_name | |
parent | no counterpart | a fork's parent means the copied-from repository, a different relation |
projectStatus | archived | true → archived, otherwise active |
isPublic | private | negated |
homepage | html_url | |
keywords | topics | |
source | html_url | |
externalId | id | |
dateCreated | created_at | |
dateModified | updated_at |
Mapping file (YAML) for this standard: github.yaml (see Mapping files)
Redmine project
| This model | Maps to | Note |
|---|---|---|
name | name | |
description | description | |
identifier | identifier | |
parent | parent.id | |
projectStatus | status | 1 → active, 5 → closed, 9 → archived |
isPublic | is_public | |
homepage | homepage | |
location | geom | redmine_gtt project boundary |
source | <base_url>/projects/<identifier> | |
externalId | id | |
dateCreated | created_on | |
dateModified | updated_on |
Mapping file (YAML) for this standard: redmine.yaml (see Mapping files)
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.
- status is a protected core-context term, hence projectStatus.
- Like start and due on Task and Milestone, start and end accept a date (YYYY-MM-DD) or a date-time; the reason is in the notes of Task. In the normalized form a date is an NGSI-LD Date value and a date-time a DateTime value.
Change history (1)
- 2026-10-09 (team decision; a pre-release correction of 1.0.0 in place): start and end changed to accept a date or a date-time.