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

G-010 - Endpoint Discovery #16

Closed
jimsch opened this issue Mar 27, 2015 · 5 comments
Closed

G-010 - Endpoint Discovery #16

jimsch opened this issue Mar 27, 2015 · 5 comments

Comments

@jimsch
Copy link
Contributor

jimsch commented Mar 27, 2015

Version -04

I don't understand why this is not a sub case of requirement G-009. From the text is not clear that there is a reason to call this out separately.

@ncamwing
Copy link
Contributor

ncamwing commented May 4, 2015

Hi Jim,
Mainly because of my laziness.....but in reality, I think the group wanted to have an explicit requirement for endpoint discovery....I'll note it for wider discussion.

Nancy.

@llorenzin
Copy link

G-009 refers to information in the ecosystem - data (objects). G-010 refers to endpoints in the ecosystem - components (subjects). Does that help make it clear why these are separate requirements?

@jimsch
Copy link
Contributor Author

jimsch commented May 8, 2015

By the information in the ecosystem do you mean discovering the schema or discovering the individual pieces of data?

@ncamwing
Copy link
Contributor

ncamwing commented May 9, 2015

My interpretation is G-009 speaks to the available schemas/data models whereas as G-010 are the actual SACM endpoints in the ecosystem that can provide individual pieces of data.

@llorenzin
Copy link

Discussed at 6/29 virtual interim, done in -07

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants