From 8b586fc6212c9ad50ef1eee44151dc138d2af8ba Mon Sep 17 00:00:00 2001
From: Ricardo Serrano Gutierrez
 <145554214+TEF-RicardoSerr@users.noreply.github.com>
Date: Tue, 4 Jun 2024 18:41:53 +0200
Subject: [PATCH] Create API-Scope-Enhancement Template.md

---
 documentation/API-Scope-Enhancement Template.md | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
 create mode 100644 documentation/API-Scope-Enhancement Template.md

diff --git a/documentation/API-Scope-Enhancement Template.md b/documentation/API-Scope-Enhancement Template.md
new file mode 100644
index 0000000..6bc1078
--- /dev/null
+++ b/documentation/API-Scope-Enhancement Template.md	
@@ -0,0 +1,17 @@
+# API Scope Enhancement Template
+This template captures all the information that a partner should fill out when proposing a scope enhancement for an existing CAMARA API
+
+
+| **Field** | Description | 
+| ---- | ----- |
+| API name | [Name of the API or API family whose scope is proposed to be enhanced](url) |
+| New API name | New API name proposed to encompass the new scope (if applies) |
+| Scope Enhancement owner | Company submitting the API enhancement. |
+| Scope Enhancement summary | High level description / scope of the API or API family, and two/three examples of in-scope business cases. |
+| Technical viability | Identify the underlying network/cloud capabilities which are needed for the support of this API or API family, relating these capabilities them to standards maturity. <br><em>Example: this API requires the availability of NEF with this Rel-15 "X"feature</em>. 
+| Commercial viability | Specify the availability of commercial or (industrialized) open-source solutions for the identified network/cloud capabilities. <br><em> NOTE: If open-source, provide a publicly available reference/link to the actual solution, and specify the version under consideration.</em>|
+| YAML code available? | YES / NO. |
+| Validated in lab/productive environments? | YES / NO. <br>If YES, specify if it was lab network or productive network. |
+| Validated with real customers? | YES / NO. <br>If YES, specify how many customers participated in the evaluation, and what their use cases were. <br><em>NOTE: It is not mandatory (though recommendable) to specify the name of the customers. </em> |
+| Validated with operators? | YES / NO. <br> If YES, specify how many operators participated in the evaluation. <br><em>NOTE: It is not mandatory (though recommendable) to specify the name of the operators. </em> |
+| Supporters in API Backlog Working Group | List of supporters. <br><em> NOTE: That shall be added by the Working Group. </em> |