[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Modified: XLIFF TC Meeting
|
Event Title: XLIFF TC Meeting Date: Tuesday, 02 February 2021, 11:00am to 12:00pm EST Description Use the following link to join the meeting: https://teams.microsoft.com/l/meetup-join/19%3ameeting_Y2QxNzNmNjctODczMy00NDU0LWJhZDAtZWVhMTU5ZjIyYTE1%40thread.v2/0?context=%7b%22Tid%22%3a%22f03dc4ba-c74a-4694-a250-85f4c45b5abb%22%2c%22Oid%22%3a%22b789449a-565d-4176-9fb5-185437e758dc%22%7d This meeting counts towards voter eligibility. Agenda Provisional Agenda II. Where do we go next? A. Charter renewal. III. Subcommittee and sister TC reports Minutes Attendance: Bryan, Rodolfo, DavidF, Lucía. We have quorum. I. Administration B: I second. L: Meeting minutes approved.
II. Where do we go next? A. Charter renewal. L: I have prepared a new draft of the charter to comply with the new OASIS template for the charters. I have discussed it with Rodolfo. [Rodolfo shares the screen and shows the document]. As you can see in most of the sections, there are any changes or they are minor ones. The main changes are in the section “Business Benefits” and “Scope”. In “Business Benefits”, I have included the section that we had on the latest white paper. In the scope, I have reduced the wording to comply with the new template. The historical section will be deleted, but we plan to include it in the TC webpage with the new update. R: I have just some comments on the section that covers the items that we will produce, as if we are not working on new modules it can mean that we are still working on 2.1. Df: I agree with the proposed changes. We could include the information about the ISO. R: I think that it would be wise not to do it if we are not sure that it will happen. Df: Ok, that is ok, we can leave it out. Btw, we need to provide a new version to ISO by 2022, we can discuss this on another time. B: I agree with the changes and I think it is a good idea to keep the historical information in the webpage. R: For the ballot, we need to have this document stored in a specific location. L: Ok, I will prepare the document and send it to the mailing list. R: Ok, after that I can prepare the ballot.
R: In the last meeting, Yoshito suggested this idea to have an online validation service that I have prepared, it is available athttps://dev.maxprograms.com/Validation/ . [Rodolfo share his screen and demonstrates his tool]. As you can see the code is open source and available in github. I have also prepared the schematron but it is not implemented in this version, what do you think about having this other validation tool? It shows sometimes different results. Df: I think that it would be good to have both, it will depend on the final user and their needs. But it can be implemented as an advance user. R: Should we put more information in the main page? I am not keeping the files, they are deleted after validation. Df: It would be good to mention that. About the validation, as you are using official validation artefacts (schema, dtd) it would be good to have information mentioning them. R: Last week, Yoshito noticed that my tool was marking a source without content as an error. I have changed the tool to accept it as it can be done if we have a look at the spec, but what should we do in the future? Will we consider this acceptable? Df: I think we can continue to allow it but we can add an informative note. We do not know how the developers might need to use it, maybe they need to have a source without content for a specific reason. Df: Do you plan to run it as a public service? R: That was suggested by Yoshito. He also mentioned that somebody needs to maintain it, I can do it. Df: It would be good to have a public service for validation. L: One of the other topics that we discussed in the previous meeting was to keep a track of the errors, as this can give us useful information about the main errors that are found in XLIFF files. R: I do not keep the files, but I can keep the generic error messages. The only problem is that if somebody sends the same file 20 times we will get the same error message 20 times. So, I do not know if we should publish these results. Df: Well, we can just have them for the TC, they can be valuable for us. Can you know if a file has been submitted twice? R: Not without storing them and I do not want to do that. Df: Can we know how broke a file is? R: Not really, we will just get the first error that the tool will find. R: I can have the tool ready by next meeting and we could discuss what we will do with it. B: Lucía, I think we could move this topic for the promotion and liaison subcommittee. DF: as we are the same members, I do not know if it makes sense to have a separate meeting for the subcommittee. R: we need to renew the charters of the sc. L: I can prepare the new charter for the PL subcommittee.
L : We need to update several aspects of the webpage. R: We need to update he liaison information. Df: I can send you the updated information for that section. L: We also need to update the technical information. R: The charter will also be updated.
III. Subcommittee and sister TC reports
L: Meeting adjourned. Owner: Dr. Lucía Morado Vázquez Group: OASIS XML Localisation Interchange File Format (XLIFF) TC Sharing: This event is not shared to any other groups. |
Attachment:
ical_51465.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:20210203T103212Z DTSTART;VALUE=DATE-TIME;TZID=America/New_York:20210202T110000 DTEND;VALUE=DATE-TIME;TZID=America/New_York:20210202T120000 SEQUENCE:1 SUMMARY:XLIFF TC Meeting LAST-MODIFIED:20210203T103212Z ORGANIZER:workgroup_mailer@lists.oasis-open.org ATTENDEE;CUTYPE=GROUP:MAILTO:xliff@lists.oasis-open.org DESCRIPTION:Use the following link to join the meeting:\n\nhttps://teams .microsoft.com/l/meetup-join/19%3ameeting_Y2QxNzNmNjctODczMy 00NDU0LWJhZDAtZWVhMTU5ZjIyYTE1%40thread.v2/0?context=%7b%22T id%22%3a%22f03dc4ba-c74a-4694-a250-85f4c45b5abb%22%2c%22Oid% 22%3a%22b789449a-565d-4176-9fb5-185437e758dc%22%7d\n\nAgenda : Provisional Agenda\nI. Administration\n Approve 16 Decembe r meeting minutes\nhttps://www.oasis-open.org/apps/org/workg roup/xliff/email/archives/202007/msg00005.html\n\nII. Where do we go next?\n\n A. Charter renewal.\n B. Online Validatio n Tool. Feedback\, next steps. https://lists.oasis-open.org/ archives/xliff/202101/msg00002.html\n C. OASIS web site upda tes - Rodolfo https://lists.oasis-open.org/archives/xliff/20 2011/msg00000.html\n D. Linking to - Rodolfo https://lists.o asis-open.org/archives/xliff/202011/msg00001.html \n\nIII. S ubcommittee and sister TC reports\n A. Promotion and Liaison SC\n B. XOMOS - Sister TC\nIV. New business\nGroup: OASIS X ML Localisation Interchange File Format (XLIFF) TC\nCreator: Dr. LucíMorado Váuez URL:https://www.oasis-open.org/apps/org/workgroup/xliff/event.php?event_id=51465 UID:https://www.oasis-open.org/apps/org/workgroup/xliff/event.php?event_id=51465 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]