Blueprint EBWOID issuance

blueprint/04-integration-model.md

@@ -75,6 +75,76 @@ Wallet-->>Wallet: Validates the credential
 Wallet-->>Wallet: Stores the credential
 User->>Wallet: Accesses the credential
 ```
+### EBWOID issuing process
+The EBW Owner Identification Data (EBWOID) is the primary identifier and credential for economic operators and is required to operate an EBW. It is issued by the responsible authentic source and stored in the EBW of the economic operator. Once the EBWOID is available, the economic operator can participate in the EBW ecosystem and store additional attestations. The EBWOID therefore serves as the foundational credential for the EBW. 
+
+The key verification steps in its issuance must be carried out in accordance with legal requirements and consistently across the ecosystem. Further details are provided in the [EBWOID Rulebook](https://github.com/webuild-consortium/webuild-attestation-rulebooks-catalog/blob/main/rulebooks/ds001-ebw-oid-rulebook.md).
+
+The sequence diagram below shows the minimum issuance flow for an EBWOID credential. It focuses on the common steps shared across use cases. Optional activities and alternative flows may be included in extended versions of the diagram.
+
+``` mermaid
+sequenceDiagram
+  autonumber
+  actor Rep as Representative
+  participant Issuer as EBWOID Issuer
+  participant AS as Authentic Source
+  participant IW as Issuer Business Wallet /Component
+  participant HW as Holder Business Wallet
+  %%participant Reg as Revocation Directory
+
+  rect rgb(245,245,245)
+    Note left of Rep: Initiate request
+    Rep->>Issuer: Visit eService of EBWOID issuer
+    %% either through an eservice or initiated from the wallet
+    Rep->>Issuer: Provide user credentials (LoA Substantial)
+    Issuer-->>Issuer: Verify user credentials
+    Rep->>Issuer: Initiate EBWOID request
+    Rep->>Issuer: Provide economic operator identifier
+    %%user can either provide, select or choose the identifier
+    Issuer->>Rep: discover wallet endpoint
+    %%EBW. could be previously registered. issuer needs to understand where to send the credential offer
+  end
+
+  rect rgb(235,245,255)
+    Note left of Issuer: Verify eligibility
+      Issuer->>AS: Request economic operator information
+      AS-->>Issuer: Provide economic operator information
+      Issuer->>Issuer: Verify economic operator status
+      Issuer->>AS: Request user powers
+      AS-->>Issuer: Provide user powers information
+      Issuer->>Issuer: Verify user powers
+      %%Assumption the user has representation or signatory rights to request EBWOID issuance according to national regulation
+      %%The issuer may need a signature as part of the eligibility process
+  end
+
+  rect rgb(235,245,255)
+    Note left of Issuer: Issue EBWOID attestation
+    Issuer->>AS: Request EBWOID information
+    AS-->>Issuer: Provide EBWOID information
+    Issuer->>IW: Request EBWOID issuance
+    IW->>IW: Construct EBWOID
+
+    rect rgb(255,245,255)
+%%Verify that the wallet is operational to receive the EBWOID credential
+
+    Note left of Issuer: Verify Wallet
+    IW->>HW: Request proof of state operational
+    HW-->>IW: Provide proof
+    IW->>IW: Verify wallet status
+end
+    IW->>HW: Issue EBWOID
+    HW->>HW: Store EBWOID
+    %%Business 
+    IW-->>Issuer: Notify of issuance
+
+    rect rgb(245,345,355)
+    Note left of Issuer: Publish revocation information for longlived EBWOID
+    Issuer->>Issuer: Publish revocation information
+    %%Publish to Trust register
+end
+    Issuer-->>Rep: Notify representative (and economic operator)
+end
+```
 
 ## Interaction Pattern: Attestation Presentation (Receiving)