Document restructure

Issue #1365 resolved
Mark Haine created an issue

Suggestion from Dima and others that the current draft of OIDC4IDA is a difficult read for some implementers and that breaking it into 2 or more parts would be beneficial.

There is also a specific ask from implementers in the VC domain that the verification element and underlying schema would be very useful outside an OpenID connect implementation and so a separate document covering the structure and content of that element would be much easier to reference.

Comments (10)

  1. Mark Haine reporter

    I wonder if we should break this into discrete tasks so that we can diuscuss the merits of each and attend tom them independently perhaps:

    1. Split out Section 11 “Transaction-Specific Purpose” into separate draft
    2. Split out 5.1.2 “Attachments” into separate draft
    3. Split out 5. “Representing Verified Claims” structure and semantics into separate draft (although without “verified_claims delivery”

  2. Mark Haine reporter

    Expanding on this to propose the following documents are split out from openid-connect-4-identity-assurance.md:

    1. “Additional Claims” - Currently section 4.1
    2. “verified_claims” schema definition - Currently section 5 (except for 5.1.2 and 5.3)
    3. “Attachments” - Currently section 5.1.2
    4. “txn” claim - Currently section 4.2
    5. “Transaction Specific Purpose” - Currently section 11

    There may be more that could be separated but I can’t see further obvious candidates at this point.

    Propose separate PR fro each document split out from existing openid-connect-4-identity-assurance.md

    PR #165 is created for “Additional Claims” separation

    Key actions identified for separating sections of the document are

    1. Creating separate document with all appropriate headers, footers etc
    2. Creating new reference in remaining IDA spec to new document
    3. Add new document to pipeline

  3. Mark Haine reporter

    proposal to move to final with:

    then move forward with final for:

  4. Kosuke Koiwai

    I used this picture to explain to Japanese works (OIDF-J KYC WG) about this restructure. This change was generally well-received. There were also comments that it would make it easier to use for enterprise (i.e. Authority) purposes.

  5. Log in to comment