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

Implement communication protocol between SensorNode and ManagementNode #11

Open
1 of 2 tasks
asorici opened this issue Aug 5, 2019 · 0 comments
Open
1 of 2 tasks
Assignees
Labels
enhancement New feature or request

Comments

@asorici
Copy link
Collaborator

asorici commented Aug 5, 2019

Why

Because there has to be one, obviously :-)
The ContextDomainGroup managed by a ManagementNode needs to be modeled as a ThingDescription entity, as well.

What

  • implement 3 default Thing description properties
    • the GET on a base representation URI (http://<baseUri>/coord/location/<domainName>) returns the description of the ContextDomain
    • the GET on <baseRep>/providers returns the list of registered SensorNodes
    • the GET on <baseRep>/capabilities returns the list of capabilities (ThingDescription modeled devices)
  • implement 1 ThingDescription action - join - by which SensorNode can register itself and its capabilities (the devices it manages, modeled as ThingDescription entities)

Notes

All communication payloads are transmitted as RDF triplets.

@asorici asorici added the enhancement New feature or request label Aug 5, 2019
asorici added a commit that referenced this issue Mar 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants