Subject: [Asdf] Type and subtype coexistence #13

From: Carsten Bormann <[email-masked]>
Date: Mon, 25 Jan 2021 09:58:16 +0100

With sdfChoice merged, there is at least one issue that we should clear before submitting the internet-draft for the consensus call to become SDF 1.1:

https://github.com/ietf-wg-asdf/SDF/issues/13

This is almost a bike shed issue; views are going to differ based on what we imagine the “subtype” quality would be used for.

I’m leaning a bit towards the status quo here (i.e., always include a “type” quality with a “subtype” quality).  Even though there is redundancy, people who are used to json-schema.org will feel more comfortable if they still find the “type” quality).  This also facilitates introducing future subtypes, as processors that don’t know a new subtype can still process the type.  (This also brings up the question if a change like #12 would be useful for “subtype”, too — but that is a different kind of quality than the pure semantic annotation quality “unit”.)

I’d like to have a PR (making a chance or confirming the status quo in the text)) in the next couple of days; if you think you can contribute to one, please go ahead now.

If you think we should be addressing issues 11 and 12 before 1.1, please speak up now.  Also, if you know about any other issue not yet recorded in github, please do so (or speak up here).

Grüße, Carsten