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
It seems like a lot of the config options have disappeared. I was looking for the SBOL3 equivalent of sbol2.Config.setOption(sbol2.ConfigOptions.SBOL_TYPED_URIS, False) which doesn't seem to exist. However, it seems like it is set somewhere as in object.py line 170 the property is checked.
The text was updated successfully, but these errors were encountered:
It seems like a lot of the config options have disappeared.
They didn't really disappear, they never existed. These config options did not get carried forward from pySBOL2 because most or all of them are unnecessary in pySBOL3.
I was looking for the SBOL3 equivalent of sbol2.Config.setOption(sbol2.ConfigOptions.SBOL_TYPED_URIS, False) which doesn't seem to exist.
All URIs are typed URIs in SBOL 3. See Section 5 of the SBOL 3 specification for more information. While non-typed URIs are allowed, they are discouraged by the specification. pySBOL3 makes it very difficult to use anything but typed URIs.
However, it seems like it is set somewhere as in object.py line 170 the property is checked.
This is true. It is also true that this code is broken and is not used. You missed the comment block and the NotImplementedError at the beginning of the function in which you found the erroneous SBOL_TYPED_URIS check. You probably also noticed that SBOL_TYPED_URIS does not appear anywhere else in the code. Issue #132 (referenced in the comment block I linked) documents the problems with this function, and what needs to be done with it.
It seems like a lot of the config options have disappeared. I was looking for the SBOL3 equivalent of sbol2.Config.setOption(sbol2.ConfigOptions.SBOL_TYPED_URIS, False) which doesn't seem to exist. However, it seems like it is set somewhere as in object.py line 170 the property is checked.
The text was updated successfully, but these errors were encountered: