Commit a76f65d5 authored by Jason Fox's avatar Jason Fox
Browse files

Fixes from API Rapporteur Call discussion 

- correct JSONProperty casing
- remove `observedAt` if missing
- clarify application of expansion/compaction
parent a0edb15d

md/clause-10.md

+7 −10
Original line number Diff line number Diff line
@@ -464,7 +464,7 @@ Figure: Set Attribute Value use case 
  [BadRequestData]{.HTML-Error} shall be raised.

- If the request payload body is not a valid JSON document or the payload body

  contains ["urn:ngsi-ld:null"]{.HTML-Code} or contains [null]{.HTML-Code}

  (excepting for Attribute fragments representing a _JSONProperty_) then an

  (excepting for Attribute fragments representing a _JsonProperty_) then an

  error of type [InvalidRequest]{.HTML-Error} shall be raised.

- If the NGSI-LD endpoint does not know about the target Entity, because there

  is no existing Entity whose id (URI), and where specified type, is equivalent
@@ -502,8 +502,8 @@ Figure: Set Attribute Value use case 
  - If the Attribute value to be replaced is represented in the **value only**

    representation, the _`type`_ of any pre-existing Attribute in the target

    entity shall be preserved.

  - If a user _`@context`_ has been supplied, the Attribute Fragment shall

    undergo expansion prior to replacement (see clause 8.2.4)

  - Term to URI expansion within the Attribute Fragment shall be occur prior to

    Attribute value replacement (see clause 8.2.4)

  - If the Attribute whose value is to be set previously contained an

    _`observedAt`_ sub-Attribute and the value to be replaced is represented in

    the **value only** representation:
@@ -511,8 +511,7 @@ Figure: Set Attribute Value use case 
    - if an _`observedAt`_ timestamp is defined, then the _`observedAt`_

      sub-Attribute is updated using the timestamp supplied.

    - if no _`observedAt`_ timestamp is defined, then the _`observedAt`_

      sub-Attribute is updated using the timestamp of the [Context

      Broker]{.HTML-Keyboard}

      sub-Attribute is removed.



#### 10.2.6.5 Output data
@@ -2392,11 +2391,9 @@ Figure: Retrieve Attribute Value use case 
#### 10.4.4.5 Output data



A JSON or JSON-LD document representing an NGSI-LD Attribute Fragment as

mandated by clause 5.4.2, formatted according to the defined representation.



if an _`@context`_ is supplied and the returned Attribute corresponds to a

[VocabProperty]{.HTML-Keyboard}, the returned value shall be compacted according

to supplied _`@context`_.

mandated by clause 5.4.2, formatted according to the defined representation,

where URI to Term compaction shall be applied according to the supplied

_`@context`_.



If a language filter is specified and the returned Attribute corresponds to a

_LanguageProperty_, the _LanguageProperty_ in question shall be converted into a

md/clause-5.md

+1 −1
Original line number Diff line number Diff line
@@ -5871,7 +5871,7 @@ Entity ["type"]{.HTML-Code} and Attribute name can all be determined from the 
operation signature.















The value _`null`_ shall not appear within Attribute fragments, with a limited













exception for Attribute fragments representing a _JSONProperty_, such as













exception for Attribute fragments representing a _JsonProperty_, such as















[{"json": null}]{.HTML-Code}





























A representation of NGSI-LD Null is only allowed within an Attribute fragment