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

 


Help: OASIS Mailing Lists Help | MarkMail Help

xliff-omos message

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


Subject: Modified: 4th Tuesday - Regular XLIFF OMOS TC telecenference


Submitter's message
meeting minutes added
-- Dr. David Filip
Event Title: 4th Tuesday - Regular XLIFF OMOS TC telecenference

Date: Tuesday, 24 January 2017, 05:00pm to 06:00pm WET
Location: https://www.oasis-open.org/apps/org/workgroup/xliff-omos/members/action_item.php?action_item_id=3822
Description

See the private action item for dial in details

https://www.oasis-open.org/apps/org/workgroup/xliff-omos/members/action_item.php?action_item_id=3822


This meeting counts towards voter eligibility.

Agenda

A. Admin

1- Roll call

total 7 voters

2- Minutes from Jan 10 https://www.oasis-open.org/apps/org/workgroup/xliff-omos/email/archives/201701/msg00002.html

 

B. Material

1- XLIFF OM

OASIS GitHub Repository URL: https://github.com/oasis-tcs/xliff-omos-om

Primary Maintainer: David Filip

Backup Maintainer: Felix Sasaki

https://wiki.oasis-open.org/xliff-omos/WorkingWithPapyrus

dF made some goo dprogress on the diagram.. let's check it out

 

2- JLIFF

Repository URL;: https://github.com/oasis-tcs/xliff-omos-jliff

Primary Maintainer: Robert van Engelen

Backup Maintainer:  Chase Tingley

- Chase added by Robin to make wiki editting possible

- Need to discuss strategy for modules and extensions

- Want to change expansion of JLIFF based on last time discussion .. should be a Fragment Format, rather than a file format..

 

3- TBX Mapping

Continue work on SVN: https://tools.oasis-open.org/version-control/browse/wsvn/xliff-omos/trunk/XLIFF-TBX/xliff-tbx-10.xml

Link to latest Editors' Draft of TBX mapping: https://tools.oasis-open.org/version-control/browse/wsvn/xliff-omos/trunk/XLIFF-TBX/xliff-tbx-v1.0.pdf

AI James and dF to schedule 1:1 editorial call for follow-up.  / PENDING

Nothing to report. Hope to schedule 1:1 meeting in next couple of weeks.

C. Other Topics

 

1- Date of next meeting?

  • Normally on Feb 14, 2017.
  • Robert will join but can only attend from 5:15 GMT or so, this conflict until April or so
  • dF: Happy to accommodate Robert, we can start JLIFF stuff after Robert joins each time..

 

2- Liaisons

dF/James: TBX Steering Committee / ISO TC37/SC3 => Expect next TBX IS version in late 2017

dF: XLIFF TC - XLIFF 2.1 CSPRD01 launched on 26th October, will end on 25th November

Review closed, significant changes under way:

https://issues.oasis-open.org/browse/XLIFF/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel

Do subscribe to the comment list https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=xliff

if you're not a member of the XLIFF TC you can only comment through the comment list (if you have a subscription)

You may follow the CTR discussion here https://issues.oasis-open.org/browse/XLIFF-4

- dF connected Chase with Klaus Fleischmann (collecting metadata) ?? status

CSPRD02 could launch after Feb 7

 

3- Promotion

dF will talk on XML Prague about the ITS module in XLIFF 2.1 in early February. Soroush to give an oXygen workshop

 

4- AOB

 

 


Minutes

A. Admin

1- Roll call

Attendance: Phil, Soroush, David, Alan, Chase, Robert, Felix

Quorum is reached by 4 (later +Chase, so 5) out of 7 voters

2- Minutes from the last meeting

dF: I move that the meeting minutes on https://www.oasis-open.org/apps/org/workgroup/xliff-omos/email/archives/201701/msg00002.html

are our official minutes of record for the 10th Jan meeting.

Chase: I second.

[no dissent]

dF: If no objections, approved.

 

B. Material

1- XLIFF OM

dF: I made some progress on the OM diagram. Some multiplicity issues have been solved since the last update. Its now complete in terms of elements, but not attributes.

dF: WRT UML, the language does not define any specific semantics for relations, there are in fact many different profiles for UML that make different conventions for the available relationships..

so if you have any issues on how the element relationships are represented currently, please notify the group via email or raise an issue on the om repo.

2- JLIFF

dF: We must concentrate on unit and sub-unit for JLIFF since we now have a clearer idea of how JIFF should work. As the file exchange is not the case for JSON, I wanted to propose a different expansion for the abbreviation. So it will make JLIFF JSON Localisation Fragment Format, not File Format as in XLIFF. It is just a simple administrative matter that can be done now easier. We also have the “fragment” keyword in our charter.

Chase: It seems like the case at the moment. But definitely it requires more thinking. 

dF: Since the JLIFF acronym has not been clarified anywhere on the TC pages it doesn't require any chnages to our templates, just meeting consensus, we can and will leave this decision for  the next meeting when people have had chance to think about it..

dF: Does anyone have something to add on JLIFF Repo?

Chase: I was assigned couple of action items since the last meeting and I added couple of pages on the wiki; default values for attributes in JLIFF and extensibility and modularity. The second is still in progress since it requires more thinking. The Metadata Module is the one that maps to JSON the most clearly (aside from namespace issue with must be solved later) and I started the wiki from it.

dF: I know UML can handle namespaces and namespaces are not an XML specificsc, but not sure about JSON.

Robert: There is nothing acceptable and in-use for JSON at this point and for the current version (there are some proposals, but not expected earlier than v. 5 of JSON schema).

dF: We will need to find a way for identifiers and namespaces later which would be also acceptable for the industry.

Robert: There are some conventions and notations, like the one from Google on JSON schema, that we can follow. But even if we come up with new solutions, we must document them completely. 

Chase: We also might face some issues with the scope of uniqueness for the identifiers.

dF: This could be solved if we focus on ‘unit’ only, which is the scope for many ids. It was also mentioned by Felix that an issue might also appear since there is no IDREF available in JSON schema, this is vital for the purpose of our work.

Robert: We have added id and ref to JLIFF schema, but it is just our convention and could not be enforced by validators as with XML. Again, it must be mentioned in our documentation.

dF: XLIFF identifiers do not follow the generic XML ID behaviour, so there should not be an issue with defining and documenting the required convention. I will add more attributes to the diagram by the next meeting, as well as completing the extensibility. We actually could set the mda module/mechanims (as mentioned by Chase) as the generic extensibility mechanism for JLIFF and recreate other module features reusing the mda key, value pair mechanism.

Chase: Yes, we could use it as the container for any module data

 

dF: Our next meeting will be on 14th Feb. Thanks everybody for contributions, the meeting is now adjourned.



Owner: Dr. David Filip
Group: OASIS XLIFF Object Model and Other Serializations (XLIFF OMOS) TC
Sharing: This event is shared with the OASIS Open (General Membership), and General Public groups. Public Event Link
  • Learn more about subscribing here.
  • View the OASIS XLIFF Object Model and Other Serializations (XLIFF OMOS) TC calendar here.
  • You may receive future notifications with updates to this event. Update the event on your calendar by accepting the changes.

Attachment: ical_41668.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:Europe/Lisbon
BEGIN:STANDARD
DTSTART:20001029T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:WET
TZOFFSETFROM:+0100
TZOFFSETTO:+0000
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T010000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:WEST
TZOFFSETFROM:+0000
TZOFFSETTO:+0100
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
STATUS:CONFIRMED
TRANSP:OPAQUE
DTSTAMP:20170213T121050Z
DTSTART;VALUE=DATE-TIME;TZID=Europe/Lisbon:20170124T170000
DTEND;VALUE=DATE-TIME;TZID=Europe/Lisbon:20170124T180000
SEQUENCE:9
SUMMARY:4th Tuesday - Regular XLIFF OMOS TC telecenference
LOCATION:https://www.oasis-open.org/apps/org/workgroup/xliff-omos/mem
 bers/action_item.php?action_item_id=3822
LAST-MODIFIED:20170213T121050Z
ORGANIZER:workgroup_mailer@lists.oasis-open.org
DESCRIPTION:See the private action item for dial in details\n\nhttps://w
 ww.oasis-open.org/apps/org/workgroup/xliff-omos/members/acti
 on_item.php?action_item_id=3822\n\nAgenda: A. Admin\n\n1- Ro
 ll call\n\ntotal 7 voters\n\n2- Minutes from Jan 10 https://
 www.oasis-open.org/apps/org/workgroup/xliff-omos/email/archi
 ves/201701/msg00002.html\n\n \n\nB. Material\n\n1- XLIFF OM\
 n\nOASIS GitHub Repository URL: https://github.com/oasis-tcs
 /xliff-omos-om\n\nPrimary Maintainer: David Filip\n\nBackup 
 Maintainer: Felix Sasaki\n\nhttps://wiki.oasis-open.org/xlif
 f-omos/WorkingWithPapyrus\n\ndF made some goo dprogress on t
 he diagram.. let&#39\;s check it out\n\n \n\n2- JLIFF\n\nRep
 ository URL\;: https://github.com/oasis-tcs/xliff-omos-jliff
 \n\nPrimary Maintainer: Robert van Engelen\n\nBackup Maintai
 ner:  Chase Tingley\n\n- Chase added by Robin to make wiki e
 ditting possible\n\n- Need to discuss strategy for modules a
 nd extensions\n\n- Want to change expansion of JLIFF based o
 n last time discussion .. should be a Fragment Format\, rath
 er than a file format..\n\n \n\n3- TBX Mapping\n\nContinue w
 ork on SVN: https://tools.oasis-open.org/version-control/bro
 wse/wsvn/xliff-omos/trunk/XLIFF-TBX/xliff-tbx-10.xml\n\nLink
  to latest Editors&#39\; Draft of TBX mapping: https://tools
 .oasis-open.org/version-control/browse/wsvn/xliff-omos/trunk
 /XLIFF-TBX/xliff-tbx-v1.0.pdf\n\nAI James and dF to schedule
  1:1 editorial call for follow-up.  / PENDING\n\nNothing to 
 report. Hope to schedule 1:1 meeting in next couple of weeks
 .\n\nC. Other Topics\n\n \n\n1- Date of next meeting?\n\n\n	
 Normally on Feb 14\, 2017.\n	Robert will join but can only a
 ttend from 5:15 GMT or so\, this conflict until April or so\
 n	dF: Happy to accommodate Robert\, we can start JLIFF stuff
  after Robert joins each time..\n\n\n \n\n2- Liaisons\n\ndF/
 James: TBX Steering Committee / ISO TC37/SC3 =&gt\; Expect n
 ext TBX IS version in late 2017\n\ndF: XLIFF TC - XLIFF 2.1 
 CSPRD01 launched on 26th October\, will end on 25th November
 \n\nReview closed\, significant changes under way:\n\nhttps:
 //issues.oasis-open.org/browse/XLIFF/?selectedTab=com.atlass
 ian.jira.jira-projects-plugin:summary-panel\n\nDo subscribe 
 to the comment list https://www.oasis-open.org/committees/co
 mments/index.php?wg_abbrev=xliff\n\nif you&#39\;re not a mem
 ber of the XLIFF TC you can only comment through the comment
  list (if you have a subscription)\n\nYou may follow the CTR
  discussion here https://issues.oasis-open.org/browse/XLIFF-
 4\n\n- dF connected Chase with Klaus Fleischmann (collecting
  metadata) ?? status\n\nCSPRD02 could launch after Feb 7\n\n
  \n\n3- Promotion\n\ndF will talk on XML Prague about the IT
 S module in XLIFF 2.1 in early February. Soroush to give an 
 oXygen workshop\n\n \n\n4- AOB\n\n \n\n \nGroup: OASIS XLIFF
  Object Model and Other Serializations (XLIFF OMOS) TC\nCrea
 tor: Dr. David Filip
URL:https://www.oasis-open.org/apps/org/workgroup/xliff-omos/event.php?event_id=41668
UID:https://www.oasis-open.org/apps/org/workgroup/xliff-omos/event.php?event_id=41668
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]