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

to add note about process VCs in eComm use case #163

Merged
merged 1 commit into from
May 18, 2021

Conversation

bumblefudge
Copy link
Contributor

Down payment on #64 -- to be updated once process VCs multiply and again if/when process VCs get segregrated in a subfolder, prefixed, etc.

@bumblefudge
Copy link
Contributor Author

(happy to leave this open or close it and re-open later when there's more to do on this front.)

Copy link
Collaborator

@mprorock mprorock left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am OK with this for now - ultimately we will want to get this stuff resolved, then we can pull this note. It is however quite helpful for now. if we get some tagging added to objects we can classify these types of items and then they will be less problematic

@OR13
Copy link
Collaborator

OR13 commented May 13, 2021

@bumblefudge I think this is the best related issue to this: #24 (comment)

if you want to add a respec issue link, you can do so like this:

   <p class="issue" data-number="24">
     Contributors are discussing how best to categorize 
     process or event credentials vs product or organization credentials
    </p>

@OR13
Copy link
Collaborator

OR13 commented May 18, 2021

6 days open, multiple approvals, merging

@OR13 OR13 merged commit 627f403 into w3c-ccg:main May 18, 2021
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

Successfully merging this pull request may close these issues.

4 participants