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
IS-11 introduces Input and Output resources, which both have a /properties endpoint that uses the same IS-04 resource_core.json schema. Like IS-04, the label, description and tags of these resources are currently read-only.
Should IS-13 support these IS-11 resources or future additions to the shared NMOS data model somehow?
One difference that would currently make updating these Input/Output resources less useful is that they aren't registered and discoverable via the Query API.
In any case, another possibility would be that IS-11 directly adds support for an IS-13-like PATCH since it's not published yet...
(IS-08 also introduced Input and Output resources though I think these seem second tier, acting as they do as the interface between the Channel Map and Sources, Receivers or non-network I/O interfaces. IS-08 Inputs and Outputs do also have a read-only /properties endpoint, but it doesn't follow the same schema, having name (cf. label) and description but no tags. IS-08 also uses a more general identifier format rather than UUIDs.)
The text was updated successfully, but these errors were encountered:
During 2022-05-18 call, we discussed whether IS-13 Read/Write Node API functionality should actually be provided by the Node API itself, e.g. in an IS-04 v1.4.
Possible pros and cons:
maybe simplify a Node implementation as it doesn't need to provide different filtered views on the same data (or keep two copies in sync!), though nodes already need to do this to support multiple versions of the Node API
maybe simplify a Controller implementation as it doesn't need to discover the Read/Write Node API via Node services but can just use the new PATCH verb if the API supports v1.4, though clients already have to do similar to discover Connection API, Channel Mapping API, etc.
We also considered the IS-13 API being "write only" (PATCH but no GET verbs at all) but decided this isn't discoverable.
IS-11 introduces Input and Output resources, which both have a /properties endpoint that uses the same IS-04 resource_core.json schema. Like IS-04, the label, description and tags of these resources are currently read-only.
Should IS-13 support these IS-11 resources or future additions to the shared NMOS data model somehow?
One difference that would currently make updating these Input/Output resources less useful is that they aren't registered and discoverable via the Query API.
In any case, another possibility would be that IS-11 directly adds support for an IS-13-like
PATCH
since it's not published yet...(IS-08 also introduced Input and Output resources though I think these seem second tier, acting as they do as the interface between the Channel Map and Sources, Receivers or non-network I/O interfaces. IS-08 Inputs and Outputs do also have a read-only /properties endpoint, but it doesn't follow the same schema, having
name
(cf.label
) anddescription
but notags
. IS-08 also uses a more general identifier format rather than UUIDs.)The text was updated successfully, but these errors were encountered: