[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Translation Web Services Specification
Hi Kevin, Thanks very much for this. It is of great help. Can I ask if you could send mails to the Trans-WS mailing list or cc the list. I think you will need to join the TC first but as the LRC are corporate members of OASIS, this should be no problem. Thanks again for your help, Peter. -----Original Message----- From: Kevin.Bargary [mailto:Kevin.Bargary@ul.ie] Sent: 03 August 2005 15:16 To: Reynolds, Peter; Kevin.Bargary Cc: Michael.J.Bourke; Reinhard.Schaler Subject: RE: Translation Web Services Specification Hi Peter, Thanks for that, we have now got the most recent specification. Just a few more things that I found whilst going through the schema. I'm sorry if you are not the right person to be telling these issues to but I said I'd point it out before I moved on. There is one tag missing from the schema causing it to be invalid. <xsd:element name="count-group"> is the guilty tag as it has no </element> closing tag. Also there is another issue where the namespaces being imported into the schema, for example; <xsd:import namespace="urn:oasis:names:tc:wstrans:v1:WSTransCountryCodesISO3166" schemaLocation="WSTransCountryCodesISO3166.xsd" /> The actual XSD names follow the naming convention; TransWSCountryCodesISO3166.xsd TransWSDomainTypes.xsd TransWSLanguageCodesISO639.xsd etc...... Therefore the schema cannot import them as it is looking for the wrong filenames. This applys to all of the namespaces being imported in the following segment of the latest version of the specification; <xsd:import namespace="urn:oasis:names:tc:wstrans:v1:WSTransCountryCodesISO3166" schemaLocation="WSTransCountryCodesISO3166.xsd" /> <xsd:import namespace="urn:oasis:names:tc:wstrans:v1:WSTransDomainTypes" schemaLocation="WSTransDomainTypes.xsd" /> <xsd:import namespace="urn:oasis:names:tc:wstrans:v1:WSTransLanguageCodesISO639" schemaLocation="WSTransLanguageCodesISO639.xsd" /> <xsd:import namespace="urn:oasis:names:tc:wstrans:v1:WSTransMimeTypes" schemaLocation="WSTransMimeTypes.xsd" /> <xsd:import namespace="urn:oasis:names:tc:wstrans:v1:WSTransScope" schemaLocation="WSTransScope.xsd" /> <xsd:import namespace="urn:oasis:names:tc:wstrans:v1:WSTransServiceTypes" schemaLocation="WSTransServiceTypes.xsd" /> I hope this information is of use, Best Regards, Kevin Bargary -----Original Message----- From: Reynolds, Peter [mailto:Peter.Reynolds@bowneglobal.ie] Sent: 03 August 2005 14:49 To: Kevin.Bargary Cc: Michael.J.Bourke Subject: RE: Translation Web Services Specification Hi Kevin, Michael, Thanks for this and the correction. You can find the latest spec in a mail from Andrzej. See below. http://www.oasis-open.org/apps/org/workgroup/trans-ws/email/archives/200 506/msg00005.html I will contact you when I get back from holidays at the end of August. Andrzej, Do you know where we can get the document, WSTransCountryCodesISO3166.xsd. Thanks, Peter. -----Original Message----- From: Kevin.Bargary [mailto:Kevin.Bargary@ul.ie] Sent: 03 August 2005 13:58 To: Reynolds, Peter Cc: Michael.J.Bourke Subject: Translation Web Services Specification Hi Peter, We were just wondering here at the LRC is this the most recent version of the TWS specification? http://www.oasis-open.org/committees/download.php/13001/trans-ws-spec.ht ml The schema defined in the Appendix 7 seems to have some errors in it which is affecting the WSDL validity. For example, it cannot locate WSTransCountryCodesISO3166.xsd. And also: xmlnsxsd="http://www.w3.org/2001/XMLSchema" should be xmlns:xsd="http://www.w3.org/2001/XMLSchema" Thanks in Advance, Kevin Bargary
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]