Support schema 4 4

[richardhallett]

Purpose

closes: #104

Approach

Adds xsd resources / updates version 4 Adds support for resourceType mapping Adds support for subject classification parsing. Add supports for relatedItems - this is a new sub array containing various parts.

So it's clear here is currently how the output of the JSON is looking for the new relatedItems

  "id": "https://doi.org/10.5072/example-full",
  "relatedItems": [
    {
      "relationType": "IsPublishedIn",
      "relatedItemType": "Journal",
      "relatedItemIdentifier": {
        "relatedItemIdentifier": "10.5072/john-smiths-1234",
        "relatedItemIdentifierType": "DOI",
        "relatedMetadataScheme": "citeproc+json",
        "schemeURI": "https://github.com/citation-style-language/schema/raw/master/csl-data.json",
        "schemeType": "URL"
      },
      "creators": [
        {
          "nameType": "Personal",
          "name": "Smith, John",
          "givenName": "John",
          "familyName": "Smith"
        }
      ],
      "titles": [
        {
          "title": "Understanding the fictional John Smith"
        },
        {
          "title": "A detailed look",
          "titleType": "Subtitle"
        }
      ],
      "volume": "776",
      "issue": "1",
      "number": "1",
      "firstPage": "50",
      "lastPage": "60",
      "publisher": "Example Inc",
      "publicationYear": "1776",
      "edition": "1",
      "contributors": [
        {
          "name": "Hallett, Richard",
          "givenName": "Richard",
          "familyName": "Hallett",
          "contributorType": "ProjectLeader"
        }
      ]
    }
  ],
}

Open Questions and Pre-Merge TODOs

Learning

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)

• [X] New feature (non-breaking change which adds functionality)

• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Reviewer, please remember our guidelines:

• Be humble in the language and feedback you give, ask don't tell.
• Consider using positive language as opposed to neutral when offering feedback. This is to avoid the negative bias that can occur with neutral language appearing negative.
• Offer suggestions on how to improve code e.g. simplification or expanding clarity.
• Ensure you give reasons for the changes you are proposing.

[richardhallett]

I've updated the mappings as requested, let me know what you think.