docs

OpenTOSCA · Oct 14, 2024 · 4b9587d · 4b9587d
1 parent 88f4cae
commit 4b9587d
Show file tree

Hide file tree

Showing 4 changed files with 6 additions and 6 deletions.
diff --git a/docs/docs/normative/index.md b/docs/docs/normative/index.md
@@ -282,7 +282,7 @@ software.application:
 
 #### service.application
 
-The abstract &#34;service.application&#34; node type defines a generic software application, which provides a service.
+The abstract &#34;service.application&#34; node type defines a generic software application, which provides a service. It is not normative how this component is implemented. This could be implemented by a Kubernetes Deployment Resource along with a Kubernetes Service Resource on Kubernetes or by a Systemd Service Unit on a virtual machine.
 
 ```yaml linenums="1"
 service.application:
@@ -574,7 +574,7 @@ file.storage:
 
 #### ingress
 
-The abstract &#34;ingress&#34; node type defines a generic ingress service, which is a reverse proxy that exposes an upstream application.
+The &#34;ingress&#34; node type manages a generic ingress service, which is a reverse proxy that exposes an upstream application. It is not normative how this component is implemented. This could be implemented by an Ingress resource on Kubernetes or by a reverse proxy, such as NGINX or Caddy, on a virtual machine.
 
 ```yaml linenums="1"
 ingress:

diff --git a/docs/docs/normative/tosca-vintner-profile-core.yaml b/docs/docs/normative/tosca-vintner-profile-core.yaml
@@ -148,7 +148,7 @@ node_types:
                 type: management
     service.application:
         derived_from: software.application
-        description: The abstract "service.application" node type defines a generic software application, which provides a service.
+        description: The abstract "service.application" node type defines a generic software application, which provides a service. It is not normative how this component is implemented. This could be implemented by a Kubernetes Deployment Resource along with a Kubernetes Service Resource on Kubernetes or by a Systemd Service Unit on a virtual machine.
         metadata:
             vintner_normative: 'true'
             vintner_abstract: 'true'
@@ -338,7 +338,7 @@ node_types:
             vintner_normative: 'true'
     ingress:
         derived_from: node
-        description: The abstract "ingress" node type defines a generic ingress service, which is a reverse proxy that exposes an upstream application.
+        description: The "ingress" node type manages a generic ingress service, which is a reverse proxy that exposes an upstream application. It is not normative how this component is implemented. This could be implemented by an Ingress resource on Kubernetes or by a reverse proxy, such as NGINX or Caddy, on a virtual machine.
         metadata:
             vintner_normative: 'true'
         properties:

diff --git a/docs/docs/variability4tosca/rules/index.md b/docs/docs/variability4tosca/rules/index.md
@@ -7,7 +7,7 @@ tags:
 
 --8<-- "enumerate.html"
 
-# DRAFT: Deployment Technology Rules Specification 1.0 Release Candidate
+# Deployment Technology Rules Specification 1.0 Release Candidate
 
 !!! info "Hidden Information"
     The document does not specify quality assignments at this stage.

diff --git a/tasks/docs/generate/rules/template.ejs b/tasks/docs/generate/rules/template.ejs
@@ -7,7 +7,7 @@ tags:
 
 --8<-- "enumerate.html"
 
-# DRAFT: Deployment Technology Rules Specification 1.0 Release Candidate
+# Deployment Technology Rules Specification 1.0 Release Candidate
 
 !!! info "Hidden Information"
     The document does not specify quality assignments at this stage.