Commit 09eaca14 authored by uschwar1's avatar uschwar1
Browse files

change order of diagrams

parent 3b3f78be
......@@ -3,6 +3,93 @@
These are diagrams that show the main foreground and background activities in
a PID architecture
## The PID consumer's view of the global PID architecture
PID Registration and Resolution in the Global PID Architecture is shown in the following diagram
```plantuml
'actor User as User
'agent Repository as Repo
agent "PID consumer" as PIDconsumer
agent "global PID Architecture" as PIDarch
'database "PID Service" as PIDserv
'rectangle "Local PID Provider" as PIDprov
'User o--> Repo : "registers Data"
'User <--* Repo : "issues credential"
'User --> Repo : "accesses Data"
PIDconsumer --> PIDarch : "queries PID"
PIDarch ..> PIDconsumer : "resolves PID"
'Repo --> Repo : "manages Data"
PIDconsumer o--> PIDarch : "registers PID"
PIDarch <--o PIDconsumer : "accesses Prefix"
PIDarch *..> PIDconsumer : "issues credential"
'PIDarch ..> PIDarch : "resolves Prefix namespace"
'PIDarch *....> PIDarch : "retrieves allocated Prefix"
'PIDarch <....* PIDarch : "provides PID service info"
'PIDarch <..o PIDarch : "implements and runs PID service"
PIDconsumer *--> PIDarch : "requests Prefix"
```
## Unfolding the PID consumer into User and Repository
The user's and repository's view of the global PID architecture is given in the following diagram
```plantuml
actor User as User
agent Repository as Repo
agent "global PID Architecture" as PIDarch
'database "PID Service" as PIDserv
'rectangle "Local PID Provider" as PIDprov
User o--> Repo : "registers Data"
User <--* Repo : "issues credential"
User --> Repo : "accesses Data"
User --> PIDarch : "queries PID"
'Repo --> Repo : "manages Data"
Repo o--> PIDarch : "registers/modifies PID"
PIDarch ..> User : "resolves PID"
PIDarch <--o Repo : "accesses Prefix"
PIDarch *..> Repo : "issues credential"
'PIDarch ..> PIDarch : "resolves Prefix namespace"
'PIDarch *....> PIDarch : "retrieves allocated Prefix"
'PIDarch <....* PIDarch : "provides PID service info"
'PIDarch <..o PIDarch : "implements and runs PID service"
Repo *--> PIDarch : "requests Prefix"
```
## Global PID Registration and Resolution
An abstraction of the global PID Registration and Resolution is given in the following diagram
```plantuml
actor User as User
agent Repository as Repo
agent "global PID Registration and Resolution" as PIDreg
database "PID Service" as PIDserv
rectangle "Local PID Provider" as PIDprov
User o--> Repo : "registers Data"
User <--* Repo : "issues credential"
User --> Repo : "accesses Data"
User --> PIDreg : "queries PID"
'Repo --> Repo : "manages Data"
Repo o--> PIDserv : "registers/modifies PID"
PIDserv ..> User : "resolves PID"
PIDserv <--o Repo : "accesses Prefix"
PIDserv *..> Repo : "issues credential"
PIDreg ..> PIDserv : "resolves Prefix namespace"
PIDreg *....> PIDprov : "retrieves allocated Prefix"
PIDreg <....* PIDprov : "provides PID service info"
PIDserv <..o PIDprov : "implements and runs PID service"
Repo *--> PIDreg : "requests Prefix"
```
## Overview
The complete description of all internal relations is given in the following diagram:
......@@ -96,88 +183,3 @@ Repo *--> SRA : "requests Prefix"
'Repo ..> ProfR : "looks up Profile"
'PIDserv ..> ProfR : "complies to Profile"
```
## Global PID Registration and Resolution
An abstraction of the global PID Registration and Resolution is given in the following diagram
```plantuml
actor User as User
agent Repository as Repo
agent "global PID Registration and Resolution" as PIDreg
database "PID Service" as PIDserv
rectangle "Local PID Provider" as PIDprov
User o--> Repo : "registers Data"
User <--* Repo : "issues credential"
User --> Repo : "accesses Data"
User --> PIDreg : "queries PID"
'Repo --> Repo : "manages Data"
Repo o--> PIDserv : "registers/modifies PID"
PIDserv ..> User : "resolves PID"
PIDserv <--o Repo : "accesses Prefix"
PIDserv *..> Repo : "issues credential"
PIDreg ..> PIDserv : "resolves Prefix namespace"
PIDreg *....> PIDprov : "retrieves allocated Prefix"
PIDreg <....* PIDprov : "provides PID service info"
PIDserv <..o PIDprov : "implements and runs PID service"
Repo *--> PIDreg : "requests Prefix"
```
## Abstraction of the Global PID Architecture
The user's and repository's view of the global PID architecture is given in the following diagram
```plantuml
actor User as User
agent Repository as Repo
agent "global PID Architecture" as PIDarch
'database "PID Service" as PIDserv
'rectangle "Local PID Provider" as PIDprov
User o--> Repo : "registers Data"
User <--* Repo : "issues credential"
User --> Repo : "accesses Data"
User --> PIDarch : "queries PID"
'Repo --> Repo : "manages Data"
Repo o--> PIDarch : "registers/modifies PID"
PIDarch ..> User : "resolves PID"
PIDarch <--o Repo : "accesses Prefix"
PIDarch *..> Repo : "issues credential"
'PIDarch ..> PIDarch : "resolves Prefix namespace"
'PIDarch *....> PIDarch : "retrieves allocated Prefix"
'PIDarch <....* PIDarch : "provides PID service info"
'PIDarch <..o PIDarch : "implements and runs PID service"
Repo *--> PIDarch : "requests Prefix"
```
## The PID consumer's view of the global PID architecture
PID Registration and Resolution with the Global PID Architecture is given in the following diagram
```plantuml
'actor User as User
'agent Repository as Repo
agent "PID consumer" as PIDconsumer
agent "global PID Architecture" as PIDarch
'database "PID Service" as PIDserv
'rectangle "Local PID Provider" as PIDprov
'User o--> Repo : "registers Data"
'User <--* Repo : "issues credential"
'User --> Repo : "accesses Data"
PIDconsumer --> PIDarch : "queries PID"
PIDarch ..> PIDconsumer : "resolves PID"
'Repo --> Repo : "manages Data"
PIDconsumer o--> PIDarch : "registers PID"
PIDarch <--o PIDconsumer : "accesses Prefix"
PIDarch *..> PIDconsumer : "issues credential"
'PIDarch ..> PIDarch : "resolves Prefix namespace"
'PIDarch *....> PIDarch : "retrieves allocated Prefix"
'PIDarch <....* PIDarch : "provides PID service info"
'PIDarch <..o PIDarch : "implements and runs PID service"
PIDconsumer *--> PIDarch : "requests Prefix"
```
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment