clarin.eu:cr1:p_1423750293168BASWebServiceThis is a derived web-service profile from the core model which describes the web-services at BAS. It uses extended components Service, ParameterGroup and Parameter from the core model (with different group name BASWebServices).
Changes from version 1.0 to 1.1:
Added component cmdi-collectiontype in component Service to allow coding of ResourceType according to DC-3806.
Added element isInternalDefaultConfigurationParameter (boolean) in component Parameter to allow the coding of non-setable default parameters of webservices.
Changes from Version 1.1 to 1.2:
Added displayName to Parameter.
Added Developer to Operation.productionThe name of the web service or set of web services.A description of the web service or set of web services.This Operation Name should be resolvable in the Service ServiceDescription, i.e., the WSDL or WADL document describing how to technically invoke the service.The Operation Description should describe what this operation does to the input to produce the output.name of the parameter; this string usually matches the exact parameter name as being used in a REST callDescription of the parametermimetype of the file, if the parameter is used to denote an input or output file. If the parameter does not denote an input/output files, this element is not present.a value domain, in general taken from the well-known XMLSchema data types (Biron et al., 2004), e.g., ID.if set true, the parameter does not denote input/output data but rather a configuration parameter that controls the behavior of the service, e.g. the languagelink to IsoCat if applicableinternal semantic typing used by chaining mechanismsthe default value for this parameter.If set to 'true' the parameter is not accessible in the REST call of this service, but rather an internal parameter that is always set to the default value (given in the element Default). The reason the parameter is shown in the CMDI is two-fold: 1.) The setting can be used by the backend server that implements this webservice to set default parameters, and 2.) this information might be useful for developers to see what default parameters are used in this services in comparism to a more general service that allows the setting of the same parameters.Preferred name to display this parameter, e.g. in a front end interfacea possible value or value range or regular expression for this parameteroptional description of a valuelink to IsoCat for semantic of a possible valuename of the parameter; this string usually matches the exact parameter name as being used in a REST callDescription of the parametermimetype of the file, if the parameter is used to denote an input or output file. If the parameter does not denote an input/output files, this element is not present.a value domain, in general taken from the well-known XMLSchema data types (Biron et al., 2004), e.g., ID.if set true, the parameter does not denote input/output data but rather a configuration parameter that controls the behavior of the service, e.g. the languagelink to IsoCat if applicableinternal semantic typing used by chaining mechanismsthe default value for this parameter.If set to 'true' the parameter is not accessible in the REST call of this service, but rather an internal parameter that is always set to the default value (given in the element Default). The reason the parameter is shown in the CMDI is two-fold: 1.) The setting can be used by the backend server that implements this webservice to set default parameters, and 2.) this information might be useful for developers to see what default parameters are used in this services in comparism to a more general service that allows the setting of the same parameters.Preferred name to display this parameter, e.g. in a front end interfacea possible value or value range or regular expression for this parameteroptional description of a valuelink to IsoCat for semantic of a possible valuename of the parameter; this string usually matches the exact parameter name as being used in a REST callDescription of the parametermimetype of the file, if the parameter is used to denote an input or output file. If the parameter does not denote an input/output files, this element is not present.a value domain, in general taken from the well-known XMLSchema data types (Biron et al., 2004), e.g., ID.if set true, the parameter does not denote input/output data but rather a configuration parameter that controls the behavior of the service, e.g. the languagelink to IsoCat if applicableinternal semantic typing used by chaining mechanismsthe default value for this parameter.If set to 'true' the parameter is not accessible in the REST call of this service, but rather an internal parameter that is always set to the default value (given in the element Default). The reason the parameter is shown in the CMDI is two-fold: 1.) The setting can be used by the backend server that implements this webservice to set default parameters, and 2.) this information might be useful for developers to see what default parameters are used in this services in comparism to a more general service that allows the setting of the same parameters.Preferred name to display this parameter, e.g. in a front end interfacea possible value or value range or regular expression for this parameteroptional description of a valuelink to IsoCat for semantic of a possible valuename of the parameter; this string usually matches the exact parameter name as being used in a REST callDescription of the parametermimetype of the file, if the parameter is used to denote an input or output file. If the parameter does not denote an input/output files, this element is not present.a value domain, in general taken from the well-known XMLSchema data types (Biron et al., 2004), e.g., ID.if set true, the parameter does not denote input/output data but rather a configuration parameter that controls the behavior of the service, e.g. the languagelink to IsoCat if applicableinternal semantic typing used by chaining mechanismsthe default value for this parameter.If set to 'true' the parameter is not accessible in the REST call of this service, but rather an internal parameter that is always set to the default value (given in the element Default). The reason the parameter is shown in the CMDI is two-fold: 1.) The setting can be used by the backend server that implements this webservice to set default parameters, and 2.) this information might be useful for developers to see what default parameters are used in this services in comparism to a more general service that allows the setting of the same parameters.Preferred name to display this parameter, e.g. in a front end interfacea possible value or value range or regular expression for this parameteroptional description of a valuelink to IsoCat for semantic of a possible valueThe name of a person who has or is developing this operation. The name of the organisation that provided funding for the development of this operation.The proper reference when the operation is cited in a publication.