Clone

HTTPS: git clone https://vervis.peers.community/repos/yEzqv

SSH: git clone USERNAME@vervis.peers.community:yEzqv

Branches

Human readable
Human writable easily as plain text
Allows to define objects, classes and properties in a graph/tree structure
Allows convenient syntax for task lists
Allows for extensions to define new syntax for new special definitions (in a similar manner to task lists)

Modular, i.e. core definitions are defined step by step on top of each other
Pluggable, i.e. common interfaces allow entities to be switched to minimize dependencies
Minimal, i.e. definition groups are simple and small, concerned with one specific domain

Allow to define requirements on data easily, and take good ideas from OWL
Support property properties: symmetric, inverseOf, asymmetric, reflexive, transitive, function, surjection, injection

Versioning: Ontologies/graphs can specify forward and backward compatibility, containment and version numbers
Equivalence: It is possible to say that different elements refer to the same entity
Cooperation: There should be continuous effort to merge similar work and create unified common definitions
Branching/Forking: It should be possible to easily extend an ontology by hand and base object definitions on it
Merging: It should be possible and easy to automatically merge work and use forked ontologies simultaneously
Sharing: It should be easy to share ontologies to allow easy community reuse, and easy to search and find ontologies
Decentralization: The community processes should be decentralized, not rely on any central service or authority
Distribution: The data should be distributed on many systems, including countless copying, thus creating strong backup and allowing machines to share data and make queries as if in one huge database