You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does HCID need to be specified to ensure interoperability?
Should HCID be be mandated on the Endpoint, the Organization, or both?
Should federated communities behind an Endpoint be reflected in its identifier list?
Should identifier of an Endpoint be empty?
We have seen directories add a custom code "HCID" that shows that an identifier is a HCID,
and have seen them use the system of "urn:ietf:rfc:3986" and a URN-encoded OID.
In committee discussions, we walked this through, and the general consensus was that
for identifying an organization to meet the MHD to a Federation use cases (i.e. to
determine connectivity), whether or not an identifier happened to be a HCID
was not significant. If we were to get into more detail about addressing federated recipients
(see issue 15 in this list), we might need to make decisions like whether HCID must be
a specific identifier type and whether it should be URN-encoded.
The text was updated successfully, but these errors were encountered:
This profile says very little about home community ID, yet it is called out
in mCSD issue #2.
Section 1:46.8.2 talks about
"identifiers of type Home Community ID". The profile on Endpoint for Document Sharing says to put the HCID in the Endpoint.identifier. The
Example of an mCSD XCA Query Endpoint shows
an Endpoint.identifier.type with coding for a HCID. But this is not specified
normatively anywhere.
We have seen directories add a custom code "HCID" that shows that an identifier is a HCID,
and have seen them use the system of "urn:ietf:rfc:3986" and a URN-encoded OID.
In committee discussions, we walked this through, and the general consensus was that
for identifying an organization to meet the MHD to a Federation use cases (i.e. to
determine connectivity), whether or not an identifier happened to be a HCID
was not significant. If we were to get into more detail about addressing federated recipients
(see issue 15 in this list), we might need to make decisions like whether HCID must be
a specific identifier type and whether it should be URN-encoded.
The text was updated successfully, but these errors were encountered: