OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

trans-ws message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: Translation Web Services Update


Peter (and Andrzej),

I think we need to re-assess what we are doing. The basic issue I see is
that Kevin (and the LRC) were going to do a basic reference implementation;
now there seems to be considerable work to be done in finalising and
synchronising the spec and the schema which should probably be done by the
TC? I know that both issues are connected, for us it is just a point of
scope and work involved (for which we have only limited funds). I will try
to ring you today to discuss.

Reinhard

-----Original Message-----
From: Andrzej Zydron [mailto:azydron@xml-intl.com] 
Sent: 20 October 2005 20:49
To: Kevin.Bargary
Cc: 'Reynolds, Peter'; trans-ws@lists.oasis-open.org; Michael.J.Bourke;
Kevin.Bargary; Reinhard.Schaler@ul.ie
Subject: Re: Translation Web Services Update

Hi Kevin and Peter,

First of all many thanks to Kevin for all his hard work - his contribution
is immeasurable in its value.

I had a suspicion that we would come across issues like this - as this is
the first reference implementation. I am at the moment extremely busy, so it
would be easier for me initially to deal with the issues as Kevin suggests
via email.

My recommendation is that Kevin updates the schemas as required as he is now
closest to the issues and knows best how to affect the required changes.

Best Regards,

AZ

Kevin.Bargary wrote:
> Hi Peter,
>  
> I am not in work for all of next week so I will not be able to do 
> another webex meeting. I will however be checking my emails so any 
> feedback that you or Andrzej have on my mail would be appreciated.
>  
> Regards,
>  
> Kevin
> 
> ----------------------------------------------------------------------
> --
> *From:* Reynolds, Peter [mailto:Peter.Reynolds@bowneglobal.ie]
> *Sent:* 20 October 2005 16:01
> *To:* Kevin.Bargary; azydron@xml-intl.com; 
> trans-ws@lists.oasis-open.org
> *Cc:* Michael.J.Bourke; Kevin.Bargary; Reinhard.Schaler@ul.ie
> *Subject:* RE: Translation Web Services Update
> 
> Hi Kevin,
>  
> Thanks very much for this.
>  
> Andrzej, I sent you a mail suggesting we have another webex type 
> meeting so that you can see what Kevin has done. Are you interested in 
> doing this. We could then deal with the issue Kevin has mentioned and 
> have the spec edited before the next TC meeting.
>  
> Thanks,
>  
> Peter.
> 
> ----------------------------------------------------------------------
> --
> *From:* Kevin.Bargary [mailto:Kevin.Bargary@ul.ie]
> *Sent:* 20 October 2005 15:54
> *To:* Reynolds, Peter; azydron@xml-intl.com
> *Cc:* Michael.J.Bourke; Kevin.Bargary; 'Reinhard.Schaler@ul.ie'
> *Subject:* 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.
> 
> *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?
> 
> *submitJob -* Again the same issue as above,/ PurchaseOrder/ is an 
> input but with no URI containing PO location.
> 
> *retrieveJobInformation -* The same issue with/ PurchaseOrder/ as 
> above
> 
> *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)?
> 
> *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
> 
> 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.
> 
> *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.
> 
> 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!
> 
> 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
> *++++++++++++++++++*
> 
> 
> ----------------------------------------------------------------------
> ----------------------------- *Text inserted by Panda Platinum 2005 
> Internet Security:*
> 
> This message has NOT been classified as spam. If it is unsolicited 
> mail (spam), click on the following link to reclassify it: It is spam!
> <http://127.0.0.1:6083/Panda?ID=pav_33423&SPAM=true>
> ----------------------------------------------------------------------
> -----------------------------


-- 


email - azydron@xml-intl.com
smail - c/o Mr. A.Zydron
	PO Box 2167
         Gerrards Cross
         Bucks SL9 8XF
	United Kingdom
Mobile +(44) 7966 477 181
FAX    +(44) 1753 480 465
www - http://www.xml-intl.com

This message contains confidential information and is intended only for the
individual named.  If you are not the named addressee you may not
disseminate, distribute or copy this e-mail.  Please notify the sender
immediately by e-mail if you have received this e-mail by mistake and delete
this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free as
information could be intercepted, corrupted, lost, destroyed, arrive late or
incomplete, or contain viruses.  The sender therefore does not accept
liability for any errors or omissions in the contents of this message which
arise as a result of e-mail transmission.  If verification is required
please request a hard-copy version. Unless explicitly stated otherwise this
message is provided for informational purposes only and should not be
construed as a solicitation or offer.





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]