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

Define more examples for use of naming #174

Open
getorymckeag opened this issue Oct 7, 2024 · 1 comment
Open

Define more examples for use of naming #174

getorymckeag opened this issue Oct 7, 2024 · 1 comment
Labels
Task catch-all for tasks not associated with spec changes

Comments

@getorymckeag
Copy link
Contributor

getorymckeag commented Oct 7, 2024

Use of CIM-style name types and authorities has some ambiguity.

An excerpt from conversation on #173:

Perhaps TROLIE should encourage but not require authority to follow the urn or Java package naming convention, too, in order to preempt questions about naming collisions.

We should also consider defining some problem responses in the spec for any situations where we can identify unambiguously when a proposal's naming is unacceptable. I don't think the spec can be silent on those situations. For example, if the TROLIE server recognizes the sender of a proposal as a particular authority, then it might treat any alternate-identifiers in that proposal not associated with that authority as informational. Or maybe this is all just "debug" info that may or may not be stored in anyway...

Add some further clarifying examples and recommendations.

@getorymckeag getorymckeag added the Task catch-all for tasks not associated with spec changes label Oct 7, 2024
@catkins-miso
Copy link
Contributor

Breadcrumb #173 (comment)

We specifically want an example of using ICCP points as alternate identifiers.

@catkins-miso catkins-miso added this to the Conformance Suite milestone Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Task catch-all for tasks not associated with spec changes
Projects
None yet
Development

No branches or pull requests

2 participants