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

compound identifiers for resources? #54

Closed
caindy opened this issue Feb 23, 2024 · 0 comments · Fixed by #71
Closed

compound identifiers for resources? #54

caindy opened this issue Feb 23, 2024 · 0 comments · Fixed by #71
Labels
documentation Improvements or additions to documentation enhancement New feature or request question Further information is requested

Comments

@caindy
Copy link

caindy commented Feb 23, 2024

Related to #9 and #6, we had the following question in the webinar (paraphrased):

Branches in our system model are nominated by a "From Bus" and a
"To Bus"; they are not assigned a (synthetic) unique identifier. How will we
be used the "resource-id" field to identify a branch when branches are not
assigned a single identifier?

Initial thoughts:

  • We could recommend an approach that uses an internal identifier a la RDF along with "from" and "to" alternate names.
  • Consider simply using "{fromBus} {toBus}" as the primary identifier in this case.
  • It's possible to have two (rarely three) circuits between the same two busses, in which case they are ostensibly assigned circuit ids.
  • Having a way to designate the from bus and to bus could be generally useful in some debugging and support scenarios.
@caindy caindy changed the title compound identifiers for resources compound identifiers for resources? Feb 23, 2024
@caindy caindy added documentation Improvements or additions to documentation enhancement New feature or request question Further information is requested labels Feb 23, 2024
@caindy caindy pinned this issue Mar 7, 2024
@caindy caindy linked a pull request Mar 14, 2024 that will close this issue
@catkins-miso catkins-miso unpinned this issue Mar 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants