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 behavior when conflicting idspaces are specified #760

Open
cmungall opened this issue May 15, 2024 · 0 comments
Open

Define behavior when conflicting idspaces are specified #760

cmungall opened this issue May 15, 2024 · 0 comments

Comments

@cmungall
Copy link
Collaborator

cmungall commented May 15, 2024

There are different potential sources of conflict or ambiguity:

  1. Contraction
      1. when an alternate prefix is specified for a builtin idspace
      1. when alternate prefixes are specified for domain idpsaces
  2. Expansion
      1. When a builtin idspace is overridden
      1. When alternate expansions are provided for domain idspaces

Originally posted by @hrshdhgd in #702 (comment)

cmungall added a commit that referenced this issue May 15, 2024
Adds test that currently codifies ambiguous behavior.

See also #760 for broader issue.

This PR also extends the obo test suite to include this,
and adds some derived files previously missing.
cmungall added a commit that referenced this issue Jun 5, 2024
* Making prefix mapping less strict, fixes #702

Adds test that currently codifies ambiguous behavior.

See also #760 for broader issue.

This PR also extends the obo test suite to include this,
and adds some derived files previously missing.

* format

* add missing

* add missing

* fix GCI example

* fixed docs

* regenrate compliance test outputs

* Ensure prefixmap is not mutated

* relax test

* fmt
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant