The name of the schema file for which the full path will be returned The full schema path Based on the provided schema name, this function returns the full URL to the schema document The name of the schema The version of the SensorML schema The full schema path Based on the provided schema name, this function returns the full URL to the schema document The URL to which the request will be submitted The body of the invalid request The response if it's a valid exception report Posts an invalid request to the url specified by methodURL post The URL to which the request will be submitted Comma-separated list of sensorID(s) to submit with the DescribeTasking request The response from the server Executes a DescribeTasking request post The URL to which the request will be submitted Sensor/Task ID to use for the request sensorID or taskID The response from the server Executes a DescribeResultAccess request post The exception report if it's valid Validates a returned exception report according to its schema and determines if it is an appropriate exception report for an SPS The exception report if it's valid Validates a returned exception report according to its schema and determines if it is an appropriate exception report for an SPS True/false depending on whether or not the provided exceptionCode is a valid exceptionCode for the provided operationName The exception report to check The exceptionCode to check The locator to check (a * can be provided to indicate that any locator value is allowed) Encoding Type True/false depending on whether or not the exception report is valid The exception report to check True/false depending on whether or not the exception report is valid The exception report to check True/false depending on whether or not the exception report is valid The SensorML/TML document if it's valid Validates a SensorML/TML document according to its schema The SensorML document if it's valid Validates a SensorML document according to its schema The TML document if it's valid Validates a TML document according to its schema The GetCapabilitiesResponse document if it's valid Validates a GetCapabilitiesResponse document according to its schema The GetCapabilitiesResponse document if it's valid Validates a GetCapabilitiesResponse document according to its schema The GetCapabilitiesResponse document if it's valid Validates a GetCapabilitiesResponse document according to its schema The GetCapabilitiesResponse document if it's valid Validates a GetCapabilitiesResponse document according to its schema The GetCapabilitiesResponse document if it's valid Validates a GetCapabilitiesResponse document according to its schema The GetCapabilitiesResponse document if it's valid Validates a GetCapabilitiesResponse document according to its schema The DescribeTaskingResponse document if it's valid Validates a DescribeTaskingResponse document according to its schema The DescribeTaskingResponse document if it's valid Validates a DescribeTaskingResponse document according to its schema The SubmitResponse document if it's valid Validates a SubmitResponse document according to its schema The SubmitResponse document if it's valid Validates a SubmitResponse document according to its schema The SubmitResponse document if it's valid Validates a GetStatusResponse document according to its schema The SubmitResponse document if it's valid Validates a GetStatusResponse document according to its schema The SubmitResponse document if it's valid Validates a GetStatusResponse document according to its schema The SubmitResponse document if it's valid Validates a GetStatusResponse document according to its schema The DescribeResultAccessResponse document if it's valid Validates a DescribeResultAccessResponse document according to its schema The DescribeResultAccessResponse document if it's valid Validates a DescribeResultAccessResponse document according to its schema The URN to validate True/False depending on whether or not the URN is valid Determines if a definition URN is valid according to the OGC Definition URN scheme [OGC 07-092r1]. Since this is a def urn, it must have 7 "pieces". NOTE: this check allows for both ogc and x-ogc as the namespace authority. The URN to validate True/False depending on whether or not the URN is a valid URN. Determines if a URN is valid The URN to validate True/False depending on whether or not the URN is valid according to the OGC URN scheme. NOTE: this check allows for both ogc and x-ogc as the namespace authority. Determines if a URN is valid The URL to validate True/False depending on whether or not the URL is valid Determines if a URL is valid Convert a valid ISO 8601 date time to a valid XSL datetime. It is assumed that dateString has already passed "sosFunctions:isValidDate". dateString is assumed to at least have a year month and day The time value to check for correctness The value to compare this time value to True if the time to check is valid; false otherwise Checks that the supplied timeToCheck value is a valid time or duration and that it occurs on or after the compareTime The date to be tested Check whether a date is a valid ISO 8601 date with at least a day included, or one of the valid constants. True/false depending on whether or not the duration is valid Checks duration values for validity (i.e. P1Y2M3DT5H10M30S) SensorID used in the Submit request The response to a DescribeTasking request for the sensor identified by the sensorID parameter The form used to gather the user input for the tasking request. True/False indicating whether the request should be constructed with an invalid notificationTarget element True/False indicating whether the request should be constructed with invalid parameter values True/False indicating whether the request should be constructed with missing required parameter values True/False indicating whether the request should be constructed with an invalid timeFrame value True/False indicating whether the service has complex InputParameters that were not handled by the Submit request form A Submit request document based on the supplied parameters Builds a Submit request document from the supplied parameters. This document can either have valid or invalid parameters. NOTE: This function does not currently handle most of the more complex scenarios within a Submit document (other than Position w/ coordinates). The function handles all simple InputParameters and Position InputParameters with coordinate elements. This function should be updated in the future to handle the more complex scenarios. 2000-01-01T00:00:00.000Z SensorID used in the Submit request The response to a DescribeTasking request for the sensor identified by the sensorID parameter The form used to gather the user input for the tasking request. True/False indicating whether the request should be constructed with an invalid notificationTarget element True/False indicating whether the request should be constructed with invalid parameter values True/False indicating whether the request should be constructed with missing required parameter values True/False indicating whether the request should be constructed with an invalid timeFrame value A Submit request document based on the supplied parameters Builds a Submit request document from the supplied parameters. This document can either have valid or invalid parameters. NOTE: This function does not currently handle most of the more complex scenarios within a Submit document (other than Position w/ coordinates). The function handles all simple InputParameters and Position InputParameters with coordinate elements. This function should be updated in the future to handle the more complex scenarios. 2000-01-01T00:00:00.000Z True/false depending on whether or not the position is valid Checks WGS84 position values for validity: 1) The position is in the correct format: longitude latitude (in decimal degrees) 2) The longitude is between -180 and 180 3) The latitude is between -90 and 90 True if position1 is greater than or equal to position2; false otherwise Compares two position values True/false depending on whether or not the WGS84BoundingBox is valid True/false depending on whether or not the WGS84BoundingBox is valid Performs a specific check on an ows:WGS84BoundingBox: 1) The UpperCorner and LowerCorner are valid according to the checkWGS84Position function 2) The UpperCorner values are greater than or equal to the LowerCorner values True/false depending on whether or not the BoundingBox is valid Performs a generic check on a ows:BoundingBox: 1) The UpperCorner and LowerCorner values are valid according to the checkPosition function 2) The UpperCorner values are greater than or equal to the LowerCorner values True/false depending on whether or not the position element (gml:pos, etc.) is valid Checks position values for validity. Does not do any specific checks to ensure that the position values correspond with their CRS. This function only checks that the values in the gml:pos element are in a numeric format separated by spaces with 2 or 3 coordinates (i.e. -150 -89 or -34.234234 10.00000 or 0.0000 34.00000 250 or 234234 234324) True/false depending on whether or not the InputDescriptor has a valid interval constraint