Update 3.0.0.md

renamed to smartAPI specificiation. added introduction section to also point to smartAPI specific elements and to the website.

Author: micheldumontier

versions/3.0.0.md

@@ -1,13 +1,15 @@
-# OpenAPI Specification
+# smartAPI Specification
 
-#### Version 3.0.0 [adapted for smartAPI]
+#### Version 3.0.0 
 
 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [BCP 14](https://tools.ietf.org/html/bcp14) [RFC2119](https://tools.ietf.org/html/rfc2119) [RFC8174](https://tools.ietf.org/html/rfc8174) when, and only when, they appear in all capitals, as shown here.
 
 This document is licensed under [The Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.html).
 
 ## Introduction
 
+The smartAPI Specification (smartAPI) is a community-based extension of the OpenAPI specification. It features new metadata elements and value sets to promote the interoperability of web-based APIs. This document seamlessly integrates smartAPI specific extensions with the OpenAPI specification. However, a list of the smartAPI specific elements has been [automatically generated](smartapi-list.md). More information about the smartAPI initiative can be found on its [website](http://smart-api.info).
+
 The OpenAPI Specification (OAS) defines a standard, language-agnostic interface to RESTful APIs which allows both humans and computers to discover and understand the capabilities of the service without access to source code, documentation, or through network traffic inspection. When properly defined, a consumer can understand and interact with the remote service with a minimal amount of implementation logic.
 
 An OpenAPI definition can then be used by documentation generation tools to display the API, code generation tools to generate servers and clients in various programming languages, testing tools, and many other use cases.