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.

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

Open Issue 21: home community ID #103

Open
lukeaduncan opened this issue May 2, 2022 · 0 comments
Open

Open Issue 21: home community ID #103

lukeaduncan opened this issue May 2, 2022 · 0 comments
Labels
open issue Open Issue mentioned in Implementation Guide

Comments

@lukeaduncan
Copy link
Contributor

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.

  • 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.

@lukeaduncan lukeaduncan added the open issue Open Issue mentioned in Implementation Guide label May 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
open issue Open Issue mentioned in Implementation Guide
Projects
None yet
Development

No branches or pull requests

1 participant