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
Some users of pySBOL3 may not want their data/information shared online via the use of online validation or conversion utilities. Consider how to protect users by default. Should online validation/conversion be off by default and require that users explicitly enable it? This could have the side benefit of allowing the library to run in disconnected environments.
But how will users know to enable online validation? And how do we make enabling online validation easy?
This will also require documentation to explain when and how online tools are used by the library so that users can control those uses.
The text was updated successfully, but these errors were encountered:
pySBOL2 now supports offline conversion, and it conversion is run via SBOL-utilities, it is now offline by default. Do we need to do anything else in order to resolve this?
Some users of pySBOL3 may not want their data/information shared online via the use of online validation or conversion utilities. Consider how to protect users by default. Should online validation/conversion be off by default and require that users explicitly enable it? This could have the side benefit of allowing the library to run in disconnected environments.
But how will users know to enable online validation? And how do we make enabling online validation easy?
This will also require documentation to explain when and how online tools are used by the library so that users can control those uses.
The text was updated successfully, but these errors were encountered: