search

ietf-rats / ietf-corim-cddl

This repository is abandoned. The adopted I-D can be found at:
https://github.com/ietf-rats-wg/draft-ietf-rats-corim/
2 stars 0 forks source link

entity-entry should be its own namespace #12

Closed nedmsmith closed 3 years ago

nedmsmith commented 3 years ago

CoRIM, XcoRIM, CoMID, and CoSWID all depend on entity-entry.

The broad dependency suggests to me that entity-entry should be a stand-alone namespace.

It needs to have an extensible roles approach - for example allowing each client to register its roles names. But this could be done using "mynamespace." convention.

An entity should be able to become a w3C DID eventually.

nedmsmith commented 3 years ago

For now agree to have a new entity entry for corim and xcorim and another for comid (while keeping coswid). 3 entity-entries total (entity-entry, corim.entity-map, comid.entity-map).

yogeshbdeshpande commented 3 years ago

I am happy to take this item and work on it!

nedmsmith commented 3 years ago

Was this part of PR#17? In the TCG Endorsement spec, we're using namespace conventions (comid.xxx, coswid.xxx, corim.xxx) for code points of a -type-choice object. Did we decide those conventions would not follow into the CDDL?

yogeshbdeshpande commented 3 years ago

As informed, PR#17 will be re-worked to have individual roles. Issue #12 will address complete entity-entry including roles.