RE: [trans-ws] RE: Translation Web Services Update

Hi Peter & Andrzej,

At this stage I feel I should point out some issues with the TWS specification that is currently preventing any further progress.

As we discussed in our last meeting, file transfer would be via URI. However this cannot yet be implemented until this is reflected in the schemas.

retreiveQuote - it was said that the quote should be sent via URI. This is not indicated in either the specification or the schemas. There is a method in the specification called Resource which is a URI. Should this be included as a parameter in the "Returned" section of the retreiveQuote service? This would make the passing back of the quote very easy and automated.

Peter: I have added a Quote URI to the return pararmerts of retreiveQuote.
I have also edited the transtype XSD files. We seem to have two files doing the same thing WSTransTypes.xsd and TransWSTypes.xsd. I have edited them both.

acceptQuote - One input for this service is a purchase order. PurchaseOrder only contains the PO number, should PurchaseOrder also contain a URI locating the physical PO?

Peter: I have added an optional parameter for the Purchase Order URI where the actual PO can be located.

submitJob - Again the same issue as above, PurchaseOrder is an input but with no URI containing PO location.

Peter: Same as acceptQuote

retrieveJobInformation - The same issue with PurchaseOrder as above

Peter: Same as acceptQuote

retrieveJobInformation - In the "Returned" parameters under the History section, Date is referred to and when compiled with AXIS it is assigned to be of type java.util.Date (which has been depreciated since version 1.1 of the API). Maybe it could be change to a Calendar type (which replaced the functionality of java.util.Date)?

Peter: Lets discuss on Thursday.

suspendJob & resumeJob & cancelJob - Something small here but all of these services are relatively similar in their requests and responses. This is not reflected in the specification where:

suspendJob = Passed-In resumeJob = Passed-In                           cancelJob = Passed-In
                Job Ticket                      Job Ticket                                      Job TIcket
                  Returned                      Returned                                               Returned
                Job Ticket                      Job Ticket                                      Job Ticket
                Succeeded                       Success Indicator                               Success Indicator
                Info                            Additional Information                         An information message

Peter: I have changed these so that the documentation has the same text. The schema was already the same.

An important issue to be addressed is that the specification for associateResource and what is in the schema do not conform.

i.e. In the specification the inputs are Job Ticket, Resource URI and Purpose, the returned values are Job Ticket, Success indicator and Resource URI.

The schema on the other hand is as follows:

<xsd:element name="associateResourceRequest">
    <xsd:complexType>
      <xsd:sequence>
        <xsd:element ref="types:ticket" />
        <xsd:element ref="types:resource" />
      </xsd:sequence>
    </xsd:complexType>
</xsd:element>
<xsd:element name="associateResourceResponse">
    <xsd:complexType>
      <xsd:sequence>
        <xsd:element ref="types:ticket" />
        <xsd:element ref="types:succeeded" />
      </xsd:sequence>
    </xsd:complexType>
</xsd:element>

As you can see from the above snippet, The input Purpose and the output Resource URI are ommitted from the schema. As I am working from these schemas, this needs to be addressed.

Peter: I have fixed this.

disassociateResource - The returned value on the specification documen for this servicet is "Acknowledgement", however in the schema, the return values are of type Job Ticket and Succeeded. The document needs to be edited to reflect this.

Peter: I have changed the documentation to match the schema.

Finally and probably most importantly the following two services are in the specification but not in the schema; retrieveResourceInformation & retrieveFullResourceList. As AXIS generates code using TransWSTypes.xsd and if they are not in it, the code will not be generated!

Peter: Lets talk on Thursday.

I hope that some of this is of use and can be fixed, let me know what you think.

Best Regards,

Kevin

++++++++++++++++++
Kevin Bargary BSc.
Research Assistant,
Localisation Research Centre,
University of Limerick,
Ireland.
Email: Kevin.Bargary@ul.ie
Telephone: 061-213557
++++++++++++++++++

trans-ws message