Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible requirement: allow discovery to return metadata in different formats #14

Closed
mmccool opened this issue Mar 30, 2020 · 2 comments
Assignees

Comments

@mmccool
Copy link
Contributor

mmccool commented Mar 30, 2020

  • 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.

@mmccool mmccool self-assigned this Apr 6, 2020
@mmccool
Copy link
Contributor Author

mmccool commented Apr 6, 2020

From 06.04.2020 meeting

Pros:

  • 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

@mmccool
Copy link
Contributor Author

mmccool commented Apr 6, 2020

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...)

  • Issue closed; conclusion is NO.

@mmccool mmccool closed this as completed Apr 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant