[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [trans-ws] Minutes of Trans-WS teleconference
Depending on the agreed scope, ebXML may be relevant for aspects related to a translation exercise, though not directly involved with the translation tasks themselves (i.e., budget tracking, resource assignment, distribution fallback, event trigger/condition handling etc...) Of course, ebXML is large and complex! Steve. Stephen Holmes Voice: +353 (1) 241 5732 Novell, Inc., the leading provider of information solutions http://www.novell.com >>> Gerard Cattin des Bois <gcatt@windows.microsoft.com> 02/03/03 7:15 PM >>> Here is the list of other formats and standards: 1. Workflow Management Coalition (WfMC): http://www.wfmc.org/ 2. LISA/OSCAR: TMX -- Translation memory exchange format: http://www.lisa.org/tmx/ 3. LISA/OSCAR: TBX -- Terminological data exchange format: http://www.lisa.org/tbx/ 4. OASIS/XLIFF: XLIFF -- localization project data format: http://www.oasis-open.org/committees/xliff/ 5. OASIS/UDDI: UDDI -- "meta service" for buildding/locating flexible web services using WSDL tModels: http://www.oasis-open.org/committees/uddi-spec/tcspecs.shtml#uddiv2 TBX is also based on ISO 12620 data categories specification. Any others we should consider? Thanks, -Gérard Gérard Cattin des Bois Lead Program Manager, LocStudio Services Windows Productivity Tools Team gcatt@microsoft.com (425) 706-1592 Symptom and sign of Inner Peace: An unmistakable ability to enjoy each moment... -----Original Message----- From: Tony Jewtushenko [mailto:Tony.Jewtushenko@oracle.com] Sent: Friday, January 31, 2003 3:13 AM To: trans-ws@lists.oasis-open.org Subject: [trans-ws] Minutes of Trans-WS teleconference Minutes Trans-WS Teleconference - 30 January 2003, 4pm Dublin/London time 1/ roll call Attending: Peter, Tony, Bill, Gerard, Paul, Milan, Reinhard, Steven, Yuri, Andrei, Steven 2/ Minutes of previous meeting were accepted. 3/ Scope of work Bill proposes: Loosely dividing into three issues - The service (funtionality) The technology The issues The Service (functionality) Scope What we need eg. ability to submit a job What we definitely don't want to include eg. currency based transactions What we need to be open eg. Ability to query support eg. Ability to extend status reporting What we need to be closed Relations What we can build on Financial translations Content management (or at least specifications) What can build on us Workflow products BPEL4WS The technology Web Services WSDL Define messages & ports Define bindings in terms of uri's UDDI UDDI tModel Allow each company to register eBXML processSchema more rigourous than WSDL can build on WSDL definition ? eBXML repository Can refer to the UDDI repository ? Some issues File transfer Mechanisms ? Efficiency ? external reference via URL Security Authentication Encryption of transfered data Can we build on the Web Services Security stuff ? Financial Other spec's Minimal support inherent Peter: These issues will be considered together with the emails which TC members have sent describing individual goals of Trans Web Services. TC to work towards agreement on the work to be undertaken over the next three to six months. Comments from TC: Steve: interested in broader views, like engineering, QA, not just translation. Need to define what's included in the initial set beyond translation. Gerard - aspects mentioned could be defined under WSMCCM, which is a standard for defining workflow where participants may not know of each others. Suggests that we discuss Paul - on financial side, must be some payments standards - so we don't have to reinvent. Peter - not in a position to fully scope our work. Translation is the obvious place to start, since everyone will have interest in this. Tony agreed with Steve that we should include other areas of localization process from the start. Bill to circulate the list of functionality, and all will reply with their ideas before next meeting. 4/ Schedule Review: Timescale for final draft deliverables as modified at this meeting (emphasis added to changes/additions): - TwS 1.0 TWS Overview Abstract 8 weeks after first meeting (new interim milestone) - TwS 1.0 TWS Business Process Terminology Specification; 12 weeks after 1st meeting - TwS 1.0 WSDL Documents; 20 weeks after 1st meeting - TwS 1.0 UDDI Deploy WSDL as UDI tModels; 24 weeks after 1st meeting Tony doesn't think the present schedule is feasible - e.g. 4 more meetings to complete final version of spec is unrealistic unless we change the meeting frequency. Reinhard suggested that we initially work on an abstract introduction report, then a more detailed technical spec that lists the exact methods or tModels that will be delivered. Peter suggested that the schedule can be left as is and that the TC schedule a face 2 face meeting to thrash out the work very quickly, and in this way the TC can make up some time. TC agreed with this sentiment. 5/ Implementation - TC decided that it's too early for this topic - need to define deliverables per item 3 first. 6/ Co-ordinating between localisation standards Gerard felt that it would be advantageous to work with other standards bodies, sooner rather than later. Gerard will send around a mail detailing the various file standards that we should incorporate into our work, especially with file transfers, etc. Peter mentioned an ad hoc teleconference between the various localization / globalization teams is scheduled for next week in order to discuss areas of common interest and define ways of working more effectively together. Since all agenda items were discussed, the meeting was adjourned without motion. Next meeting in 2 weeks - same time/same dial in instructions. Reminders and agenda to be sent in advance.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC