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
Ideas for a New Layer which is more abstract than Layer 2.
This will likely be dictated by the terms used as this is not going to fully or partially follow the SBOL data model like the previous two layers.
However, I think that it would be useful to find potential methods that will further abstract via the language therefore some ideas that have been thrown around in the past:
Implicit Template Creation but exposing the name
Basically what we have now but expose the name of implicitly created templates,
or allow the user to define the name.
Implicit creation of the ComponentDefinition
Instead of Instances being implicitly created implicitly create the ComponentDefinition.
This does add a problem that potential hierarchy is lost with this.
Introduce more complex logic
This is because we are relying on tricks of the Language to make these abstractions,
The whole current implicit creation is an example of this.
Instead, we could analyze the graph and by making assumptions.
Likely in the form of an extension.
(Move logic to language, not library)
Not anything that is imminent just ideas.
Likely a better set of terms/ relationships than SBOL and a mapping between these and SBOL terms will need to be defined before this.
The text was updated successfully, but these errors were encountered:
Ideas for a New Layer which is more abstract than Layer 2.
This will likely be dictated by the terms used as this is not going to fully or partially follow the SBOL data model like the previous two layers.
However, I think that it would be useful to find potential methods that will further abstract via the language therefore some ideas that have been thrown around in the past:
Implicit Template Creation but exposing the name
Basically what we have now but expose the name of implicitly created templates,
or allow the user to define the name.
Implicit creation of the ComponentDefinition
Instead of Instances being implicitly created implicitly create the ComponentDefinition.
This does add a problem that potential hierarchy is lost with this.
Introduce more complex logic
This is because we are relying on tricks of the Language to make these abstractions,
The whole current implicit creation is an example of this.
Instead, we could analyze the graph and by making assumptions.
Likely in the form of an extension.
(Move logic to language, not library)
Not anything that is imminent just ideas.
Likely a better set of terms/ relationships than SBOL and a mapping between these and SBOL terms will need to be defined before this.
The text was updated successfully, but these errors were encountered: