In SBOL, we have always made a set of strong logical closure assumptions based around the notion of object completeness. Now that SBOL 3 is based in RDF, rather than a fixed document structure, we need to make these assumptions explicit, since otherwise (a) it is legal to arbitrarily split up the properties of an SBOL object, and (b) we lose the ability to make strong validation rules.
Implicit in this is a clear set of rules for the fragmentation and composition of documents and the circumstances under which version control decisions are necessary.
In SBOL, we have always made a set of strong logical closure assumptions based around the notion of object completeness. Now that SBOL 3 is based in RDF, rather than a fixed document structure, we need to make these assumptions explicit, since otherwise (a) it is legal to arbitrarily split up the properties of an SBOL object, and (b) we lose the ability to make strong validation rules.
Implicit in this is a clear set of rules for the fragmentation and composition of documents and the circumstances under which version control decisions are necessary.
This also resolves https://github.com/SD2E/opil/issues/146