Re: [Asdf] ASDF IETF 109 Hackathon (Friday)

[Carsten Bormann <[e-mail]>]

On 2020-11-13, at 15:21, Carsten Bormann <[e-mail]> wrote:
> 
> I created an sdf-1-1.cddl in branch "1-1" in https://github.com/ietf-wg-asdf/SDF"
> 
> https://github.com/ietf-wg-asdf/SDF/blob/1-1/sdf-1-1.cddl

And here is a narrated diff:

This is a new production that goes into what was pointer-lists in 1.0 and are dataqualities (our extended version of json-schema.org) now in 1.1:

62a63,66
> parameter-list =
>   pointer-list .feature "1.0" /
>   dataqualities .feature "1.1"  ; cddl-tool currently blurts out the value

(The comment points out a missing feature of “.feature” — can’t suppress a diagnostic output of the actual value, which is distracting here.)

This parameter-list is now used for sdfInputData (actions) and sdfOutputData (actions, events).
Note that sdfRequiredInputData is now deprecated in 1.1 (use required in the data qualities); I didn’t catch that one in the CDDL.

65c69
<  ? sdfInputData: pointer-list   ; sdfRequiredInputData applies here (a bit redundant)
---
>  ? sdfInputData: parameter-list   ; sdfRequiredInputData applies here (a bit redundant)
67c71
<  ? sdfOutputData: pointer-list  ; sdfRequired applies here
---
>  ? sdfOutputData: parameter-list  ; sdfRequired applies here
74c78
<  ? sdfOutputData: pointer-list  ; sdfRequired applies here
---
>  ? sdfOutputData: parameter-list  ; sdfRequired applies here


Trying to correct the “units” typo:

82c86,87
<  ? units: text
---
>  ? ("units" .feature "1.0") => text
>  ? ("unit" .feature "1.1") => text

Addition to “allowed-types” (e.g., value after “default”:):

96a102
>               / {* text => any}

Define a group for compound type.
I started to make use of co-occurrence here, so “required” and “properties” can only occur if type=object.  (I will hate having done this when I update the CDDL-to-json-schema.org converter for this; json-schema.org cannot do that.)

98a105,110
> compound-type = (
>   "type" => ("object" .feature "1.1"),
>   ? required: [+text],
>   ? properties: named<dataqualities>,
> )
> 

Use the compound type in dataqualities:

100,101c112,115
<  ? type: "number" / "string" / "boolean" / "integer" / "array" ; / "object"
<            / (text .feature "type-ext")                       ; EXTENSION-POINT
---
>  ? (("type" => "number" / "string" / "boolean" / "integer" / "array")
>     // compound-type
>     // (type: text .feature "type-ext")                       ; EXTENSION-POINT
>    )

Same in the nested “items”:

128,129c142,145
<      ? type: "number" / "string" / "boolean" / "integer" ; no "array" / "object"
<            / (text .feature "itemtype-ext")                       ; EXTENSION-POINT
---
>      ? ((type: "number" / "string" / "boolean" / "integer") ; no "array"
>         // compound-type
>         // (type: text .feature "itemtype-ext")                       ; EXTENSION-POINT
>        )

Comments welcome.
“See” you all in half an hour…

Grüße, Carsten