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.

Sign up for GitHub

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

Jump to bottom

Clarify Discovery API scope #206

Open
zolkis opened this issue Feb 25, 2020 · 3 comments
Open

Clarify Discovery API scope #206

zolkis opened this issue Feb 25, 2020 · 3 comments
Labels
discovery Relates to discovery and/or relates to joint work/discussions with the discovery task force F2F Topics related to Face-to-Face meetings propose closing Solutions exists and labelled as to be closed soon Waiting for feedback Issues and PRs that are awaiting feedback from another group or institution.

Comments

@zolkis
Copy link
Contributor

zolkis commented Feb 25, 2020

As discussed in the Discovery TF call on 24.2.2020, the scope of the Scripting API for discovery needs some clarifications vs device lifecycle, discussed in Architecture TF.

There are several types of discovery:

  1. discovery during onboarding/provisioning (e.g. of unowned devices)
  2. discovery of Thing directories, during provisioning or in operational mode
  3. discovery of Things (when in operational mode).

The current API has been designed with 3. in mind, but could be adapted to be used also for 1. and 2.

Related issues:
w3c/wot-discovery#2
w3c/wot-architecture#48
https://github.com/w3c/wot-architecture/issues/425
See also:
Device lifecycle comparisons
WoT Device Lifecycle working draft
@zolkis zolkis added the F2F Topics related to Face-to-Face meetings label Jun 18, 2020
@danielpeintner
Copy link
Contributor

Note: I suggest to remove the F2F label and re-label it with discovery

@JKRhb JKRhb added the discovery Relates to discovery and/or relates to joint work/discussions with the discovery task force label Dec 11, 2023
@JKRhb
Copy link
Member

JKRhb commented Dec 11, 2023

Although the Discovery aspects have been improved, I suppose some clarifications could still be added to the specification?

@relu91 relu91 added the propose closing Solutions exists and labelled as to be closed soon label Jan 22, 2024
@relu91 relu91 added the Waiting for feedback Issues and PRs that are awaiting feedback from another group or institution. label Jan 29, 2024
@relu91
Copy link
Member

relu91 commented Jan 29, 2024

Call 29/01:

  • @zolkis needs to review the issue and close it if needed. We are waiting for his review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discovery Relates to discovery and/or relates to joint work/discussions with the discovery task force F2F Topics related to Face-to-Face meetings propose closing Solutions exists and labelled as to be closed soon Waiting for feedback Issues and PRs that are awaiting feedback from another group or institution.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@zolkis @relu91 @danielpeintner @JKRhb