# Common Terms
🚧 Work In Progress 🚧
Here we define some of the common terms we use when working with Murmurations.
TODO - needs defining
The Murmurations Index keeps track of all the Nodes (via their Profiles) in the network. Whenever someone (or something) updates its Profile it tells the Index. Aggregators frequently query the Index to find Profiles using their Schemas along with changes to existing Profiles, enabling them to provide up to date information in their maps, directories and content aggregators.
The Murmurations Library (opens new window) stores a list of Murmurations Schemas and data fields. Anyone can define a new Schema, or data field, and create a pull request to have it added it to the Library.
# Murmurations Protocol:
The Murmurations Protocol, which we also just call Murmurations, is a standardised, open source set of rules designed to enable decentralised collaboration at scale. Murmurations uses existing standards including JSON Schema (opens new window), Schema.org (opens new window), RSS (opens new window) and JSON-LD (opens new window) to help people, projects and organisations discover each other and share data across platforms and between networks. The ultimate aim of Murmurations is to accelerate the global transition to the regenerative economy (opens new window).
A Node is an entity (person, project, organisation, event or smart object) that has a Profile which is registered in the Murmurations Index.
A Profile is a JSON (opens new window) document describing a Node (person, project, etc.), using one or more Schemas. Here's an example Murmurations Profile (opens new window) describing The Open Co-op, using the Murmurations Map schema (opens new window).
# Profile Generator:
The Murmurations Profile Generator (opens new window), or MPG for short, is a web application for creating Profiles. MPG automatically converts Schemas in the Library into forms to enable people to create the JSON documents for their Profiles. MPG can also host these JSON documents, which may seem an odd way to manage decentralised data, but is an important feature which makes the protocol accessible to people who can't host their own Profile files.
A schema is a JSON Schema (opens new window) file which defines a collection of data fields and explains how they should be used. Schemas validate JSON documents to check the data entered in a Profile matches the expected format. Schemas define the composition of fields, and fields define the type and validation rules for data. See the Murmurations Map Schema file (opens new window) as an example.