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
Should a directory service support content negotiation and return metadata in different formats, eg. Vorto, OpenAPI, WoT TDs?
What formats? How can a directory service state which formats it supports? What is the minimal set? What is the canonical form? How can a requestor request a particular format?
Please comment on Pros and Cons in comments.
The text was updated successfully, but these errors were encountered:
Integrate with systems and ecosystems that already support other metadata formats, etc. OpenAPI
Cons:
Implementation complexity
Interoperability downside: don't know in advance what formats are supported (although we could make WoT TDs mandatory as a minimal set).
We should focus on supporting W3C standards; if a service already exists to support other formats that can remain and be used as needed... whether or not they share backends is an implementation issue and need not be visible at the network API level
In 06.04.2020 meeting
resolution: a WoT discovery service should support only WoT TDs. Content negotiation, if supported, should only be used to select between different versions of TDs (when there is more than one...)
Please comment on Pros and Cons in comments.
The text was updated successfully, but these errors were encountered: