All the images are linked to Bitbucket not to this repo. Furthermore, Github does not allow embedding svg images in the .md, so they have to be converted to png.

Hello Everyone,

I have setup a project page, and setup a draft proposal for submitting the SLA project to the OAI Technical Oversight Board (TOB).

Please help me finish the proposal, and discuss any other considerations as we move to setup the incubator project.

Thanks!!

Kin Lane

• Make document instances identifiable and versionable, e.g. with a top-level sla4api property containing a semver value (I note that some of the examples have an sla property with a numeric 1.0 value)
• move Specification.md to something like versions/1.0.0-pre.md
• use full text of Apache-2.0 license so GitHub identifies it correctly
• GitHub: fix No description, website, or topics provided.
• GitHub: add Code of Conduct and issue templates early in the process
• use open formats for documentation directory
• define a media-type for SLA instance documents following the vnd.oai. style with +json variant and version property
• recommend naming of the instance documents (e.g. sla.yaml or sla.json)
• consider registering an RFC5785 .well_known location
• include a (cut-down?) contact object so contact information specific to the SLA info is available
• allow specification extensions (x- properties) within SLA instance documents for extensibility
• update Swagger 2.0 examples to OpenAPI 3.x - should include patch version: e.g. 3.0.3
• is it appropriate to use floating point number types for currency values (especially for things like BTC)? Suggest integer with divisor or multiplier / units modifier
• use ISO-8601 for durations
• set up CI to validate/lint markdown using mdv - no issues currently
• s/quartely/quarterly/g
• s/matric/metric/g
• s/managment/management/g

Fix the example of metric, it doesn't show correct values for property resolution.