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

 


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

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


Subject: Modified: XLIFF TC Meeting


Submitter's message
minutes added
-- Dr. David Filip
Event Title: XLIFF TC Meeting

Date: Tuesday, 21 October 2014, 11:00am to 12:00pm EDT
Description

Please get the dial in information from our private Action Item here:
https://www.oasis-open.org/apps/org/workgroup/xliff/members/action_item.php?action_item_id=3663


This meeting counts towards voter eligibility.

Agenda

I Administration (0:00 - 0:10)
  A. Roll call  

  B. Approve meeting minutes, 7 October 2014
     https://lists.oasis-open.org/archives/xliff/201410/msg00041.html  

  C. XLIFF 2.0 as an ISO standard


  D. SOU Report (David)
     https://lists.oasis-open.org/archives/xliff/201410/msg00001.html


(* indicates new, not acted upon, since last meeting)

II XLIFF 2.1 (0:10 - 0:45)
  A. New XLIFF 2.1 Tracker page - Bryan     
  https://wiki.oasis-open.org/xliff/FeatureTracking

  B. ITS Mapping - XLIFF 2.1
   1. *possible issue with URN prefixes used to define acceptable namespaces in XLIFF 2.1 - DavidF
      https://lists.oasis-open.org/archives/xliff/201410/msg00009.html
   2. *ITS scope with sm/em - Yves
      https://lists.oasis-open.org/archives/xliff/201410/msg00015.html
   3. *ITS Mapping Update - some inconsistencies found - Yves
      https://lists.oasis-open.org/archives/xliff/201410/msg00017.html
   4. *ITS module implementation - Yves
      https://lists.oasis-open.org/archives/xliff/201410/msg00033.html

  C. *Error in spc 2.0 in example 5.2.6 (Yves)
     https://lists.oasis-open.org/archives/xliff/201409/msg00033.html

  D. *Media Type Registration Template for XLIFF V2.0 Committee Specification 01 is published
     https://lists.oasis-open.org/archives/xliff/201410/msg00028.html

  E. *Versions and Modules - Yves
     https://lists.oasis-open.org/archives/xliff/201410/msg00037.html


III Sub Committee Report (0:45 - 0:55)


IV Current and New Business (0:55 - )


Minutes

I Administration:

A. Roll call: Bryan, Yves, David W, David F., Fredrik Estreen, Joachim Shurig, Lucia, Soroush, Tom Comerford, Michael Ow, Asanka, Uwe.

  B. Approve meeting minutes, 7 October 2014
     https://lists.oasis-open.org/archives/xliff/201410/msg00041.html 

Fredrik: I second.

[no dissent]

B: Meeting minutes approved.

 

C. XLIFF 2.0 as an ISO standard

B: P&L SC and Peter are working on this topic.


D. SOU Report (David)

https://lists.oasis-open.org/archives/xliff/201410/msg00001.html

B: anything new here?

dF: it was just to tell everyone that it is available. This item should be removed from the ongoing agenda.

 

II XLIFF 2.1 (0:10 - 0:45)
  A. New XLIFF 2.1 Tracker page - Bryan    
  https://wiki.oasis-open.org/xliff/FeatureTracking

  B. ITS Mapping - XLIFF 2.1
   1. possible issue with URN prefixes used to define acceptable namespaces in XLIFF 2.1 - DavidF
      https://lists.oasis-open.org/archives/xliff/201410/msg00009.html
Y: We have several discussions going on on the mailing lists, both TC and ITS IG. One of them related to the issue with namespaces. The idea is to use a single XLIFF TC hosted namespace for the its module and mapping, there have not been objections to this idea.

dF: There are several good reasons to use an OASIS namespace for that (most importantly agents recognizing modules by a URN prefix, different semantics due to non-wellformed spans in XLIFF), all of them discussed on the mailing list. I suggest that we record consensus on that.

Is there any dissent or is more discussion required?

[no dissent]

B: Ok, we can record consensus and we can take this issue off the agenda.

DF: The namespace is already proposed in the current working draft: urn:oasis:names:tc:xliff:its:2.1

Fredrik: I think it can be considered done.

B: Ok, this point can be considered approved (Agenda II, B, 1)

 

   2. *ITS scope with sm/em - Yves
      https://lists.oasis-open.org/archives/xliff/201410/msg00015.html

Yves: I think this one is resolved as well.

Fredrik: I agree as well, in the discussions people agreed on that.

DF: I think it is not an issue on the XLIFF side. But there might be an issue with the simplification algorithm. It is premature to say if it will be normative or informative.

Fredrik: we might need some more normative language, we might need some statement around of what we consider invalid.

Yves: Bryan, I think this one is solved, we just need to add some text to the module definition.

dF: I think we fine for now, we will bring this up again when a detailed solution is elaborated. But all stakeholders agreed on the principle.


   3. *ITS Mapping Update - some inconsistencies found - Yves
      https://lists.oasis-open.org/archives/xliff/201410/msg00017.html

Yves: This one is relatively easy. There have been some inconsistencies on the examples.

dF: Renat submitted this through the comment list on my request, so that it is covered by OASIS feedback IPR policy. I am working with the document.


   4. *ITS module implementation - Yves
      https://lists.oasis-open.org/archives/xliff/201410/msg00033.html

Yves: that is just information about the current implementation, I made some changes and I wanted to make that information public.

B: Everyone please have a look and give feedback to Yves on that implementation.

 

  C. *Error in spc 2.0 in example 5.2.6 (Yves)
     https://lists.oasis-open.org/archives/xliff/201409/msg00033.html

B: We can fix that with errata or in the 2.1 version.

Yves: It is just a typo. I think that we can just fix it.

Fredrik: I do not know about the process of communicating errata and publishing the document.

DF: From Oasis point of view the only way how to amend 2.0 is Errata, I do not about the errata process, but I think we are moving well on the 2.1, so it should be OK to to have it fixed in 2.1, rather than having a separate errata document right now.

Fredrik: we can have errata on the main TC page informing people about the error.

DF: I suggest that the Chair explores the process of publishing the errata, as we do not know how the process relates to a full blown publishing process and if it’s worth spending time on it.

B: I will do it.

 

  D. *Media Type Registration Template for XLIFF V2.0 Committee Specification 01 is published
     https://lists.oasis-open.org/archives/xliff/201410/msg00028.html

B: Chet has made an official announcement.

DF: It would be good if we have a ballot resolution to make a provisional registration of the media type based on the CS.

Independent of the progress of the provisional registration we planned to merge the template for the final registration with the 2.1 spec.

B: Sure, we can vote on that.

DF: I will prepare the move and I will distribute it through the mailing list.

 

  E. *Versions and Modules - Yves
     https://lists.oasis-open.org/archives/xliff/201410/msg00037.html

Yves: I don’t have a strong opinion, but I want to know what is going to work in the long run.

DF: the link to my response is on that link too.

B: Users might not think of modules, but of features that tools can have.

DF: it will depend on the developer/owner of the particular module, whether they want the tools to work with the latest version of the module or not.

Fredrik: I think point 3 is hard to resolve if we say yes to points 1 and 2. I think it will cause confusion.

Joachim:  I do not think that there is a perfect solution in the real world.

Fredrik: We can change the answer to point one.

DF: I think discussion should continue.

B: we will have it on the agenda for next meeting.


III Sub Committee Report

D: I cannot report progress on the ISO submission as Peter is missing. There was a delay introcuced in Jamie coming back to Peter with the templates. Also there is no point in having an SC meeting today w/o Peter.

There will be the 5.5th Symposium next week in Vancouver, please come and register.


IV Current and New Business

 

Fredrik: I am looking for a standardised way how to embed information in inline tags. I am not sure if that can be a good addition to the standard, what do you think?

DF: Like a reference guide?

Fredrik: a way of embedding information in a predictable way.

Fredrik: I will start the discussion on the mailing list, but it will not be for the 2.1 version, as it can be a complex and long process.



Owner: Bryan Schnabel
Group: OASIS XML Localisation Interchange File Format (XLIFF) TC
Sharing: This event is shared with the OASIS Open (General Membership), and General Public groups. Public Event Link

Microsoft Outlook users: You will see event notifications requiring further action in your Outlook mail application.
Non-Outlook users: We still recommend subscribing to a Group or organization-wide calendar to keep your calendar updated.

  • Learn more about subscribing here.
  • View the updated Group web calendar here.

Attachment: ical_38521.ics
Description: application/ics

BEGIN:VCALENDAR
CALSCALE:GREGORIAN
METHOD:REQUEST
VERSION:2.0
PRODID:-//Kavi Corporation//NONSGML Kavi Groups//EN
X-MS-OLK-FORCEINSPECTOROPEN:TRUE
BEGIN:VTIMEZONE
TZID:America/New_York
BEGIN:STANDARD
DTSTART:20001029T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20061029T060000Z
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD
BEGIN:STANDARD
DTSTART:20071104T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000402T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=20060402T070000Z
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:20070311T020000
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
STATUS:CONFIRMED
TRANSP:OPAQUE
DTSTAMP:20141103T120835Z
DTSTART;VALUE=DATE-TIME;TZID=America/New_York:20141021T110000
DTEND;VALUE=DATE-TIME;TZID=America/New_York:20141021T120000
SEQUENCE:1
SUMMARY:XLIFF TC Meeting
LAST-MODIFIED:20141103T120835Z
ORGANIZER:tc_admin@oasis-open.org
DESCRIPTION:Please get the dial in information from our private Action I
 tem here:\nhttps://www.oasis-open.org/apps/org/workgroup/xli
 ff/members/action_item.php?action_item_id=3663\n\nAgenda: I 
 Administration (0:00 - 0:10)\n  A. Roll call  \n\n  B. Appro
 ve meeting minutes\, 7 October 2014\n     https://lists.oasi
 s-open.org/archives/xliff/201410/msg00041.html  \n\n  C. XLI
 FF 2.0 as an ISO standard\n\n\n  D. SOU Report (David)\n    
  https://lists.oasis-open.org/archives/xliff/201410/msg00001
 .html\n\n\n(* indicates new\, not acted upon\, since last me
 eting)\n\nII XLIFF 2.1 (0:10 - 0:45)\n  A. New XLIFF 2.1 Tra
 cker page - Bryan     \n  https://wiki.oasis-open.org/xliff/
 FeatureTracking\n\n  B. ITS Mapping - XLIFF 2.1\n   1. *poss
 ible issue with URN prefixes used to define acceptable names
 paces in XLIFF 2.1 - DavidF\n      https://lists.oasis-open.
 org/archives/xliff/201410/msg00009.html\n   2. *ITS scope wi
 th sm/em - Yves\n      https://lists.oasis-open.org/archives
 /xliff/201410/msg00015.html\n   3. *ITS Mapping Update - som
 e inconsistencies found - Yves\n      https://lists.oasis-op
 en.org/archives/xliff/201410/msg00017.html\n   4. *ITS modul
 e implementation - Yves\n      https://lists.oasis-open.org/
 archives/xliff/201410/msg00033.html\n\n  C. *Error in spc 2.
 0 in example 5.2.6 (Yves)\n     https://lists.oasis-open.org
 /archives/xliff/201409/msg00033.html\n\n  D. *Media Type Reg
 istration Template for XLIFF V2.0 Committee Specification 01
  is published\n     https://lists.oasis-open.org/archives/xl
 iff/201410/msg00028.html\n\n  E. *Versions and Modules - Yve
 s\n     https://lists.oasis-open.org/archives/xliff/201410/m
 sg00037.html\n\n\nIII Sub Committee Report (0:45 - 0:55)\n\n
 \nIV Current and New Business (0:55 - )\nGroup: OASIS XML Lo
 calisation Interchange File Format (XLIFF) TC\nCreator: Brya
 n Schnabel
URL:https://www.oasis-open.org/apps/org/workgroup/xliff/event.php?event_id=38521
UID:https://www.oasis-open.org/apps/org/workgroup/xliff/event.php?event_id=38521
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT00H15M00S
END:VALARM
END:VEVENT
END:VCALENDAR


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