You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
arch-schema: Thus, the Interaction Affordance for structured data types SHOULD be associated with a data schema to provide more detailed syntactic metadata for the data exchanged.
arch-property-dataschema: If the data format is not fully specified by the Protocol Binding used (e.g., through a media type), Properties MAY contain one data schema for the exposed state.
arch-action-dataschema: If the data format is not fully specified by the Protocol Binding used (e.g., through a media type), Actions MAY contain data schemas for input parameters and output results.
arch-event-dataschema: If the data is not fully specified by the Protocol Binding used (e.g., through a media type), Events MAY contain data schemas for the event data and subscription control messages (e.g., a callback URI to subscribe with a Webhook).
I think that either 1 should stay and 2,3,4 should be removed or 1 should be removed and 2,3,4 should stay since they are overlapping
The text was updated successfully, but these errors were encountered:
Arch call on Nov 30th:
They are not exactly redundant.
To make the text more consistent, the MAY in 4,3,4 should be converted to SHOULD.
At this point we should not modify assertions, defer to next version of the architecture spec. If we need to do it earlier, we had to reopen the CR.
Agree to defer to next spec version.
There are the following 4 assertions in the spec:
I think that either 1 should stay and 2,3,4 should be removed or 1 should be removed and 2,3,4 should stay since they are overlapping
The text was updated successfully, but these errors were encountered: