@ctranoris
How is the mapping between "Area of Service: Region specification" and "Area of Service" supposed to work?
"Area of Service" contains a list of ISO 3166-1 Alpha-2 country codes.
Let's assume as example that "Area of Service" has the values ["ES","FR","DE"]
"Area of Service: Region specification" specifies a list of regions for each of the countries listed in "Area of Service".
For the example above, we might need to specify up to 3 lists in "Area of Service: Region specification": one for ES, one for FR, one for DE, with example values: [["ES",1,2,3],["FR",0],["DE,2,4,5,7]].
How these lists are supposed to be represented according to the tmf633 service specification provided in gst.json , where "Area of Service: Region specification" is defined as a set of integers?
Shouldn't "Area of Service: Region specification" be defined as a set of sets of integers?
Can you please provide an example?
@ctranoris
How is the mapping between "Area of Service: Region specification" and "Area of Service" supposed to work?
"Area of Service" contains a list of ISO 3166-1 Alpha-2 country codes.
Let's assume as example that "Area of Service" has the values ["ES","FR","DE"]
"Area of Service: Region specification" specifies a list of regions for each of the countries listed in "Area of Service".
For the example above, we might need to specify up to 3 lists in "Area of Service: Region specification": one for ES, one for FR, one for DE, with example values: [["ES",1,2,3],["FR",0],["DE,2,4,5,7]].
How these lists are supposed to be represented according to the tmf633 service specification provided in gst.json , where "Area of Service: Region specification" is defined as a set of integers?
Shouldn't "Area of Service: Region specification" be defined as a set of sets of integers?
Can you please provide an example?