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
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.
The text was updated successfully, but these errors were encountered:
Use of CIM-style name types and authorities has some ambiguity.
An excerpt from conversation on #173:
Add some further clarifying examples and recommendations.
The text was updated successfully, but these errors were encountered: