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

Credential instance references to non-registry concepts & competencies #234

Open
stuartasutton opened this issue Jun 13, 2019 · 1 comment
Assignees
Labels
Long-term technical issue Issues to be aware of, but which do not require action at this time.

Comments

@stuartasutton
Copy link

We need to discuss how references to competencies in non-CE registry repositories will/should/might be handled--e.g., a CE registry credential reference to a CASE encoded competency in a non-CE registry/repository. I'm making the assumption, for example, that a credential instance in the registry that references a competency in the IMS Case Registry (ICR) does so via our standards CredetialAlignmentObject--embodying the competency text and URI's pointing to relevant URI's in the ICR. [i.e., there's no CTDL-ASN decoding of the CASE version of the framework in the CER] This would mean that resolving either the node link or the framework link in that CredetialAlignmentObject would resolve: to (1) an html page in the ICR for the competency, or (2) ICR would return the relevant CASE data.

What are the implications in terms of the finder, etc.? Likely none at the moment since there's no means to resolve those URI. But what CE about that data in the wild? What about traversal of such links via the graph store.

@siuc-nate siuc-nate transferred this issue from CredentialEngine/Schema-Development Jun 18, 2019
@siuc-nate siuc-nate added the Long-term technical issue Issues to be aware of, but which do not require action at this time. label Jun 18, 2019
@siuc-nate
Copy link
Collaborator

@stuartasutton Is this issue still needed? Can it be closed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Long-term technical issue Issues to be aware of, but which do not require action at this time.
Projects
None yet
Development

No branches or pull requests

4 participants