[Minutes] ITS IG call 2014-09-29 and main items

See
http://www.w3.org/2014/09/29-i18nits-minutes.html
and below as text. Next call will be in three weeks, same day (Monday) + time. 
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20141020T15

Main items to discuss: 

1) David will move the XLIFF / ITS mapping in the OASIS XLIFF 2.1 draft forward, and in there weeks from now we will have something to look at. People who have feedback on the XLIFF mapping 
https://www.w3.org/International/its/wiki/XLIFF_2.0_Mapping
(e.g. Serge / Renat) will give feedback ideally before. 

2) open data management for MT, see
https://www.w3.org/International/its/wiki/Open_Data_Management_for_Public_Automated_Translation_Services
Serge confirmed that the doc is of relevance and in three weeks from now he will make a push to get more interest. Again, people in this group who want to provide feedback should do so now.

- Felix



  [1]W3C

     [1] http://www.w3.org/

                              - DRAFT -

                                ITS IG

29 Sep 2014

  [2]Agenda

     [2] http://lists.w3.org/Archives/Public/public-i18n-its-ig/2014Sep/0007.html

  See also: [3]IRC log

     [3] http://www.w3.org/2014/09/29-i18nits-irc

Attendees

  Present
         felix, Yves, dF, joerg, serge

  Regrets
  Chair
         felix

  Scribe
         fsasaki

Contents

    * [4]Topics
        1. [5]roll call
        2. [6]action items
        3. [7]XLIFF 2.0 mapping
        4. [8]decide about XLIFF testing design
        5. [9]other agenda items
        6. [10]other open items
        7. [11]aob
    * [12]Summary of Action Items
    __________________________________________________________

  <scribe> scribe: fsasaki

roll call

  checking attendees ...

  <dF> joining audio in a minute..

  [13]http://lists.w3.org/Archives/Public/public-i18n-its-ig/2014
  Sep/0007.html

    [13] http://lists.w3.org/Archives/Public/public-i18n-its-ig/2014Sep/0007.html

action items

  [14]http://www.w3.org/International/its/ig/track/actions/open

    [14] http://www.w3.org/International/its/ig/track/actions/open

  action-40?

  <trackbot> action-40 -- Felix Sasaki to Assure that xliff2
  mapping is finished by end of june -- due 2014-05-30 -- OPEN

  <trackbot>
  [15]http://www.w3.org/International/its/ig/track/actions/40

    [15] http://www.w3.org/International/its/ig/track/actions/40

  close action-40

  <trackbot> Closed action-40.

XLIFF 2.0 mapping

  [16]https://www.w3.org/International/its/wiki/XLIFF_2.0_Mapping

    [16] https://www.w3.org/International/its/wiki/XLIFF_2.0_Mapping

  [17]http://lists.w3.org/Archives/Public/public-i18n-its-ig/2014
  Aug/0007.html

    [17] http://lists.w3.org/Archives/Public/public-i18n-its-ig/2014Aug/0007.html

  [18]http://www.w3.org/International/its/wiki/XLIFF_2.0_Mapping#
  Data_Categories_Not_Mapped_Yet

    [18] http://www.w3.org/International/its/wiki/XLIFF_2.0_Mapping#Data_Categories_Not_Mapped_Yet

  [19]http://lists.w3.org/Archives/Public/public-i18n-its-ig/2014
  Aug/0000.html

    [19] http://lists.w3.org/Archives/Public/public-i18n-its-ig/2014Aug/0000.html

  <dF> action 37 is done

  <trackbot> Error finding '37'. You can review and register
  nicknames at
  <[20]http://www.w3.org/International/its/ig/track/users>.

    [20] http://www.w3.org/International/its/ig/track/users%3E.

  close action-37

  <trackbot> Closed action-37.

  david: renat said he will check with serge, did not come back
  to us yet
  ... let's see what comes back from renat / serge

  yves: nothing to add on the mapping at the moment
  ... did not have time to follow up, will try to work on that in
  the coming months
  ... not sure if we will have time to implement everything
  before the end of the year
  ... phil and others are working on using it and implementing
  that in ocelot
  ... using e.g. lqi and provenance
  ... they will be working on it also on the end of the year
  rather than now

  felix: is that an issue process wise in OASIS? the OASIS xliff
  2.1 timing and the mapping progress?

  david: xliff tc decided that we want to have yearly releases
  ... two related things: 1) transfering the mapping into the
  OASIS specification format
  ... I am starting that work this week
  ... I am a bit worried
  ... if work continues in the wiki we may end up with scattered
  information
  ... like to have a simple rule: don't touch ... in the wiki so
  that I can transfer that to the OASIS template
  ... the OASIS draft will be public, only OASIS TC members will
  be able to edit
  ... must happen sooner or later
  ... we are kind of late
  ... implementations by the end of the year is fine
  ... question is: will we have approved spec in the committee
  specification phase
  ... I would take all categogries marked for review and leave
  others for now until next call

  felix: next call timing?

  david: before loc world

  <yves_> Oct-20 would work for me.

  <scribe> ACTION: felix to announce next call 20 october, to
  prepare for loc world [recorded in
  [21]http://www.w3.org/2014/09/29-i18nits-minutes.html#action01]

  <trackbot> Created ACTION-51 - Announce next call 20 october,
  to prepare for loc world [on Felix Sasaki - due 2014-10-06].

  david: felix had good input, also summarizing issues - some are
  not even issues, some categories are not metadata, this is not
  really relevant
  ... we should have a feeling how it goes in three weeks

  jörg: maybe inbetween david can give feedback on the work in
  progress

  david: sure, I will send a link to the xliff 2.1 draft

  serge: we (logrus) want to come back on XLIFF 2.0 mapping
  issue, for sure
  ... I understand that xliff 2.1 is going to incooperate ITS 2.0
  ... so we would like to get back to everything we discovered

  felix: would be great to get some feedback in the next three
  weeks

  serge: ok, I'll look into that

  [22]http://lists.w3.org/Archives/Public/public-i18n-its-ig/2014
  Aug/0000.html

    [22] http://lists.w3.org/Archives/Public/public-i18n-its-ig/2014Aug/0000.html

decide about XLIFF testing design

  [23]http://lists.w3.org/Archives/Public/public-i18n-its-ig/2014
  Sep/0008.html

    [23] http://lists.w3.org/Archives/Public/public-i18n-its-ig/2014Sep/0008.html

  david: not sure how the ITS2 test site worked - in OASIS we
  don't have application hosting, just simple SVN
  ... we have wiki and SVN
  ... that's it
  ... does not seem to me that we would be able to replicate W3C
  testing structure
  ... we will have reference files that we had for XLIFF 2.0
  ... XLIFF files with ITS extensions or mappings
  ... how they are supposed to look before and after
  ... test automation is not a requirement for OASIS
  ... in W3C you need to present test suite results to progress
  ... in OASIS you need to present statement of use
  ... advanced validation was also approved for XLIFF 2.1
  ... we will be able to test a lot using schematron rules,
  without having a specific test suite

  serge:

  <dF>
  [24]https://www.oasis-open.org/committees/download.php/54178/ba
  llot_2674.html

    [24] https://www.oasis-open.org/committees/download.php/54178/ballot_2674.html

  <dF> XLIFF TC approval of the ITS feature for 2.1

  df: )

  [discussion on ITS2 / XLIFF 2.1 outreach]

  felix: testing the mapping - would we need input files in a
  given format, e.g. HTML5?

  david: how the extraction is performed is normally out of scope
  of xliff - this may be an issue with ITS now
  ... for ITS we may have more stages even than input - output
  ... not sure about step between original format and XLIFF - it
  is probably not going to be normative
  ... we can have best practices - the xliff tc had reference
  guides but never talked about how the extraction is done

other agenda items

  rdf-its ontology - postponed

  "open data management for public automated translation
  services"

  [25]https://www.w3.org/International/its/wiki/Open_Data_Managem
  ent_for_Public_Automated_Translation_Services

    [25] https://www.w3.org/International/its/wiki/Open_Data_Management_for_Public_Automated_Translation_Services

  serge: please keep this on the agenda
  ... this topic will develop further
  ... if we don't have substantial revision of the document, it
  is time to get through the channels we have and try to push
  this throuhg
  ... I will try to propose this as a presentation topic at the
  lt-innovate summit
  ... we can try to email this to various people in this theme

  <scribe> ACTION: felix to announce work for data managemnt
  document [recorded in
  [26]http://www.w3.org/2014/09/29-i18nits-minutes.html#action02]

  <trackbot> Created ACTION-52 - Announce work for data managemnt
  document [on Felix Sasaki - due 2014-10-06].

other open items

  [27]http://www.dercom.de/en/projects

    [27] http://www.dercom.de/en/projects

  "An interface COTI between authoring and translation memory
  systems is planned. The specification may be downloaded from
  this page and commented."

  felix: any comments on this? should we contact the people?

  david: the people do what they think they have to do
  ... I went through the doc today
  ... this has an overlap with linport
  ... approach of spec is similar to linport and tip approach -
  sending a zip package that can contain project files
  ... not sure how the project files are supposed to be
  structured - the doc seems to define a soap envelope
  ... which is not in conflict with what we are doing
  ... this is a kind of web services interface
  ... they define an XML wrapper based on SOAP
  ... there is not necessarily a conflict
  ... but I'm a bit worried that there was no interest in contact
  - there is a potential for mismatch
  ... but at the same time I think there is not a clash - one
  could propose xliff 2.0 as a payload for their soap envelope
  ... xliff does not say anything about the web service should
  work
  ... there may be a conflict with the object model and API that
  people now want to see for XLIFF 2.0
  ... above feedback is based on me looking into this before
  today's call
  ... behind this there is a trade org of german content
  producers
  ... the spec does not seem to follow some current practices,
  e.g. it has its own definitions of keywords "must, can, ..."
  ... they are referencing xml and soap, and they are referencing
  some standards

  jörg: there is a huge gap in communication between different
  communities - it seems they don't know about xliff and so on

  david: hard to achieve things via mail

  felix: will be at tekom again, will try again to contact them
  and see what happens

  david: maybe alan melby could be helpful - linport is in clahs
  with this

  jörg: not really

  scribe: it is a little bit from linport and tipp, and then
  their own way

  david: xliff can be payload of anything

  jörg: I can check with Alan to see if he has talked to these
  guys

  felix: thanks

aob

  [28]http://lists.w3.org/Archives/Public/public-i18n-its-ig/2014
  Sep/0007.html

    [28] http://lists.w3.org/Archives/Public/public-i18n-its-ig/2014Sep/0007.html

  adjourned, by to all! next call in three weeks

Summary of Action Items

  [NEW] ACTION: felix to announce next call 20 october, to
  prepare for loc world [recorded in
  [29]http://www.w3.org/2014/09/29-i18nits-minutes.html#action01]
  [NEW] ACTION: felix to announce work for data managemnt
  document [recorded in
  [30]http://www.w3.org/2014/09/29-i18nits-minutes.html#action02]

  [End of minutes]
    __________________________________________________________


   Minutes formatted by David Booth's [31]scribe.perl version
   1.138 ([32]CVS log)
   $Date: 2014-09-29 15:53:34 $

    [31] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
    [32] http://dev.w3.org/cvsweb/2002/scribe/

Received on Monday, 29 September 2014 16:01:54 UTC