---------- Forwarded message ----------
From:
Johannes Lehtinen <johannes.lehtinen@rossum.fi>Date: 2012/4/11
Subject: Fixes and proposals related to WSDL 2012-04-11 by JL
To: FFM TC List <
ffm@lists.oasis-open.org>
Hello, all.
I have been going through accepted spec versions published after February to update the WSDL and XML schemas accordingly. While doing this, I noticed couple of issues for which I propose fixes or changes in this e-mail.
Section 8.2.1.2 Activity, State and Step
In Table 15, ActivitySpecification, name and description of property "ActivitiesLocationData" are incorrect (see Section 5.1.2.2 Work Type Specification structure, Figure 9 and the following text, as well as Section 5.1.2.3 where "Activity Location Data" is described).
Current property name: ActivitiesLocationData
Fixed property name: ActivityLocationData
Current description: Data elements providing information the Assignee will need to reach the Activities Location. See Section 5.1.2.3.
Fixed description: Data elements providing information the Assignee will need to reach the location associated with the Activity. See Section 5.1.2.3.
(There are no further references to "ActivitiesLocation" or "Activities Location" in the spec.)
Section 8.4.1.2 Field-Initiated Request
Section 8.4.1.3 Field-Initiated Request Response
Inconsistent way of writing "TimeStamp" vs. "Timestamp". Elsewhere in the spec written as "Timestamp", propose to use that instead.
In Table 56, FieldInitiatedRequest, rename property "TimeStamp" to "Timestamp".
In Table 57, FieldInitiatedRequestResponse, rename property "TimeStamp" to "Timestamp".
(No further references to "TimeStamp" or "time stamp" found in the spec.)
Section 8.4.1.4 Field-Initiated Request Operation Result Structures
In Table 58, FirGetResponseResult, incorrect type for property "Responses".
Current type: Sequence of FIRResponse
Fixed type: Sequence of FieldInitiatedRequestResponse
(No further references to "FIRResponse" in the spec.)
Section 8.4.2 Operations
In Table 60, Field-Initiated Request Operations. Propose to use "FieldInitiatedRequest" instead of "Fir" in parameter names to be consistent with how properties were renamed elsewhere.
On row describing "FIR_EXECUTE":
Current input parameters:
Fir: FieldInitiatedRequest
Fixed input parameters:
FieldInitiatedRequest: FieldInitiatedRequest
On row describing "FIR_GET_RESPONSE"
Current input parameters:
FirIds: Sequence of Identifier
Fixed input parameters:
FieldInitiatedRequestIds: Sequence of Identifier
(Could not find "Fir" elsewhere except as part of FIR_... operation result types FirGetResponseResult, etc, and WSDL operation names FirGet, etc, which are consistent with the way result types and operations have been named elsewhere, WrPutResult, WrPut, etc.)
Section 9.2 Primitive data types
In Table 106, Primitive data types / XML schema type mappings, the XML schema type associated with primitive data type "Boolean" is incorrect (corrupted by global Boolean renaming operation):
Current XML schema type: xs:Boolean
Fixed XML schema type: xs:boolean
(There are no further references to "xs:Boolean" in the spec.)