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

Interoperability #166

Open
mlagally opened this issue Feb 9, 2022 · 0 comments
Open

Interoperability #166

mlagally opened this issue Feb 9, 2022 · 0 comments
Labels
P1 Priority 1 to be discussed (e.g., next week) requirement

Comments

@mlagally
Copy link
Contributor

mlagally commented Feb 9, 2022

Supporters: Oracle, Intel, Siemens, Fujitsu, Ben, Cristano

This is the most important objective of the profile. A TD Consumer satisfying the requirements of a profile should be able to process any TD also satisfying the profile and should be able to correctly interact with all affordances of the Thing such a TD describes.

Note: this implies that a profile has three parts:

  1. Restrictions on TDs
  2. Implementation requirements, constraints and behavioral assertions for Consumers
  3. Implementation requirements, constraints and behavioral assertions on Things

Note: We don't want to prevent a TD to have forms for additional protocols, but these can be ignored by compliant consumers, and could be removed without affecting profile comformance and compatibility. This may be useful for consumers that support multiple profiles.

@mlagally mlagally added requirement P1 Priority 1 to be discussed (e.g., next week) labels Feb 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 Priority 1 to be discussed (e.g., next week) requirement
Projects
None yet
Development

No branches or pull requests

1 participant