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

Discovery of exposed Things on the same runtime - Issue 233 from w3c/wot #227

Open
egekorkan opened this issue Jul 28, 2020 · 3 comments
Open

Discovery of exposed Things on the same runtime - Issue 233 from w3c/wot #227

egekorkan opened this issue Jul 28, 2020 · 3 comments
Labels
discovery Relates to discovery and/or relates to joint work/discussions with the discovery task force for next iteration Planned or postponed topics for the future priority: low Issues that might be deferred for later use case Describes a scenario that may be useful for technical decisions Waiting for other Taskforce Issues and PRs that depend on a feature or the resolution of a discussion from another WoT Taskforce

Comments

@egekorkan
Copy link
Contributor

This is a rather issue coming over from w3c/wot at w3c/wot#233

There is also a somewhat related issue at node-wot at eclipse-thingweb/node-wot#160
@egekorkan egekorkan mentioned this issue Jul 28, 2020
Closed
@danielpeintner
Copy link
Contributor

Scripting Call 2020-10-19
related to "local" in planned discovery work
Note: node-wot does not (yet) implement discovery as a whole

"direct" discovery for each binding could (should?) be describable -> create dedicated scripting API issue (@relu91)

@danielpeintner danielpeintner added the discovery Relates to discovery and/or relates to joint work/discussions with the discovery task force label Nov 30, 2020
@JKRhb
Copy link
Member

JKRhb commented Dec 11, 2023

I think part of this discussion has now moved to w3c/wot-discovery#440 – is there still something we would need to add to the Scripting API as well?

@zolkis
Copy link
Contributor

zolkis commented Dec 11, 2023

It's still open, waiting for results of the discussion in the other issue.

@JKRhb JKRhb added the Waiting for other Taskforce Issues and PRs that depend on a feature or the resolution of a discussion from another WoT Taskforce label Dec 11, 2023
@relu91 relu91 added use case Describes a scenario that may be useful for technical decisions for next iteration Planned or postponed topics for the future priority: low Issues that might be deferred for later labels Jan 22, 2024
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 for next iteration Planned or postponed topics for the future priority: low Issues that might be deferred for later use case Describes a scenario that may be useful for technical decisions Waiting for other Taskforce Issues and PRs that depend on a feature or the resolution of a discussion from another WoT Taskforce
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@zolkis @relu91 @danielpeintner @JKRhb @egekorkan