[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [trans-ws] RE: Translation Web Services Update
Hi Peter,
I am just back from the Lisa conference in Zurich. Do you want me to
check the XHTML aspect of your changes? Does Dreamweaver output correct
XHTML?
Best Regards,
AZ
Reynolds, Peter wrote:
> Hi Kevin,
>
> Thanks for doing this.
>
> It would be good if you could add the fileUri.
>
> I can do the HTML document here. I am using dreamweaver and I can use
> the WYSIWYG editor. This will convert the '<' and '>' marks.
>
> Thanks,
>
> Peter.
>
> ------------------------------------------------------------------------
> *From:* Kevin.Bargary [mailto:Kevin.Bargary@ul.ie]
> *Sent:* 10 November 2005 11:23
> *To:* Reynolds, Peter; Kevin.Bargary; azydron@xml-intl.com;
> trans-ws@lists.oasis-open.org
> *Cc:* Michael.J.Bourke; Reinhard.Schaler@ul.ie
> *Subject:* RE: [trans-ws] RE: Translation Web Services Update
>
> Hi Peter,
>
> I have finished making the changes to the XSD's...The WSDL files also
> had to be updated to contain the different elements that were added. I
> have done this. The specification has to be updated to contain these
> revised WSDL files. With regards the *optional fileUri parameter *that
> you mentioned should be added to the *requestQuote* service, I can do
> that here on my side if that suits? I am fairily familiar with where the
> changes need to be made at this stage!
>
> Final question, how do you suggest I update the specification HTML
> document? What was is quickest? I have been using notepad++ and its a
> pain because all of the tags are escaped to > and < and I don't
> want to mess up the layout!
>
> Regards,
> Kevin
>
> ------------------------------------------------------------------------
> *From:* Reynolds, Peter [mailto:Peter.Reynolds@bowneglobal.ie]
> *Sent:* 08 November 2005 16:00
> *To:* Kevin.Bargary; azydron@xml-intl.com; trans-ws@lists.oasis-open.org
> *Cc:* Michael.J.Bourke; Reinhard.Schaler@ul.ie
> *Subject:* RE: [trans-ws] RE: Translation Web Services Update
>
> Hi Kevin,
>
> The files I changed were the ones which Andrzej sent after his last
> update. Can I give you a call in the morning about this.
>
> Thanks,
>
> Peter.
>
> ------------------------------------------------------------------------
> *From:* Kevin.Bargary [mailto:Kevin.Bargary@ul.ie]
> *Sent:* 08 November 2005 15:49
> *To:* Reynolds, Peter; Kevin.Bargary; azydron@xml-intl.com;
> trans-ws@lists.oasis-open.org
> *Cc:* Michael.J.Bourke; Reinhard.Schaler@ul.ie
> *Subject:* RE: [trans-ws] RE: Translation Web Services Update
>
> Hi Peter,
>
> It seems that the changes you made were on an older version of the
> TransWSTypes schema. Changes that we made a while back to adhere to a
> naming convention are not in the version you sent out. For example, what
> should read ;* TransWSServiceTypes:CodeContentType_service *reads as
> *WSTransServiceTypes:CodeContentType_service *in the version you sent out.
>
> I can remake the changes on the document you sent out and send you back
> the TransWSTypes schema tomorrow. As regards updating the specification,
> the WSDL's in the appendix of the specification still have the *WSTrans
> *format as opposed to the *TransWS *format which was agreed upon. I
> would say that some work is needed on the specification to update it
> properly. Regarding *quoteURI, *and* purchaseOrderUri*....* *Do these
> only have to appear once in the specification schema descriptions? Or
> everytime they are used?* *
>
> Regards,
>
> Kevin
>
> ------------------------------------------------------------------------
> *From:* Reynolds, Peter [mailto:Peter.Reynolds@bowneglobal.ie]
> *Sent:* 08 November 2005 15:06
> *To:* Kevin.Bargary; azydron@xml-intl.com; trans-ws@lists.oasis-open.org
> *Cc:* Michael.J.Bourke; Reinhard.Schaler@ul.ie
> *Subject:* RE: [trans-ws] RE: Translation Web Services Update
>
> Hi Kevin,
>
> Thanks for this. I think we should have an optional fileUri parameter
> which can be used for this. I can make this change in the morning if you
> want to pass me what you have done already. Please edit the
> specification if needed.
>
> Thanks,
>
> Peter.
>
> ------------------------------------------------------------------------
> *From:* Kevin.Bargary [mailto:Kevin.Bargary@ul.ie]
> *Sent:* 08 November 2005 11:27
> *To:* Reynolds, Peter; Kevin.Bargary; azydron@xml-intl.com;
> trans-ws@lists.oasis-open.org
> *Cc:* Michael.J.Bourke; Reinhard.Schaler@ul.ie
> *Subject:* RE: [trans-ws] RE: Translation Web Services Update
>
> Hi Peter,
>
> I have made all of the changes necessary in the schema's {I am un-sure
> how to update the actual specification document, do I have to manually
> edit it??)
>
> I still have one question regarding the following...
>
> |/requestQuote/|
> <file:///C:/Documents%20and%20Settings/Kevin.Bargary/Desktop/trans-ws-spec/trans-ws-spec-xhtml-1.0.html#requestQuote>/
> Job ticket created by publisher. Meta data sent about the job. *The
> location of a file can be indicated using a URI*. Quote information
> returned/
>
> This is a snippet from the specification...I have bolded somthing which
> is confusing, what file is being referred to in a requestQuote? The
> specification does not indicate the passing back of a URI for this
> particular service? The quoteURI is passed back using the service
> retrieveQuote? Does this functionality need to be added?
>
> Regards,
> Kevin
>
> ------------------------------------------------------------------------
> *From:* Reynolds, Peter [mailto:Peter.Reynolds@bowneglobal.ie]
> *Sent:* 07 November 2005 16:52
> *To:* Kevin.Bargary; azydron@xml-intl.com; trans-ws@lists.oasis-open.org
> *Cc:* Michael.J.Bourke; Reinhard.Schaler@ul.ie
> *Subject:* RE: [trans-ws] RE: Translation Web Services Update
>
> Kevin,
>
> If you had time that would be wonderful. Let me know if there are any
> problems and I will get it done.
>
> I will call you later in the week about the IGNITE conference.
>
> Thanks,
>
> Peter.
>
> ------------------------------------------------------------------------
> *From:* Kevin.Bargary [mailto:Kevin.Bargary@ul.ie]
> *Sent:* 07 November 2005 16:47
> *To:* Reynolds, Peter; Kevin.Bargary; azydron@xml-intl.com;
> trans-ws@lists.oasis-open.org
> *Cc:* Michael.J.Bourke; Reinhard.Schaler@ul.ie
> *Subject:* RE: [trans-ws] RE: Translation Web Services Update
>
> Hi Peter,
>
> I can make the changes on my side, to speed things up a little if you
> would like? I can update both the specification and the XSD's and send
> you on the final versions?
>
> Regards,
> Kevin
>
> ------------------------------------------------------------------------
> *From:* Reynolds, Peter [mailto:Peter.Reynolds@bowneglobal.ie]
> *Sent:* 07 November 2005 14:25
> *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: [trans-ws] RE: Translation Web Services Update
>
> Hi Kevin, all,
>
> Thanks for this. I will not be able to look at this until tomorrow
> morning. I will try and resolve these issues then.
>
> Thanks,
>
> Peter.
>
> ------------------------------------------------------------------------
> *From:* Kevin.Bargary [mailto:Kevin.Bargary@ul.ie]
> *Sent:* 07 November 2005 12:18
> *To:* Reynolds, Peter; Kevin.Bargary; azydron@xml-intl.com;
> trans-ws@lists.oasis-open.org
> *Cc:* Michael.J.Bourke; Kevin.Bargary; Reinhard.Schaler@ul.ie
> *Subject:* RE: [trans-ws] RE: Translation Web Services Update
>
>
> Hi Peter,
>
> Here are a few things I spotted when browsing through the spec and the
> updated schema. I'll be able to give more detailed feedback when I start
> generating the code etc..
>
> "*purchaseOrderUri*" with the attribute "*uri*" is not reflected in the
> TransWSTypes schema
>
> For example "*resource*" with the attribute "*uri*" is reflected by
>
> <xsd:element name="*resource*">
> <xsd:complexType>
> <xsd:attribute name="*uri*" type="anyURI" use="required" />
> </xsd:complexType>
> </xsd:element>
>
> *purchaseOrderUri* needs to have something similar to this in schema also.
> *quoteUri* is the same...
>
> One more thing I am not familiar with how XML deals with spacing but if
> only for consistency "*retrieveResource Information Response*" should be
> "*retrieveResourceInformationResponse*". The spacing occurs in both
> specification and the schema.
>
> Finally in the service "*UploadFile*" specifically in*
> FileUploadResponse* there is a reference to
> *types:uri*
>
> This is no *uri* type in the schema..Actually on second look,
> "*UploadFile*" is not in the schema at all...I don't know if this is
> supposed to be omitted or not? Plus, in the spec, the request for the
> service "*UploadFile*" is *fileUpload*, it should be *fileUploadRequest*
> to match the *fileUploadResponse*
> **
> |/requestQuote/|
> <file:///C:/Documents%20and%20Settings/Kevin.Bargary/Desktop/trans-ws-spec/trans-ws-spec-xhtml-1.0.html#requestQuote>/
> Job ticket created by publisher. Meta data sent about the job. *The
> location of a file can be indicated using a URI*. Quote information
> returned/
>
> This is a snippet from the specification...I have bolded somthing which
> is confusing, what file is being referred to in a requestQuote?
>
>
> I hope this helps.. and apologies if any of the points made are
> invalid...I'll let you know if I find anything else..
> Best Regards,
> Kevin
> ------------------------------------------------------------------------
> *From:* Reynolds, Peter [mailto:Peter.Reynolds@bowneglobal.ie]
> *Sent:* 07 November 2005 09:50
> *To:* Reynolds, Peter; Kevin.Bargary; azydron@xml-intl.com;
> trans-ws@lists.oasis-open.org
> *Cc:* Michael.J.Bourke; Kevin.Bargary; Reinhard.Schaler@ul.ie
> *Subject:* RE: [trans-ws] RE: Translation Web Services Update
>
> Hi all,
>
> I hope you all had a good weekend.
>
> I have attached the latest version of specification following our
> discussions on Thursday. Can you review and get back to me if there are
> issues.
>
> Thanks,
>
> Peter.
>
> ------------------------------------------------------------------------
> *From:* Reynolds, Peter [mailto:Peter.Reynolds@bowneglobal.ie]
> *Sent:* 31 October 2005 12:26
> *To:* Kevin.Bargary; azydron@xml-intl.com; trans-ws@lists.oasis-open.org
> *Cc:* Michael.J.Bourke; Kevin.Bargary; Reinhard.Schaler@ul.ie
> *Subject:* [trans-ws] RE: Translation Web Services Update
>
> Hi all,
>
> I have edited the specification in the light of Kevin's comments. The
> updated spec is attached. Please also see my responses to Kevin's mail
> below. We can use this mail and edited specification for our meeting on
> Thursday.
>
> Thanks,
>
> Peter.
>
> ------------------------------------------------------------------------
> *From:* Kevin.Bargary [mailto:Kevin.Bargary@ul.ie]
> *Sent:* Thu 20/10/2005 15:53
> *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.
>
> 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
> *++++++++++++++++++*
>
>
> ---------------------------------------------------------------------------------------------------
> *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_35003&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]