Correct links and add examples. (72cc8556) · Commits · DATA - Data Solutions / Specifications / TS 104 175

md/annex-c.md

+1 −1

Original line number	Diff line number	Diff line
		@@ -1327,7 +1327,7 @@ one.
		}
		```

		#### C.2.3.2 Concise represenatation
		#### C.2.3.2 Concise representation

		The concise representation is a terser, lossless form of the normalized
		representation, where redundant Attribute _`type`_ members are omitted and the

md/clause-5.md

+52 −6

Original line number	Diff line number	Diff line
		@@ -3834,7 +3834,7 @@ distributed queries, the values of _`scope`_ are merged. The value of _`scope`_
		is represented as a JSON array in case there is more than one Scope. For the
		Temporal Evolution a given Scope is considered valid from the time it has been
		set until the time it has been explicitly removed by an update or delete
		operation (for an example see Annex A, Clause+++annex-c+++A.15).
		operation (for an example see Annex C, Clause+++annex-c+++C.11).

		The grammar that encodes the syntax of the Scope is expressed in ABNF format
		[n.16]. It is described below (it has been validated using
		@@ -5052,6 +5052,32 @@ data type described above:
		["VocabProperty"]{.HTML-Code}, ["ListProperty"]{.HTML-Code},
		["Relationship"]{.HTML-Code}, ["JsonProperty"]{.HTML-Code}

		<!-- prettier-ignore-start -->

		>>> [!tip]

		```json
		"speed": {
		"type": "Property",
		"values": [
		{
		"value": 120,
		"unitCode": "KMH",
		"observedAt": "2018-08-01T12:03:00Z"
		},
		{
		"value": 80,
		"unitCode": "KMH",
		"observedAt": "2018-08-01T12:05:00Z"
		}
		]
		}
		```

		>>>

		<!-- prettier-ignore-end -->

		Multi-Attribute Representation

		In the multi-attribute case (see Clause+++clause-8+++8.5), the temporal values
		@@ -5425,7 +5451,7 @@ temporal Entity data after applying an aggregation function on the values of the
		Attribute instances. The aggregated temporal representation of Entities shall be
		supported by implementations supporting the temporal representation of Entities
		and can be selected by [Context Consumers]{.HTML-Keyboard} through specific
		request parameters. An example can be found in Annex A, Clause+++annex-a+++A.14.
		request parameters.

		The aggregation function is applied according to the following principles:

		@@ -5470,9 +5496,6 @@ The aggregated temporal representation of an Entity shall include the following:
		2. the start _DateTime_
		3. the end _DateTime_

		An example of this aggregated temporal representation can be found in Annex A,
		Clause+++annex-a+++A.14

		Supported behaviours for aggregation functions

		In order to support such aggregation functions, two parameters are defined:
		@@ -5621,12 +5644,35 @@ Table: Semantics of aggregation methods for Relationships

		<!-- prettier-ignore-end -->


		<!-- prettier-ignore-start -->

		>>> [!tip]

		```json
		"speed": {
		"type": "Property",
		"max": [
		[120, "2018-08-01T12:00:00Z", "2018-08-01T12:04:00Z"],
		[100, "2018-08-01T12:04:00Z", "2018-08-01T12:08:00Z"]
		],
		"avg": [
		[120, "2018-08-01T12:00:00Z", "2018-08-01T12:04:00Z"],
		[90, "2018-08-01T12:04:00Z", "2018-08-01T12:08:00Z"]
		]
		}
		```

		>>>

		<!-- prettier-ignore-end -->

		Multi-Attribute Representation

		In the multi-attribute case (see Clause+++clause-8+++8.5), the aggregated values
		of a multi-Attribute are held as an array of JSON-LD objects separated by
		`datasetId`. An example of this representation can be found in Annex C,
		Clause+++annex-c+++C.2.2.5
		Clause+++annex-c+++C.2.2.4.5

		### 5.3.3 GeoJSON

Admin message