-
Notifications
You must be signed in to change notification settings - Fork 0
Home
The role of the Network Library Toolkit user experience is to create Reference Contracts. These Reference Contracts provide the building blocks to describe data and provide guarantees on data interoperability.
There are a limited number of Reference Contract types:
Datatypes Compute Packaging Visualisation Modulues (units not active)
There are three basic parts to a reference contract: Concept Space Computational
Concept is short of conceptual, think of this being as the ontological structured way of describing knowledge in natural language
Space The coordinates of matter e.g. the structure of a water molecule or building etc.
Computational a computer program that manipulates data
Each datatype is given a name, description and a wikipedia and RDF URI link Options are give for what type of data this is likely to be along with units of measurement
A name, description and a link to a github repository along with the hash of the entry provided by the commit
Describes the datastore or API source data structure. In simplest terms the mapping of datatype name in network library are matched to the columns names holding the data. Where column include coding e.g for categorization a section is available to describe this features of the data. Also if any column has tidy up rules, these can be described in the packaging contract
The name of the visualisation library being used e.g. a charting library. Information is asked on how the data need to be structured for the library to work
Modules are intermediary or connecting reference contracts that provide a way to bundle together any combination of the above basic reference contracts. See creating Network Experiment using modules example (coming soon)