Working towards the next version of the SWIM Supporting Material

Page tree

Working towards the next version of the SWIM Supporting Material

Skip to end of metadata
Go to start of metadata


Requirement

Title

Service categories

Identifier

SWIM-SERV-009

Requirement

A service description shall include the categories to which the service belongs based on the PCP information exchange areas:

  • Aeronautical information exchange;
  • Meteorological information exchange; 
  • Cooperative network information exchange;
  • Flight information exchange.

Rationale

Service category information allows discovering services by a series of classification criteria.

This requirement supports decision making in terms of service suitability in relation to a particular usage context.

Verification

Completeness: Verify that the PCP category is present.

Consistency: Not applicable.

Correctness: Not Applicable. 

Examples/Notes

Note: It is best practice to include additional category information, and state the service categorisation scheme used, by inclusion or reference. The SESAR 1 ISRM Portfolio [RD 5] is a good source for service categories.

Level of Implementation

Mandatory


Guidance

Examples

See the Service categories section within the Donlon TOBT Setting Service Description.

Guidance for JSON service description

Unable to render {include} The included page could not be found.

info

Guidance on the full set of categories as available within the European SWIM Registry is provided at requirement SWIM-REG-0004 Service categorization.

Schema

The guidance concerns JSON Schema v0.0.3 (see Schema releases).

		"serviceCategorisation":
				{
					"description" : "A taxonomy used to classify a service by the type of service provided or by some other technological or architectural solution. [SWIM-SERV-009]",
					"$ref" : "#/definitions/ServiceCategorisation"
				},



		"ServiceCategorisation" : 
		{
			"description" : "A taxonomy used to classify a service by the type of service provided or by some other technological or architectural solution. [SWIM-SERV-009]",
			"type": "object",
			"additionalProperties": false,
			"required": ["serviceType", "lifeCycleStage", "businessActivityType", "intendedConsumer", "informationCategory", "applicationMessageExchangePattern"],
			"properties":
			{
				"informationCategory":
				{
					"description" : "TBD",
					"type" : "array",
					"items" : { "$ref":"#/definitions/CodeInformationExchangeCategory" },
					"minItems": 1
				},
			}
		},

Rules expressed for the cases as defined in Registry URD.

caserules
COMPLIANTMandatory, one or more values
CANDIDATEsame
DEFINITIONsame

Guidance

Select one or more values in field informationCategory, within field serviceCategorisation.

Enumerated values 

Type CodeInformationExchangeCategory defines the Information exchange area as from PCP.

AERONAUTICAL_INFORMATION_EXCHANGE 

METEOROLOGICAL_INFORMATION_EXCHANGE  

COOPERATIVE_NETWORK_INFORMATION_EXCHANGE 

FLIGHT_INFORMATION_EXCHANGE 

SWIM_INFRASTRUCTURE_EXCHANGE

Note: This value is not in the scope of SWIM-SERV-009 and should not be used. It is in the enumeration to give complete coverage of the PCP.

Example

   "serviceCategorisation": {
	  
      "informationCategory": [
        "FLIGHT_INFORMATION_EXCHANGE"
      ],
	  
    }

A complete JSON example is available in page JSON example - Donlon TOBT Setting service description.

More information

More information on service categories can be found on the Using Service Categories page. It is especially useful when listing "additional category information" as mentioned in the best practice in the requirement.

  • No labels