Comments (6)
mmccool
commented on August 11, 2024
Sorry, I meant to put this issue under Architecture. However, it does drive requirements if we consider "EdgeX integration" as a very specific use case ;)
from wot-usecases.
mmccool
commented on August 11, 2024
Metadata does seem to be oriented around "device instance" (similar to Thing Descriptions) not "classes" (eg Thing Models). Metadata service also seems to line up in functionality with what we are working on in the Discovery TF, so maybe I should also make a more specific issue to look at the EdgeX discovery architecture.
from wot-usecases.
mlagally
commented on August 11, 2024
@mmccool please carry over this issue into architecture and close here.
from wot-usecases.
mlagally
commented on August 11, 2024
UC call on May 4th:
Need to carry over and add a hub section in the architecture document.
from wot-usecases.
mlagally
commented on August 11, 2024
See architecture issue: w3c/wot-architecture#585
from wot-usecases.
mlagally
commented on August 11, 2024
UC call on May 11th:
Hub architecture is very similar to WebThings, some details probably are different.
Need to reengage EdgeX colleagues and talk to Krellian, ideally doing a prototype for an upcoming plugfest or POC.
from wot-usecases.
Related Issues (20)
- Update Privacy Requirements
- Review Discovery Requirements and Use Case Links HOT 3
- Update Status of each Discovery Requirement
- [Discuss] Focus on Functional Requirements HOT 11
- [Process] Not proceeding to feature definition if there is no gap HOT 1
- [Process] Not accepting Use Cases if there is no hint of a gap HOT 1
- [Process] Aligning with Relationship between groups document HOT 1
- Thoughts from the TD Use Case Discussions HOT 5
- How to extract information, e.g., about requirements, from the UC description? HOT 1
- When/which level of UC description to be generated? HOT 1
- Who/how to submit UCs? HOT 1
- How to deal with gap analysis? Ned clear definition for "gap analysis HOT 1
- How to deal with gap analysis? Need clear definition for "gap analysis" HOT 5
- The structure/category of the use case description HOT 1
- What level (technical, functional, business, etc.) to be described for use cases? HOT 1
- What would be the possible items for use case description?
- How to deal with the feedback from the TFs working on each specification HOT 1
- Expectations of the TD stakeholders from the Use Case process
- What we mean by "functional" and "technical"
- What we expect for "user stories" from the Use Case description HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from wot-usecases.