Draft overview of Fields and Schemas

Includes #7

explain how schemas are composed from fields
give some examples

Here's some text which can be the basis of the documentation:

A schema is a group of data points (fields) that together provide information that is useful to aggregators who present that data in meaningful ways.

Fields

A field can contain a single item of data, such as an organization's name:

"legalName": "Greenfarm Co-op"

a date of creation:

"foundingDate": "2010-09-10"

or a number of staff members.

"numberOfEmployees": 88

Alternatively a field could hold more complex structures such as a list of items:

"itemListElement": [
    "carrots",
    "lettuce",
    "apples",
    "cherries",
    "broccoli"
  ]

or an object composed of many different fields.

"address": {
  "streetAddress": "123 Country Lane",
  "addressLocality": "Pleasantville",
  "addressRegion": "Comfortshire",
  "addressCountry": "Loveland"
}

Every field needs to have context, that is, some definition that provides a clear meaning for the data it holds. The Murmurations Protocol leverages widely accepted field definitions whenever possible, using established vocabularies.

{
  "@context": {
      "legalName": "http://schema.org/legalName",
      "foundingDate": "https://schema.org/foundingDate",
      "numberOfEmployees": "https://schema.org/numberOfEmployees"
  }
}

However if suitable definitions do not exist to describe fields correctly, it is possible to create new vocabularies and use them, provided there is a URL where it is described.

MurmurationsNetwork / MurmurationsProtocol

Draft overview of Fields and Schemas #8

Fields