Writing up the OPIL spec, I notice that our properties have shifted from the camelCase pattern used by SBOL to the snake_case pattern used by Python. This means that documents will have a mix of snake case and camel case.
This feels inelegant, but not necessarily bad.
Example of the issue:
An ExperimentRequest uses sample_set to link to its SampleSet member. That SampleSet, being a subclass of CombinatorialDerivation, uses hasVariableFeature to link to its variables.
We should either:
Change from snake_case to camelCase (but make sure the python mappings remain pythonic)
Explicitly document and justify the disagreement of styles.
Following discussion, we're going to switch from snake_case to camelCase for the representation, but keep snake_case in the python API, just as with SBOL.
Writing up the OPIL spec, I notice that our properties have shifted from the camelCase pattern used by SBOL to the snake_case pattern used by Python. This means that documents will have a mix of snake case and camel case.
This feels inelegant, but not necessarily bad.
Example of the issue:
An
ExperimentRequest
usessample_set
to link to itsSampleSet
member. ThatSampleSet
, being a subclass ofCombinatorialDerivation
, useshasVariableFeature
to link to its variables.We should either: