Reset API version in main branch to wip

code/API_definitions/network-slice-assignment.yaml

@@ -48,7 +48,7 @@ info:
 
     As a specific rule, error `501 - NOT_IMPLEMENTED` can be only a possible error response if it is explicitly documented in the API.
 
-  version: 0.1.0
+  version: wip
   x-camara-commonalities: 0.6
   license:
     name: Apache 2.0

code/API_definitions/network-slice-booking.yaml

@@ -43,7 +43,7 @@ info:
 
     As a specific rule, error `501 - NOT_IMPLEMENTED` can be only a possible error response if it is explicitly documented in the API.
 
-  version: 0.1.0
+  version: wip
   x-camara-commonalities: 0.6
   license:
     name: Apache 2.0
@@ -52,7 +52,7 @@ externalDocs:
   description: Project documentation at CAMARA
   url: https://github.com/camaraproject/NetworkSliceBooking
 servers:
-  - url: "{apiRoot}/network-slice-booking/v0.1"
+  - url: "{apiRoot}/network-slice-booking/vwip"
     variables:
       apiRoot:
         default: http://localhost:9100

code/Test_definitions/network-slice-assignment-assign.feature

@@ -1,4 +1,4 @@
-Feature: CAMARA Network Slice Assignment API v0.1.0 - Operation assign
+Feature: CAMARA Network Slice Assignment API vwip - Operation assign
 
     # Input to be provided by the implementation to the tester
     #
@@ -7,11 +7,11 @@ Feature: CAMARA Network Slice Assignment API v0.1.0 - Operation assign
 	# * List of device identifier types which are not supported, among: phoneNumber, ipv4Address, ipv6Address.
 	# * For this version, CAMARA does not allow the use of networkAccessIdentifier, so it is considered by default as not supported.
 	#
-    # References to OAS spec schemas refer to schemas specified in network-slice-assignment.yaml, version 0.1.0
+    # References to OAS spec schemas refer to schemas specified in network-slice-assignment.yaml, version wip
 
   Background: Common assignSlice setup
     Given an environment at "apiRoot"
-    And the resource "/network-slice-assignment/v0.1/slices/devices/assign"
+    And the resource "/network-slice-assignment/vwip/slices/devices/assign"
     And the header "Content-Type" is set to "application/json"
     And the header "Authorization" is set to a valid access token
     And the header "x-correlator" complies with the schema at "#/components/schemas/XCorrelator"

code/Test_definitions/network-slice-assignment-get.feature

@@ -1,4 +1,4 @@
-Feature: CAMARA Network Slice Assignment API v0.1.0 - Operation get
+Feature: CAMARA Network Slice Assignment API vwip - Operation get
 
 	# Get information about devices assigned to an existing network slice.
 
@@ -14,11 +14,11 @@ Feature: CAMARA Network Slice Assignment API v0.1.0 - Operation get
 	# * List of device identifier types which are not supported, among: phoneNumber, ipv4Address, ipv6Address.
 	# * For this version, CAMARA does not allow the use of networkAccessIdentifier, so it is considered by default as not supported.
 	#
-    # References to OAS spec schemas refer to schemas specified in network-slice-assignment.yaml, version 0.1.0
+    # References to OAS spec schemas refer to schemas specified in network-slice-assignment.yaml, version wip
 
   Background: Common getDevice setup
     Given an environment at "apiRoot"
-    And the resource "/network-slice-assignment/v0.1/slices/devices/get/{sliceId}"
+    And the resource "/network-slice-assignment/vwip/slices/devices/get/{sliceId}"
     And the header "Content-Type" is set to "application/json"
     And the header "Authorization" is set to a valid access token
     And the header "x-correlator" complies with the schema at "#/components/schemas/XCorrelator"

code/Test_definitions/network-slice-assignment-release.feature

@@ -1,4 +1,4 @@
-Feature: CAMARA Network Slice Assignment API v0.1.0 - Operation release
+Feature: CAMARA Network Slice Assignment API vwip - Operation release
 
     # Input to be provided by the implementation to the tester
     #
@@ -9,11 +9,11 @@ Feature: CAMARA Network Slice Assignment API v0.1.0 - Operation release
 	# * The AssignmentInfo of an existing Slice assignment
 	# * The AssignmentInfo of an existing Slice assignment with status "AVAILABLE", and with provided values for "sink" and "sinkCredential"
 	#
-    # References to OAS spec schemas refer to schemas specified in network-slice-assignment.yaml, version 0.1.0
+    # References to OAS spec schemas refer to schemas specified in network-slice-assignment.yaml, version wip
 
   Background: Common releaseSlice setup
     Given an environment at "apiRoot"
-    And the resource "/network-slice-assignment/v0.1/slices/devices/release"
+    And the resource "/network-slice-assignment/vwip/slices/devices/release"
     And the header "Content-Type" is set to "application/json"
     And the header "Authorization" is set to a valid access token
     And the header "x-correlator" complies with the schema at "#/components/schemas/XCorrelator"

code/Test_definitions/network-slice-assignment-retrieve.feature

@@ -1,4 +1,4 @@
-Feature: CAMARA Network Slice Assignment API v0.1.0 - Operation retrieve
+Feature: CAMARA Network Slice Assignment API vwip - Operation retrieve
 
 	# Retrieve the list of network slices to which a device is assigned.
 
@@ -14,11 +14,11 @@ Feature: CAMARA Network Slice Assignment API v0.1.0 - Operation retrieve
 	# * List of device identifier types which are not supported, among: phoneNumber, ipv4Address, ipv6Address.
 	# * For this version, CAMARA does not allow the use of networkAccessIdentifier, so it is considered by default as not supported.
 	#
-    # References to OAS spec schemas refer to schemas specified in network-slice-assignment.yaml, version 0.1.0
+    # References to OAS spec schemas refer to schemas specified in network-slice-assignment.yaml, version wip
 
   Background: Common retrieveSlice setup
     Given an environment at "apiRoot"
-    And the resource "/network-slice-assignment/v0.1/slices/devices/retrieve"
+    And the resource "/network-slice-assignment/vwip/slices/devices/retrieve"
     And the header "Content-Type" is set to "application/json"
     And the header "Authorization" is set to a valid access token
     And the header "x-correlator" complies with the schema at "#/components/schemas/XCorrelator"

code/Test_definitions/network-slice-booking-createSession.feature

@@ -1,4 +1,4 @@
-Feature: CAMARA Network Slice Booking API v0.1.0 - Operation createSlice
+Feature: CAMARA Network Slice Booking API vwip - Operation createSlice
 
     # Input to be provided by the implementation to the tester
     #
@@ -14,11 +14,11 @@ Feature: CAMARA Network Slice Booking API v0.1.0 - Operation createSlice
     # * An Area outside the supported area
     # * A combination of request parameters including service area, start time, and end time, configuration information of network slicing
     #
-    # References to OAS spec schemas refer to schemas specified in network-slice-booking.yaml, version 0.1.0
+    # References to OAS spec schemas refer to schemas specified in network-slice-booking.yaml, version wip
 
   Background: Common createSlice setup
     Given an environment at "apiRoot"
-    And the resource "/network-slice-booking/v0.1/slices"
+    And the resource "/network-slice-booking/vwip/slices"
     And the header "Content-Type" is set to "application/json"
     And the header "Authorization" is set to a valid access token
     And the header "x-correlator" complies with the schema at "#/components/schemas/XCorrelator"

code/Test_definitions/network-slice-booking-deleteSession.feature

@@ -1,4 +1,4 @@
-Feature: CAMARA Network Slice Booking API v0.1.0 - Operation deleteSlice
+Feature: CAMARA Network Slice Booking API vwip - Operation deleteSlice
 
     # Input to be provided by the implementation to the tester
     #
@@ -7,11 +7,11 @@ Feature: CAMARA Network Slice Booking API v0.1.0 - Operation deleteSlice
     #
     # Testing assets:
     # * The sliceId of an existing slice.
-    # * References to OAS spec schemas refer to schemas specified in network-slice-booking.yaml, version 0.1.0
+    # * References to OAS spec schemas refer to schemas specified in network-slice-booking.yaml, version wip
 
   Background: Common deleteSlice setup
     Given an environment at "apiRoot"
-    And the resource "/network-slice-booking/v0.1/slices/{sliceId}"
+    And the resource "/network-slice-booking/vwip/slices/{sliceId}"
     And the header "Content-Type" is set to "application/json"
     And the header "Authorization" is set to a valid access token
     And the header "x-correlator" complies with the schema at "#/components/schemas/XCorrelator"

code/Test_definitions/network-slice-booking-getSession.feature

@@ -1,4 +1,4 @@
-Feature: CAMARA Network Slice Booking API v0.1.0 - Operation getSlice
+Feature: CAMARA Network Slice Booking API vwip - Operation getSlice
 
     # Input to be provided by the implementation to the tester
     #
@@ -7,11 +7,11 @@ Feature: CAMARA Network Slice Booking API v0.1.0 - Operation getSlice
     #
     # Testing assets:
     # * The sliceId of an existing slice.
-    # * References to OAS spec schemas refer to schemas specified in network-slice-booking.yaml, version 0.1.0
+    # * References to OAS spec schemas refer to schemas specified in network-slice-booking.yaml, version wip
 
   Background: Common getSlice setup
     Given an environment at "apiRoot"
-    And the resource "/network-slice-booking/v0.1/slices/{sliceId}"
+    And the resource "/network-slice-booking/vwip/slices/{sliceId}"
     And the header "Content-Type" is set to "application/json"
     And the header "Authorization" is set to a valid access token
     And the header "x-correlator" complies with the schema at "#/components/schemas/XCorrelator"