EPIC: Collections

[blake-regalia]

To allow for the query of the union of multiple graphs at specific versions
A collection can reference other repos' branch or lock, and the collection query would query against the union of those graphs

[stevevestal]

Most workflows we see use multiple documents/ontologies. A collection of multiple repos with one document/ontology, or a repo with multiple documents/ontologies, either could group related ones. Either way, serialized or transactional commits on collections of documents/ontologies would be useful for configuration management, but locks on commits of single models could be sufficient. Workflows in big projects use documents/ontologies from multiple servers owned by multiple organizations, so there is still global configuration management to be done. The best thing I know of to help manage configurations globally is for developers to use the standards for namespace/ontology IRIs and version IRIs together with locks on commits. RDF graphs are not required to contain those, but most documents/ontologies have them. Something else that might be useful is to tag (in the git sense) a commit that is locked by the owning organization (read-only access to others) as a deliverable version.