[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Modified: XLIFF TC Call
|
Event Title: XLIFF TC Call Date: Tuesday, 05 April 2016, 11:00am to 12:00pm EDT Description Please get the dial in information from our private Action Item here: This meeting counts towards voter eligibility. Agenda I Administration (0:00 - 0:10) B. Approve meeting minutes, 15 March 2016 D. Requesting progress of ISO submission of XLIFF 2.0 E. XLIFF 2.0 Support - Survey (Lucía) F. Action Item progress (as tracked in kavi AI tracker) II XLIFF 2.1 (0:10 - 0:45) * indicates new topic, not yet discussed A. Discuss whether can be allowed at all extension points (Ryan)
IV Current and New Business (0:55 - Minutes Attendance: Bryan, Yves, David F, Fredrik, Soroush, Lucia, Peter R., Felix Sasaki, Tom C., Phil. ________________________________ Agenda I Administration (0:00 - 0:10) B. Approve meeting minutes, 15 March 2016 B: I move to approve the meetings Y: I second. D. Requesting progress of ISO submission of XLIFF 2.0 P: Chet, Jayme Clark, David F were presents from OASIS. Jayme made clear that there were be no changes to the standard, but suggestions will be given to the TC and it will decide whether to implement changes or not. We are preparing a document that needs to go to the secretary of the TC-37, that will be translated into French and that will go directly to be presented as a standard. It will go for a vote process. David gave a good overview of the process that the 2.0 version went through to be accepted. Df: Thank Peter. I will like to conclude the call for dissent within this meeting. With this document, we will be able to initiate a ballot with some procedural deadlines and timeframes. If the ballot starts before the end of June, it will be good timing because it will be before the meeting in Copenaghen. If there are comments, it is clear that 2.0 is unmutuable, but if there are material comments we can take them home and apply them in 2.1. I have uploaded the zipped package in the svn. The package contains the xsd catalogue. We are sending them the whole package and it is up to them how to manage it. F: In terms of the document, it is accurately describing the document we approved, but in terms of formatting it is not always very clear. Df: There are two versions. There are example formatting was not well handled. F: Yes, the examples look bad. The problem is in the tree structure, in section 4.2. P: In ISO they can change some editorial problems, but I am not sure about those problems. F: The tree structure is not decodable, and I know the original tree structure. B: Is there an option to improve the format? Df: The calendar perspective is April. We can improve the structure by manually coding the examples and tree examples or going back to the original version. The first copy-paste in Ms Word was very good, but there were problems with the cross-referencing. F: The examples can go as they are, but the tree is the one that needs to be fixed. The line breaking should be also be fixed. Df: This is a production version. ISO will process it. F: yes, but the structure tree must be fixed. Df: can we approve the document given that we make sure that the tree structure is fixed? Is anybody volunteering for fixing it? P: I will change it. I will copy the html and then fix the links. Df: we can do now the call for dissent. We approve the document given that we make sure that the tree structure is fixed (in sections 4.2.1 and a1 in appendix) is fixed? Df: Peter, when you will have the new version ready I will commission it to the svn and notify the TC. Felix: when there is a vote, can I talk to other committees like the German one? Df: It is a good idea to reach national organisations. P: I can send you a list. But this is not like an OASIS vote, that you have to campaign. But if you want to know who to contact, I can put you in contact with. In ISO if they vote no they have to explain it. F: If we should try to time the ISO requests and try to respond them within a timeframe. Df: The material comments will be gathered during July, if we are lucking we will be in first public review. During that period we can make changes. F: That seems good. B: About the translation. P: It will be done by ISO members. They can ask us to review it. They have experience translating. We can answer translators’ questions. B: It would be good to have a look just to make sure the quality is acceptable. F: I expect ISO to have a good quality standard. Df: In my experience answering source questions could mitigate some of the target possible errors. F: It would be good to know the process. P: it will be translated in the translation section in Geneva. I think that the best way is that we offer assistance.
E. XLIFF 2.0 Support - Survey (Lucía) F. Action Item progress (as tracked in kavi AI tracker) Y: I have looked it, I have seen some question marks that you have left. Df: I will have a look at it. I have Y: The rest looks ok.
Phil: what is my AI? B: 0012 P: No progress on that, but it will be addressed soon.
B: I still have to finish mine, and once that, we will be almost be finished. F: I have not still finished mine (005). Y: I did some progress but I have not publish it yet, I will work on it.
P. * Missing elements in "Used in" entry in section "4.3.2.2 xml:space" (Yves) Df: Can you make an AI and I can fix it? B: Sure. G. New business requested by Soroush "updated the improved validation artefacts on the version control and would like to ask you to allocate few minutes for it in today meeting" S: I prefer to have more time to discuss it deeply, so I would like to talk in the next meeting. Df: We are preparing for the Dublin symposium. We are going to start the reviewing process. We should try to organise a FTF meeting that would be a good thing. We are having a meeting after this one. Y: The sister committee, people are working on the diagrams and examples. There is work going on, you can follow it on the mailing list. Df: the UML diagram provided by SDL facilitates the discussion. The first version was too XML driven, but the new version is more general. The model should be a baseline for other serialisations, so we should not include XML specifics. B: Any new business? DF: fragged prefixes were not registered. We should make a push for the registration process, for owners of extensions to register. B: An email would be a good thing to do? Df: Yes, that can be discussed by email before the next meeting. B: Meeting adjourned.
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. |
Attachment:
ical_42716.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:20160417T235110Z DTSTART;VALUE=DATE-TIME;TZID=America/New_York:20160405T110000 DTEND;VALUE=DATE-TIME;TZID=America/New_York:20160405T120000 SEQUENCE:1 SUMMARY:XLIFF TC Call LAST-MODIFIED:20160417T235110Z ORGANIZER:workgroup_mailer@lists.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. Approv e meeting minutes\, 15 March 2016\n https://lists.oasis- open.org/archives/xliff/201603/msg00025.html\n \n C. R evise scheduled for XLIFF 2.1 \n https://lists.oasis- open.org/archives/xliff/201504/msg00009.html\n https://l ists.oasis-open.org/archives/xliff/201504/msg00014.html\n\n D. Requesting progress of ISO submission of XLIFF 2.0\n Meeting took place. Update from Peter or David\n Notes are here:\n https://lists.oasis-open.org/archives/xliff/ 201603/msg00034.html\n\n E. XLIFF 2.0 Support - Survey (Luc í\;a)\n https://lists.oasis-open.org/archives/xlif f/201601/msg00003.html\n\n F. Action Item progress (as trac ked in kavi AI tracker)\n https://www.oasis-open.org/app s/org/workgroup/xliff/members/action_items.php\n \n G. New business requested by Soroush "\;updated the improve d validation artefacts on the version control and would like to ask you to allocate few minutes for it in today meeting& quot\;\n \n H. Call for dissent - Version Control\n https ://lists.oasis-open.org/archives/xliff/201603/msg00039.html\ n\nII XLIFF 2.1 (0:10 - 0:45)\n\n* indicates new topic\, not yet discussed\n\n A. Discuss whether can be allowed at all extension points (Ryan)\n https://lists.oasis-open.org/ archives/xliff/201506/msg00013.html\n B. Inline attributes and canCopy (Ryan)\n https://lists.oasis-open.org/archiv es/xliff/201506/msg00015.html\n C. NVDL for the core is upd ated (Soroush)\n https://lists.oasis-open.org/archives/x liff/201503/msg00009.html\n D. NVDL validation for XLIFF 2. 0 (Soroush)\n https://lists.oasis-open.org/archives/xlif f/201509/msg00002.html\n F. * CanReorder Validation error ( Ryan)\n https://lists.oasis-open.org/archives/xliff/2015 09/msg00031.html\n G. * ITS text analytics (David)\n H. In ternationalization and beyond related metadata for JSON - XL IFF perspective? (Felix)\n https://lists.oasis-open.org/ archives/xliff/201510/msg00006.html\n I. * Question on name space re-writing and ITS text analysis (Felix)\n https:/ /lists.oasis-open.org/archives/xliff/201511/msg00013.html\n J. * Proposal For Change Tracking in XLIFF 2.1 (Phil)\n https://lists.oasis-open.org/archives/xliff/201511/msg00024 .html\n K. * Inline codes in Change Tracking (Yves)\n h ttps://lists.oasis-open.org/archives/xliff/201512/msg00010.h tml\n L. * XLIFF and ITS mapping- Elements within text (Sor oush)\n https://lists.oasis-open.org/archives/xliff/2015 12/msg00033.html\n M. * XLIFF and ITS mapping-ID value (Sor oush)\n https://lists.oasis-open.org/archives/xliff/2015 12/msg00034.html\n N. [Progress on AI] Example with inline codes for MTC module test suite (Yves)\n https://lists.o asis-open.org/archives/xliff/201602/msg00001.html\n O. * Is sue with validating extensions (David)\n https://lists.o asis-open.org/archives/xliff/201603/msg00019.html\n P. * Mi ssing elements in "\;Used in"\; entry in section &qu ot\;4.3.2.2 xml:space"\; (Yves)\n https://lists.oasi s-open.org/archives/xliff/201603/msg00020.html\n\n\nIII Sub Committee Report (0:45 - 0:55)\n\nIV Current and New Busine ss (0:55 -\nGroup: OASIS XML Localisation Interchange File F ormat (XLIFF) TC\nCreator: Bryan Schnabel URL:https://www.oasis-open.org/apps/org/workgroup/xliff/event.php?event_id=42716 UID:https://www.oasis-open.org/apps/org/workgroup/xliff/event.php?event_id=42716 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]