Merge pull request oam-dev#458 from resouer/dev

v0.3.0 pre release

Author: resouer

3.component_model.md

@@ -10,7 +10,7 @@ Components describe functional units that may be instantiated as part of a large
 
 The role of a `ComponentDefinition` entity is to permit component providers to declare, in infrastructure-neutral format, the runtime characteristics of such unit of execution. 
 
-For example, each microservice in an application is described as a component. Note that `ComponentDefinition` itself is not an instance of that microservice, but a declaration of the configurable runtime characteristics of that microservice. 
+For example, each microservice in an application is described as a component. Note that `ComponentDefinition` itself is *NOT* an instance of that microservice, but a declaration of the configurable attributes of that microservice. These configurable attributes should be expose as a list of parameters which allow the application team to set and instantiate this component later at deployment time.
 
 In practice, a simple containerized workload, a Helm chart, or a cloud database may all be modeled as a component.
 
@@ -49,16 +49,17 @@ Here are the attributes that provide top-level information about the component d
 
 #### Schematic
 
-The schematic section of component definition declares the schematic of a reusable and deployable unit that will composed an application in the later workflow.
+This section declares the schematic of a component that could be instantiated as part of an application in the later workflow.
+
+The OAM specification has no opinion or enforcement on the schematic itself as long as a JSON schema equivalent parameter list is defined. Though in order to make the specification implementable, several built-in approaches (`cue`, `helm`, `kube`) are defined as part of the specification for now.
+
+> Note: below sections may change in the future releases.
 
 | Attribute | Type | Required | Default Value | Description |
 |-----------|------|----------|---------------|-------------|
 | `kube` | [Template](#template)  | N | | A template with parameter list for certain [Kubernetes workload](https://kubernetes.io/docs/concepts/workloads/) resource as component. |
 | `cue` | [Template](#template)  | N || A [CUE](https://github.com/cuelang/cue) module as component. |
 | `helm` | [Template](#template) | N || A [Helm](https://helm.sh) chart as component. |
-| `extension` | `unstructured` | N || A extension point for adding other approaches to provide schematic for component definition. |
-
-The OAM specification has no opinion on the encapsulation tools to enable component definition schematic. Though in order to make the specification implementable, we currently introduced several built-in approaches (`cue`, `helm`, `kube`) as part of the specification.
 
 ```yaml
 kind: ComponentDefinition
@@ -110,8 +111,6 @@ kind: ComponentDefinition
         - "spec.template.spec.containers[0].image"
 ```
 
-Also, by leveraging the `extension` field, the implementation could have its own way to encapsulate a component and expose a parameter list for users to instantiate it. In future releases, we may introduce a structured extension point to enhance this field. 
-
 ### Example
 
 Below is a full example of CUE based component definition:

7.application.md

@@ -6,7 +6,7 @@ This section describes how applications are designed and deployed.
 
 ## Application
 
-The _Application_ entity defines which components will be instantiated once the application is deployed. 
+The _Application_ entity defines a list of components that will be instantiated once the application is deployed. 
 
 Users will specify the final parametrization of each component and the traits that are applied to augment their functionality or alter their behavior. Additionally, a set of scopes grouping different subsets of components can be specified.
 

README.md

@@ -31,9 +31,9 @@ In Open Application Model, we propose an app-centric approach instead:
 
 ## Read the specification
 
-|                                | Previous Stable Release | Latest Release |    Working Draft                  |
+|                                | Previous Releases | Latest Release |    Working Draft                  |
 | :----------------------------: | :-----------------: | :------------: |:--------------------------------: |
-| OAM Specification              | [v0.1.0](https://github.com/oam-dev/spec/releases/tag/v0.1.0) | [v0.3.0](SPEC.md) |  --  |
+| OAM Specification              | [v0.1.0](https://github.com/oam-dev/spec/releases/tag/v0.1.0), [v0.2.1](https://github.com/oam-dev/spec/releases/tag/v0.2.1) | [v0.3.0](SPEC.md) |  --  |
 
 ## See it in action