Meeting Date
- The ToIP Trust Registry Task Force (TRTF) meets weekly twice every Thursday at the following times (to cover global time zones - see the Calendar of ToIP Meetings for full meeting info including Zoom links):
- NA/EU 07:00-8:00 PT / 15:00-16:00 UTC
- APAC 18:00-19:00 PT / 02:00-03:00 UTC
Zoom Meeting Link / Recording
- NA/EU MEETING: https://zoom.us/rec/share/Qy31TyCEp4FqpxNSkhTxpblNVac2u-kSa-BxZHHJZseEHLiXhm7mT9CvLw-4WHSH.J990nM-QOhHeLgIk
- APAC MEETING: https://zoom.us/rec/share/xVNJbyYpyT9oWAIXAd_e3HQxli5PB-yXiCx5s8tj81zNsCNBkgbWvbp5kj5j0gGX.AvwSTSns5aF2EpXZ
(These links will be replaced with a link to the recording of the meeting as soon as that is available)
Attendees
NA/EU Meeting
APAC Meeting
Agenda Items and Notes (including all relevant links)
| Time | Agenda Item | Lead | Notes |
| 5 min |
| Chairs |
|
| 5 min | Review of previous action items | Chairs | |
| 30 mins | Special topic #1 | ||
| 10 mins | Special topic #2 | ||
| 10 mins | Special topic #3 | ||
| 5 mins |
| Chairs |
Screenshots/Diagrams (numbered for reference in notes above)
#1
### DID Document
```sh
"serviceEndpoint": [
{
"profile": "https://trustoverip.org/profiles/trp/v2",
"uri": "https://my-tr-service/"
}
]
```
### Profile
```sh
{
"@context": ["https://trustoverip.org/contexts/v2/profile"],
"id": "trp-v2-profile",
"response_schema": "swagger",
"body": {
swagger doc
}
}
```
### TRP
```
https service
```
### Architecture
```mermaid
graph TD
DIDDocument --> Profile -->|Describes| ServiceInteraction[Service Interaction]
```
from our pre-meeting [somewhat related] discussion... this is the recent document that does a good job summarizing Digital Identity Standards from ENISA (not ETSI): https://www.enisa.europa.eu/publications/digital-identity-standards/@@download/fullReport
https://www.aamva.org/identity/mobile-driver-license-digital-trust-service
### Differences between Service Endpoint Type Vs. Profile
* Differences in scope.
* Profiles are more specific about what `implementation` of service endpoint is available whereas `type` field is more of a `class` of service endpoints.
```mermaid
graph TD
subgraph TrustRegistryType
Profile1[TRP]
Profile2[TEDocument]
end
```
* Namespacing issue
```sh
"serviceEndpoint": [
{
"type": "Trust Registry",
"profile": "https://trustoverip.org/profiles/trp/v2",
"uri": "https://my-tr-service/"
}
]
```
```sh
"serviceEndpoint": [
{
"type": "Trust Registry",
"profile": "https://eutrustlist.com/protocols/v2",
"url": "https://"
}
]
```
### Service Endpoint Struct
* It MUST be either an array or a single struct:
* It MUST be a struct with the following properties:
* If adding a Profile definition, service endpoint array MUST have the following properties:
* An HTTPS resolvable JSON Profile document. See profile document section for more details.
* It MUST have a URI, which descibes the endpoint address of the interaction.
An Example is seen below:
```sh
{
"@context":[
"https://www.w3.org/ns/did/v1",
"https://trustoverip.org/profile/v2"
],
...
"service": [{
"id":"did:example:123#trust-registry",
"type": "TrustRegistry",
"serviceEndpoint": {
"profile": "https://trustoverip.org/profiles/trp/v2",
"uri": "https://my-tr-service/"
}
}]
}
```
## Profile Definitions
* 2 goals
* Description: string match.
* Normatively describe interaction
```
{
"metadata": {
},
""
}
```
Cosanna : Pan Canadian TR might be able to help.
## Non-normative chaining and container problem
* Trust on First Use
Decisions
- Sample Decision Item
Action Items
- Sample Action Item