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.

Sign up for GitHub

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

Jump to bottom

How to handle URI enums? #8

Open

jakebeal opened this issue Jun 15, 2021 · 1 comment

Milestone

Contributor

jakebeal commented Jun 15, 2021

SBOL uses URI enums in a number of places, e.g., in the draft SBOL3 OWL RDF:

<owl:Class rdf:about="#Orientation">
  <rdfs:subClassOf rdf:resource="#SBOLTerm"/>
  <owl:equivalentClass>
    <owl:Class>
      <owl:unionOf rdf:parseType="Collection">
        <rdf:Description rdf:about="#inline"/>
        <rdf:Description rdf:about="#reverseComplement"/>
      </owl:unionOf>
    </owl:Class>
  </owl:equivalentClass>
</owl:Class>

How should SBOL factory handle enum declarations like this?

The text was updated successfully, but these errors were encountered:

Contributor Author

jakebeal commented Sep 1, 2021 •

edited

Loading

Plan: can we handle this by turning these into available constants?
e.g., equivalent of sbol3.SBOL_INLINE

jakebeal mentioned this issue

Declaration of constants? #14

Open

jakebeal added this to the Future Tasks milestone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment