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

Clarify meaning of "capabilities" and "roles" #8

Closed
adammontville opened this issue Apr 17, 2015 · 4 comments
Closed

Clarify meaning of "capabilities" and "roles" #8

adammontville opened this issue Apr 17, 2015 · 4 comments

Comments

@adammontville
Copy link
Contributor

Henk raised this issue during the 2015-04-17 endpoint ID design meeting. The present architecture draft doesn't clearly articulate what a "capability" and sometimes (potentially) confuses "capability" with "role". These terms and their use should be clarified.

@llorenzin
Copy link

Resolution

  • change existing use of "capability" to "function"
  • add a discussion of "capability" as being able to talk a specific data model, data operations, or SACM transport
  • be specific about what kind of capability / what kind of function we're talking about
  • data plane function / control plane function reside in the SACM component
  • data plane capabilities / control plane capabilities can be discovered via querying the controller

@llorenzin
Copy link

Started fixes in -04

  • changed existing use of "capability" to "function"
  • stubbed in a section for "capability" / discovery
  • clarifications around functions

@llorenzin
Copy link

Henk is okay with closing this issue.

@jimsch
Copy link
Contributor

jimsch commented Sep 24, 2015

Given that the comment says that it was started in -04 has this been finished yet?

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

No branches or pull requests

3 participants