Entity Statement - Revision history

Tom: /* Solutions */

2024-01-12T00:39:54Z

‎Solutions

2021-05-25T01:08:38Z

‎Solutions

2021-05-25T01:04:29Z

‎Solutions

2021-05-25T00:58:10Z

‎Solutions

2021-05-25T00:57:19Z

‎Solutions

2019-10-16T18:04:57Z

‎HL7 FHIR Capability Statement

2019-10-16T18:03:24Z

‎Solutions

2019-10-16T17:57:38Z

‎Problems

2019-10-11T20:48:13Z

‎Solutions

2019-10-11T20:46:31Z

‎Solutions

@@ Line 54: / Line 54: @@
 |policy ||instantiates || || || uri of detailed description (level confusion)
 |-
-| sub_is_leaf|| || || ||is the subject considered a leaf entity
+| sub_is_leaf|| || || ||is the subject considered a leaf entity or [[Leaf Node]]
 |-
 | organization_name|| implementation ||Legal entity || || incl contact, uri. not very exact correspondence (level confusion)

@@ Line 65: / Line 65: @@
 |-
 | federation||s/w app  ||PKI || self ID||context
 |-
 |aud || || || || audience = the entity that is specifically targeted by this statement.
 |}

@@ Line 45: / Line 45: @@
 |-
 | metadata_policy|| || || ||type followed by organization information
 |-
 | metadata type|| kind of app || || ||overall purpose of this type of installation

@@ Line 62: / Line 62: @@
 | federation||s/w app  ||PKI || self ID||context
 |-
-|aud || || || audience = The entity identifier for the entity that is specifically targeted by this statement.
+|aud || || || || audience = the entity that is specifically targeted by this statement.
 |}

@@ Line 61: / Line 61: @@
 |-
 | federation||s/w app  ||PKI || self ID||context
 |}

@@ Line 64: / Line 64: @@
 ===HL7 FHIR Capability Statement===
-The FHIR spec include a definition of a [https://hl7.org/fhir/R4/capabilitystatement.html Resource Capability Statement]. Which is similar in purpose to the [[Entity Statement]] but includes FHIR specific fields. To quote the spec "A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.".
+The FHIR spec includes a definition of a [https://hl7.org/fhir/R4/capabilitystatement.html Resource Capability Statement]. Which is similar in purpose to the [[Entity Statement]] but includes FHIR specific fields. To quote the spec "A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.".
 ==References==

@@ Line 13: / Line 13: @@
 {|border="1" padding="2" width="999px"
 | Entity Statement ||HL7 capability|| X.509 certificate||DID Document || Notes
 |-
 | n/a || persistent URI|| ver 3, Serial No.||@context || Document ID - may include status & url to this or current version of doc

← Older revision		Revision as of 17:57, 16 October 2019
Line 6:		Line 6:

	==Problems==		==Problems==
		+	There have been several attempts to get information from web sites to users. These have diverged in unexpected ways based on the approach taken.

	==Solutions==		==Solutions==

@@ Line 14: / Line 14: @@
 |-
 | n/a || persistent URI|| ver 3, Serial No.||@context || Document ID - may include status & url to this or current version of doc
 |-
 | n/a ||s/w app name || || ||may include status & a human readable description of function
@@ Line 39: / Line 37: @@
 | jwks || ||public key || publicKeyPem || public part of the subject entity's signing keys
 |-
-| authority_hints|| ||chain ||blockchain ||entities that may issue an entity statement about the issuer entity
+| authority_hints|| imports||chain ||blockchain ||entities that may issue an entity statement about the issuer entity
 |-
 | metadata || || || || protocol specific metadata claims