Internet draft format (#135)

* Server Discovery

* Share Creation Notification

* Accessing the Resource

* Add code / token flow in spec.yaml

* Consolidate scope and assumptions section

* capitalise defined terms, other small corrections

* Write out security advantages of the invite flow

* remove references in Invite flow section

* Refer to I-D spec from API spec

* userId -> userID

* Bring field descriptions in line with I-D. Ref #117

* response codes

* Discovery document fields from API spec to I-D spec

* typo

* refactor: hal+json -> json as response type

* Reduce header nesting

First work on describing the required and optional Share Creation Notification fields

Share Creation Notification Fields

document notifications

Make the same point but without referencing a GitHub issue

Introduction -> Abstract

kramdown-rfc ./kramdown-input.md > draft-lopresti-open-cloud-mesh.xml

kramdown

whiteline before bullets

use README.md as the Kramdown filename to avoid losing changes when rebasing etc

* Put code blocks back into Appendix B

* Unindent Appendix B headers by one level

* You can now simply upload the readme to https://author-tools.ietf.org/ and click 'HTML', then 'open in browser'

* Update README.md

Just add my email

* code block syntax

---------

Co-authored-by: Mahdi Baghbani <[email protected]>
Co-authored-by: Micke Nordin <[email protected]>