name of Jnst
description::
· a-Jnst-document is a-json-object with NAMED json-semantic-units.
name::
* McsEngl.Jnstname,
* McsEngl.Jnstname'(Jnst'name)!⇒Jnstname,
* McsEngl.Jnst'name!⇒Jnstname,
* McsEngl.Jnst'property!⇒Jnstname,
Jnstname.SPECIFIC
description::
* category,
* child,
* class,
* coordinates,
* decimals,
* dimension,
* dimension-ID,
* error,
* extension,
* geo,
* href,
* id,
* index,
* link,
* metric,
* note,
* position,
* relation-ID,
* role,
* size,
* source,
* status,
* symbol,
* time,
* type,
* unit,
* updated,
* value,
* version,
name::
* McsEngl.Jnstname.specific,
Jnstname.version
description::
"It declares the JSON-stat version of the response. The goal of this property is to help clients parsing that particular response.
{
"version" : "2.0",
…
}
Because future versions could add optional properties, the same response can be valid in several versions: any of such versions is accepted as a value of version.
Before version 2.0
version was introduced in version 2.0. That’s why this property can’t accept values lower than 2.0."
[{2020-12-28} https://json-stat.org/format/#version]
× aJsonsunt: [string]
× bRequired: true
× nSince: 2.0
× sParent: root
× sChild: none
name::
* McsEngl.Jnstversion,
* McsEngl.Jnstname.version!⇒Jnstversion,
* McsEngl.Jnst'version!⇒Jnstversion,
Jnstname.class
description::
"JSON-stat supports several classes of responses. Possible values of class are: dataset, dimension and collection.
Dataset responses include a single dataset. They are declared using the dataset class value."
[{2020-12-29} https://json-stat.org/format/#class]
× aJsonsunt: [string]
× bRequired: false
× nSince: 1.1
× sParent: root, relation-ID array element
× sChild: none
name::
* McsEngl.Jnstclass,
* McsEngl.Jnstname.class!⇒Jnstclass,
* McsEngl.Jnst'class!⇒Jnstclass,
Jnstname.href
description::
"It specifies a URL.
Providers can use this property to avoid sending information that is shared between different requests (for example, dimensions)."
[{2020-12-29} https://json-stat.org/format/#href]
× aJsonsunt: [string]
× bRequired: false
× nSince: 1.1
× sParent: root, dimension-ID, relation-ID array element
× sChild: none
name::
* McsEngl.Jnsthref,
* McsEngl.Jnstname.href!⇒Jnsthref,
* McsEngl.Jnst'href!⇒Jnsthref,
Jnstname.label
description::
"It is used to assign a very short (one line) descriptive text to IDs at different levels of the response tree. It is language-dependent.
When it is a root property or a child of dimension-ID or of a unit category ID, it is a string."
[{2020-12-29} https://json-stat.org/format/#label]
× aJsonsunt: [string, object]
× bRequired: true
× nSince: 1.0
× sParent: root, dimension-ID, category, unit category ID, relation-ID array element
× sChild: none
name::
* McsEngl.Jnstlabel,
* McsEngl.Jnstname.label!⇒Jnstlabel,
* McsEngl.Jnst'label!⇒Jnstlabel,
Jnstname.source
description::
"It contains a language-dependent short text describing the source of the dataset."
[{2020-12-29} https://json-stat.org/format/#source]
× aJsonsunt: [string]
× bRequired: false
× nSince: 1.0
× sParent: root, dimension-ID, relation-ID array element
× sChild: none
name::
* McsEngl.Jnstsource,
* McsEngl.Jnstname.source!⇒Jnstsource,
* McsEngl.Jnst'source!⇒Jnstsource,
Jnstname.updated
description::
"It contains the update time of the dataset. It is a string representing a date in an ISO 8601 format recognized by the Javascript Date.parse method (see ECMA-262 Date Time String Format)."
[{2020-12-29} https://json-stat.org/format/#updated]
× aJsonsunt: [string]
× bRequired: false
× nSince: 1.0
× sParent: root, dimension-ID, relation-ID array element
× sChild: none
name::
* McsEngl.Jnstupdated,
* McsEngl.Jnstname.updated!⇒Jnstupdated,
* McsEngl.Jnst'updated!⇒Jnstupdated,
Jnstname.value
description::
"It contains the data sorted according to the dataset dimensions. It usually takes the form of an array where missing values are expressed as nulls.
... When too many cube cells are empty (sparse cube), the value array is populated with nulls.
... To avoid this, the value property can take the form of an object.
Value order follows the “What does not change, first” criterion. According to this criterion, values are ordered by combination of category dimensions keeping fixed the first categories of the first dimensions and iterating through the categories of the last dimension in the id array (and so forth).
For example, if we have three dimensions (A, B and C) with 3, 2 and 4 categories respectively, the values should be ordered iterating first by the 4 categories of C, then by the 2 categories of B and finally by the 3 categories of A:
A1B1C1 A1B1C2 A1B1C3 A1B1C4
A1B2C1 A1B2C2 A1B2C3 A1B2C4
A2B1C1 A2B1C2 A2B1C3 A1B1C4
A2B2C1 A2B2C2 A2B2C3 A2B2C4
A3B1C1 A3B1C2 A3B1C3 A3B1C4
A3B2C1 A3B2C2 A3B2C3 A3B2C4
This flattening method is known as row-major order."
[{2020-12-29} https://json-stat.org/format/#value]
× aJsonsunt: [array, object]
× bRequired: true
× nSince: 1.0
× sParent: root (when class "dataset"), relation-ID array element
× sChild: none
name::
* McsEngl.Jnstvalue,
* McsEngl.Jnstname.value!⇒Jnstvalue,
* McsEngl.Jnst'value!⇒Jnstvalue,
Jnstname.dimension
description::
"JSON-stat follows a cube model: the values are organized in cells, and a cell is the intersection of various dimensions. The dimension property contains information about the dimensions of the dataset.
dimension must have properties (see dimension-ID) with the same names of each element in the id array.
Before version 2.0
Properties id, size and role were children of dimension."
[{2020-12-29} https://json-stat.org/format/#dimension]
× aJsonsunt: [object]
× bRequired: true
× nSince: 1.0
× sParent: root (when class "dataset"), relation-ID array element
× sChild: dimension-ID
name::
* McsEngl.Jnstdimension,
* McsEngl.Jnstname.dimension!⇒Jnstdimension,
* McsEngl.Jnst'dimension!⇒Jnstdimension,
Jnstname.dimension-ID
description::
"It is used to describe a particular dimension. The name of this object must be one of the strings in the id array. There must be one and only one dimension-ID object for every dimension in the id array.
"dimension" : {
"metric" : { … },
"time" : { … },
"geo" : { … },
"sex" : { … },
…
}"
× aJsonsunt: [array]
× bRequired: true
× nSince: 1.0
× sParent: dimension
× sChild: category, label, class
name::
* McsEngl.JnstdimensionID,
* McsEngl.Jnstname.dimension-ID!⇒JnstdimensionID,
* McsEngl.Jnst'dimensionID!⇒JnstdimensionID,
Jnstname.id
description::
"It contains an ordered list of dimension-IDs.
"class": "dataset",
"id" : ["metric", "time", "geo", "sex"],
Dimension IDs can be any string and have no special meaning in JSON-stat. Use role to assign a particular meaning to them.
Before version 2.0
Properties id, size and role were children of dimension.
Data providers that depend on JSON-stat libraries that are not yet 2.0-ready are advised, as a transitional strategy, to include those three properties at the root level (2.0) and as children of dimension (<2.0)."
[{2020-12-29} https://json-stat.org/format/#id]
× aJsonsunt: [array]
× bRequired: true
× nSince: 1.0
× sParent: root (when class "dataset"), relation-ID array element
× sChild: none
name::
* McsEngl.Jnstid,
* McsEngl.Jnstname.id!⇒Jnstid,
* McsEngl.Jnst'id!⇒Jnstid,
Jnstname.size
description::
"It contains the number (integer) of categories (possible values) of each dimension in the dataset. It has the same number of elements and in the same order as in id.
...
"id" : ["metric", "time", "geo", "sex"],
"size" : [1, 1, 1, 3],
...
Before version 2.0
Properties id, size and role were children of dimension.
Data providers that depend on JSON-stat libraries that are not yet 2.0-ready are advised, as a transitional strategy, to include those three properties at the root level (2.0) and as children of dimension (<2.0)."
[{2020-12-29} https://json-stat.org/format/#size]
× aJsonsunt: [array]
× bRequired: true
× nSince: 1.0
× sParent: root (when class "dataset"), relation-ID array element
× sChild: none
name::
* McsEngl.Jnstsize,
* McsEngl.Jnstname.size!⇒Jnstsize,
* McsEngl.Jnst'size!⇒Jnstsize,
Jnstname.category
description::
"It is used to describe the possible values of a dimension."
× aJsonsunt: [object]
× bRequired: true
× nSince: 1.0
× sParent: root (when class "dimension"), dimension-ID, relation-ID array element
× sChild: index, label, child, coordinates, unit
name::
* McsEngl.Jnstcategory,
* McsEngl.Jnstname.category!⇒Jnstcategory,
* McsEngl.Jnst'category!⇒Jnstcategory,
Jnstname.child
description::
"It is used to describe the hierarchical relationship between different categories. It takes the form of an object where the key is the ID of the parent category and the value is an array of the IDs of the child categories. It is also a way of exposing a certain category as a total."
[{2020-12-29} https://json-stat.org/format/#child]
× aJsonsunt: [object]
× bRequired: false
× nSince: 1.0
× sParent: category
× sChild: none
name::
* McsEngl.Jnstchild,
* McsEngl.Jnstname.child!⇒Jnstchild,
* McsEngl.Jnst'child!⇒Jnstchild,
Jnstname.coordinates
description::
"It can be used to assign longitude/latitude geographic coordinates to the categories of a dimension with a geo role. It takes the form of an object where keys are category IDs and values are an array of two numbers (longitude, latitude).
"category" : {
"label" : {
"ISO-3166-2:TV" : "Tuvalu"
},
"coordinates" : {
"ISO-3166-2:TV" : [179.1995, -8.5199]
}
}
The goal of JSON-stat is not to provide rich geographical information. To that purpose, use GeoJSON or TopoJSON and match your maps areas in those formats with statistical data (in JSON-stat) encoding your geographical categories with common IDs."
[{2020-12-29} https://json-stat.org/format/#coordinates]
× aJsonsunt: [object]
× bRequired: false
× nSince: 1.0
× sParent: category
× sChild: none
name::
* McsEngl.Jnstcoordinates,
* McsEngl.Jnstname.coordinates!⇒Jnstcoordinates,
* McsEngl.Jnst'coordinates!⇒Jnstcoordinates,
Jnstname.index
description::
"It is used to order the possible values (categories) of a dimension. The order of the categories and the order of the dimensions themselves determine the order of the data in the value array. While the dimensions’ order has only this functional role (and therefore any order chosen by the provider is valid), the categories’ order has also a presentation role: it is assumed that the categories are sorted in a meaningful order and that the consumer can rely on it when displaying the information. For example, categories in dimensions with a time role are assumed to be in chronological order.
To provide the category IDs and their order, an array can be used.
"sex" : {
"category" : {
"index" : ["M", "F", "T"]
}
}
For efficiency reasons (see Arrays vs. Objects), an object that attaches a position to every ID can also be used (this is currently the recommended format).
"sex" : {
"category" : {
"index" : {
"M" : 0,
"F" : 1,
"T" : 2
}
}
}
index is required unless the dimension is a constant dimension (dimension with a single category). When a dimension has only one category, the index property is indeed unnecessary. In the case that a category index is not provided, a category label must be included."
[{2020-12-29} https://json-stat.org/format/#index]
× aJsonsunt: [object, array]
× bRequired: false
× nSince: 1.0
× sParent: category
× sChild: none
name::
* McsEngl.Jnstindex,
* McsEngl.Jnstname.index!⇒Jnstindex,
* McsEngl.Jnst'index!⇒Jnstindex,
Jnstname.unit
description::
"It can be used to assign unit of measure metadata to the categories of a dimension with a metric role.
"role": {
"metric": ["concept"]
}
It takes the form of an object where category ID is the key and the value is an object.
"concept" : {
"category" : {
"label" : {
"pop" : "population"
},
"unit" : {
"pop" : { … }
}
}
}
Four properties of this object are currently closed: decimals, label, symbol and position.
"unit" : {
"exp" : {
"decimals": 1,
"label" : "millions",
"symbol" : "$",
"position" : "start"
}
}
Following the previous example, a client could display a value of 10 of metric exp as “$10.0 millions”.
Based on current standards and practices, other properties of this object could be:
* base: It is the base unit (person, gram, euro, etc.).
* type: This property should probably help deriving new data from the data. It should probably help answering questions like: does it make sense to add two different cell values? Some possible values of this property could be count or ratio. Some might also consider as possible values things like currency, mass, length, time, etc.
* multiplier: It is the unit multiplier. It should help comparing data with the same base unit but different multiplier. If a decimal system is used, it can be expressed as powers of 10 (0=1, 1=10, -1=0.1, etc.).
* adjustment: A code to express the time series adjustment (for example, seasonally adjusted or adjusted by working days) or indices adjustment (for example, chain-linked indices).
These properties are currently open. Data providers are free to use them on their own terms, although it is safer to do it under extension."
[{2020-12-29} https://json-stat.org/format/#unit]
× aJsonsunt: [object]
× bRequired: false
× nSince: 1.0
× sParent: category
× sChild: category-ID
name::
* McsEngl.Jnstunit,
* McsEngl.Jnstname.unit!⇒Jnstunit,
* McsEngl.Jnst'unit!⇒Jnstunit,
Jnstname.symbol
description::
"It contains a possible unit symbol to add to the value when it is displayed (like “€”, “$” or “%”)."
[{2020-12-29} https://json-stat.org/format/#symbol]
× aJsonsunt: [string]
× bRequired: false
× nSince: 1.2
× sParent: Unit category ID
× sChild: none
name::
* McsEngl.Jnstsymbol,
* McsEngl.Jnstname.symbol!⇒Jnstsymbol,
* McsEngl.Jnst'symbol!⇒Jnstsymbol,
Jnstname.position
description::
"It contains the place (start or end, strings) where the unit symbol should be written (before or after the value). Default is end."
[{2020-12-29} https://json-stat.org/format/#position]
× aJsonsunt: [string]
× bRequired: false
× nSince: 1.2
× sParent: Unit category ID
× sChild: none
name::
* McsEngl.Jnstposition,
* McsEngl.Jnstname.position!⇒Jnstposition,
* McsEngl.Jnst'position!⇒Jnstposition,
Jnstname.decimals
description::
"It contains the number of unit decimals (integer). If unit is present, decimals is required."
[{2020-12-29} https://json-stat.org/format/#decimals]
× aJsonsunt: [number]
× bRequired: false
× nSince: 1.2
× sParent: Unit category ID
× sChild: none
name::
* McsEngl.Jnstdecimals,
* McsEngl.Jnstname.decimals!⇒Jnstdecimals,
* McsEngl.Jnst'decimals!⇒Jnstdecimals,
Jnstname.error
description::
"Besides using HTTP status codes, JSON-stat documents can include the error property to communicate response errors. It takes the form of an array of objects, each providing information for an error. Libraries should offer a method to retrieve this array but should also check the validity of the response, as the inclusion of error is not mandatory.
Based on current standards and practices, possible error elements could be:
* status: The HTTP status code (for example, "401").
* id: The provider’s internal error code (for example, "106").
* href: A link to a web page where information about this error is published (for example, "http://example.com/error/106").
* label: A short descriptive text about the error. It can be useful to provide two properties: one for the end user ("The selected country does not exist.") and one for the developer ("Parameter 'area' must be an ISO 3166-1 alpha-2 code.")."
[{2020-12-29} https://json-stat.org/format/#error]
× aJsonsunt: [array]
× bRequired: false
× nSince: 1.1
× sParent: root
× sChild: open
name::
* McsEngl.Jnsterror,
* McsEngl.Jnstname.error!⇒Jnsterror,
* McsEngl.Jnst'error!⇒Jnsterror,
Jnstname.link
description::
"It is used to provide a list of links related to a dataset or a dimension, sorted by relation (see relation-ID).
{
"version" : "2.0",
"class" : "dataset",
"label" : "Tuvalu population by sex in the 2002 Census",
"href" : "http://example.com/2002/population/sex",
"link" : {
"alternate" : [
{
"type" : "text/csv",
"href" : "http://example.com/2002/population/sex.csv"
}
],
…
},
…
}"
[{2020-12-29} https://json-stat.org/format/#link]
× aJsonsunt: [object]
× bRequired: false
× nSince: 1.1
× sParent: root, dimension-ID, relation-ID array element
× sChild: none
name::
* McsEngl.Jnstlink,
* McsEngl.Jnstname.link!⇒Jnstlink,
* McsEngl.Jnst'link!⇒Jnstlink,
Jnstname.relation-ID
description::
"This ID must be an IANA link relation name that describes the relation between the elements of the array and the parent of link.
When used to link to non-JSON-stat documents, the elements of the array are objects that can contain a type and an href property.
{
"version" : "2.0",
"class" : "dataset",
"link" : {
"alternate" : [
{
"type" : "text/csv",
"href" : "http://example.com/2002/population/sex.csv"
},
{
"type" : "text/html",
"href" : "http://example.com/2002/population/sex.html"
}
],
…
},
…
}
When used to link to JSON-stat documents, they can contain the common JSON-stat properties class, label, href and extension.
{
"version" : "2.0",
"class" : "collection",
"href" : "https://json-stat.org/samples/collection.json",
"label" : "JSON-stat Dataset Sample Collection",
"updated" : "2015-07-02",
"link" : {
"item" : [
{
"class" : "dataset",
"href" : "https://json-stat.org/samples/oecd.json",
"label" : "Unemployment rate in the OECD countries 2003-2014"
},
{
"class" : "dataset",
"href" : "https://json-stat.org/samples/canada.json",
"label" : "Population by sex and age group. Canada. 2012"
},
{
"class" : "dataset",
"href" : "https://json-stat.org/samples/galicia.json",
"label" : "Population by province of residence, place of birth, age, gender and year in Galicia"
},
{
"class" : "dataset",
"href" : "https://json-stat.org/samples/us-gsp.json",
"label" : "US States by GSP and population"
},
{
"class" : "dataset",
"href" : "https://json-stat.org/samples/us-unr.json",
"label" : "Unemployment Rates by County, 2012 Annual Averages"
},
{
"class" : "dataset",
"href" : "https://json-stat.org/samples/us-labor.json",
"label" : "Labor Force Data by County, 2012 Annual Averages"
},
{
"class" : "dataset",
"href" : "https://json-stat.org/samples/order.json",
"label" : "Demo of value ordering: what does not change, first"
},
{
"class" : "dataset",
"href" : "https://json-stat.org/samples/hierarchy.json",
"label" : "Demo of hierarchical dimension"
}
]
}
}
They can also be used to embed full JSON-stat responses of any class.
{
"version" : "2.0",
"class" : "collection",
"href" : "https://json-stat.org/samples/oecd-canada-col.json",
"label" : "OECD-Canada Sample Collection",
"updated" : "2015-12-24",
"link" : {
"item" : [
{
"class" : "dataset",
"href" : "https://json-stat.org/samples/oecd.json",
"label" : "Unemployment rate in the OECD countries 2003-2014",
"source" : "Economic Outlook No 92 - December 2012 - OECD Annual Projections",
"updated" : "2012-11-27",
"value" : [5.943826289, 5.39663128, 5.044790587, …],
"id" : ["concept", "area", "year"],
"size" : [1, 36, 12],
"dimension" : {
…
},
…
},
…
]
}
},
…
}"
· external-word
× aJsonsunt: [array]
× bRequired: false
× nSince: 1.1
× sParent: link
× sChild: none
name::
* McsEngl.JnstrelationID,
* McsEngl.Jnstname.relation-ID!⇒JnstrelationID,
* McsEngl.Jnst'relationID!⇒JnstrelationID,
Jnstname.note
description::
"This is a property similar to label. The main differences are:
note is used to assign annotations instead of a descriptive text where label uses a string, note uses an array of strings Please, see label for a general description.
{
"version" : "2.0",
"class" : "dataset",
"note" : [ "Most of the data in this dataset ..." ],
"dimension" : {
"country" : {
"note" : [ "Except where otherwise ..." ],
"category" : {
"note" : {
"DEU" : [ "Germany (code DEU) ..." ]
},
…
},
…
},
…
},
…
}
note allows to assign annotations to datasets (array), dimensions (array) and categories (object). To assign annotations to individual data, use status."
[{2020-12-29} https://json-stat.org/format/#note]
× aJsonsunt: [array, object]
× bRequired: false
× nSince: 1.1
× sParent: none, dimension-ID, category, relation-ID array element
× sChild: none
name::
* McsEngl.Jnstnote,
* McsEngl.Jnstname.note!⇒Jnstnote,
* McsEngl.Jnst'note!⇒Jnstnote,
Jnstname.role
description::
"It can be used to assign special roles to dimensions. At this moment, possible roles are: time, geo and metric. A role can be shared by several dimensions.
{
"version" : "2.0",
"class" : "dataset",
"id" : ["concept", "arrivaldate", "departuredate", "origin", "destination"],
"size" : [1, 24, 24, 10, 10],
"role": {
"time": ["arrivaldate", "departuredate"],
"geo": ["origin", "destination"],
"metric": ["concept"]
},
…
}
Before version 2.0
Properties id, size and role were children of dimension.
Data providers that depend on JSON-stat libraries that are not yet 2.0-ready are advised, as a transitional strategy, to include those three properties at the root level (2.0) and as children of dimension (<2.0)."
[{2020-12-29} https://json-stat.org/format/#role]
× aJsonsunt: [object]
× bRequired: false
× nSince: 1.0
× sParent: root (when class "dataset"), relation-ID array element
× sChild: time, geo and metric
name::
* McsEngl.Jnstrole,
* McsEngl.Jnstname.role!⇒Jnstrole,
* McsEngl.Jnst'role!⇒Jnstrole,
Jnstname.geo
description::
"It can be used to assign a spatial role to one or more dimensions. It takes the form of an array of dimension-IDs in which order does not have a special meaning.
"role": {
"geo": ["origin", "destination"]
}"
[{2020-12-29} https://json-stat.org/format/#geo]
× aJsonsunt: [array]
× bRequired: false
× nSince: 1.0
× sParent: role
× sChild: none
name::
* McsEngl.Jnstgeo,
* McsEngl.Jnstname.geo!⇒Jnstgeo,
* McsEngl.Jnst'geo!⇒Jnstgeo,
Jnstname.time
description::
"It can be used to assign a time role to one or more dimensions. It takes the form of an array of dimension-IDs in which order does not have a special meaning.
"role": {
"time": ["arrivaldate", "departuredate"]
}"
[{2020-12-29} https://json-stat.org/format/#time]
× aJsonsunt: [array]
× bRequired: fale
× nSince: 1.0
× sParent: role
× sChild: none
name::
* McsEngl.Jnsttime,
* McsEngl.Jnstname.time!⇒Jnsttime,
* McsEngl.Jnst'time!⇒Jnsttime,
Jnstname.metric
description::
"It can be used to assign a metric role to one or more dimensions. It takes the form of an array of dimension-IDs in which order does not have a special meaning.
"role": {
"metric": ["concept"]
}"
[{2020-12-29} https://json-stat.org/format/#metric]
× aJsonsunt: [array]
× bRequired: false
× nSince: 1.0
× sParent: role
× sChild: none
name::
* McsEngl.Jnstmetric,
* McsEngl.Jnstname.metric!⇒Jnstmetric,
* McsEngl.Jnst'metric!⇒Jnstmetric,
Jnstname.status
description::
"It contains metadata at the observation level. When it takes an array form of the same size of value, it assigns a status to each data by position.
{
"version" : "2.0",
"class" : "dataset",
"value" : [100, null, 102, 103, 104],
"status" : ["a", "m", "a", "a", "p"],
…
}
To assign the same status to all data, an array of size 1 can be used.
{
"version" : "2.0",
"class" : "dataset",
"value" : [100, 99, 102, 103, 104],
"status" : ["e"],
…
}
For the same purpose, a string can be used (this is the recommended way to assign the same status to all data).
{
"version" : "2.0",
"class" : "dataset",
"value" : [100, 99, 102, 103, 104],
"status" : "e",
…
}
An object can also be used to provide status information for specific cells.
{
"version" : "2.0",
"class" : "dataset",
"value" : [100, null, 102, 103, 104],
"status" : { "1" : "m" },
…
}
Currently, “status” does not have a standard meaning nor a standard vocabulary. These are, for the moment, up to the provider. It can be used to optionally include any metadata information at the observation level, not only what is regularly known as “status”. If the vocubulary does not adhere to a standard, there is no way yet to assign meaning to the status codes in the same response."
[{2020-12-29} https://json-stat.org/format/#status]
× aJsonsunt: [array, object, string]
× bRequired: false
× nSince: 1.0
× sParent: root (when class "dataset"), relation-ID array element
× sChild: none
name::
* McsEngl.Jnststatus,
* McsEngl.Jnstname.status!⇒Jnststatus,
* McsEngl.Jnst'status!⇒Jnststatus,
Jnstname.type
description::
"It describes the media type of the accompanying href. Not required when the resource referenced in the link is a JSON-stat resource."
[{2020-12-29} https://json-stat.org/format/#type]
× aJsonsunt: [string]
× bRequired: false
× nSince: 1.1
× sParent: relation-ID array element
× sChild: none
name::
* McsEngl.Jnsttype,
* McsEngl.Jnstname.type!⇒Jnsttype,
* McsEngl.Jnst'type!⇒Jnsttype,
Jnstname.extension
description::
"extension allows JSON-stat to be extended for particular needs. Providers are free to define where they include this property and what children are allowed in each case."
[{2020-12-29} https://json-stat.org/format/#extension]
× aJsonsunt: [object]
× bRequired: false
× nSince: 1.1
× sParent: root, dimension-ID, relation-ID array element
× sChild: open
name::
* McsEngl.Jnstextension,
* McsEngl.Jnstname.extension!⇒Jnstextension,
* McsEngl.Jnst'extension!⇒Jnstextension,
