Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Relying Party PE, media-type for EC and normative language section #76

Merged
merged 2 commits into from
Jul 24, 2023
Merged

Relying Party PE, media-type for EC and normative language section #76

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c3fd8e0
normative lang, media type for EC, RP PE typos
peppelinux Jul 23, 2023
20a9455
fix: typo
peppelinux Jul 23, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions docs/en/defined-terms.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,13 @@

.. _defined-terms.rst:


Normative Language and Conventions
++++++++++++++++++++++++++++++++++

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.


Defined Terms
+++++++++++++

Expand Down
11 changes: 3 additions & 8 deletions docs/en/relying-party-solution.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -340,10 +340,10 @@ Here a non-normative example of ``presentation_definition``:

{
"presentation_definition": {
"id": "pid-sd-jwt:unique_id+given_name+family_name",
"id": "presentation definitions",
"input_descriptors": [
{
"id": "eu.europa.ec.eudiw.pid.it.1",
"id": "pid-sd-jwt:unique_id+given_name+family_name",
"name": "Person Identification Data",
"purpose": "User authentication",
"format": "vc+sd-jwt",
Expand Down Expand Up @@ -409,14 +409,9 @@ Below is a non-normative example of the decrypted JSON ``response`` content:
"id": "04a98be3-7fb0-4cf5-af9a-31579c8b0e7d",
"descriptor_map": [
{
"id": "eu.europa.ec.eudiw.pid.it.1:unique_id",
"id": "pid-sd-jwt:unique_id+given_name+family_name",
"path": "$.vp_token.verified_claims.claims._sd[0]",
"format": "vc+sd-jwt"
},
{
"id": "eu.europa.ec.eudiw.pid.it.1:given_name",
"path": "$.vp_token.verified_claims.claims._sd[1]",
"format": "vc+sd-jwt"
}
]
}
Expand Down
5 changes: 4 additions & 1 deletion docs/en/trust.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -254,7 +254,10 @@ Below is a non-normative example of a Trust Anchor Entity Configuration, where e
Entity Configuration
--------------------

The Entity Configuration is the verifiable document that each Federation Entity must publish on its own behalf.
The Entity Configuration is the verifiable document that each Federation Entity must publish on its own behalf in the web path **.well-known/openid-federation**.

The Entity Configuration HTTP response MUST set the media type `application/entity-statement+jwt`.

The Entity Configuration must be cryptographically signed. The public part of this key must be present in the
Entity Configuration and within the Entity Statement issued by a immediate superior concerning the Federation Entity.

Expand Down
Loading