Regular monthly LEXIDMA TC meeting (Conference Call) | ||
Name | Regular monthly LEXIDMA TC meeting (Conference Call) | |
Time | Monday, 17 May 2021, 01:30pm to 03:00pm WEST
(Monday, 17 May 2021, 12:30pm to 02:00pm UTC) |
|
Description | Find connection link within this action item https://www.oasis-open.org/apps/org/workgroup/lexidma/members/action_item.php?action_item_id=3939 |
|
Minutes | 1. Admin Attendance: Tomaž, dF, Iztok, John, Michal, Adam, Carole Quorum: 6/7 voters present Adam became a voting member at the end of the meeting Minutes from 19th April were not available for approval. Action on Tomaž to publish the minutes from 19th April 2. Material
Michal's proposal
was discussed and compared with objectives set in LEXIDMA TC Charter https://www.oasis-open.org/committees/lexidma/charter.php agreed design principles https://github.com/oasis-tcs/lexidma/wiki/Fused-revised-design-principles/e0c2f377f58e2e8274806baf31c47bd9608709a1 in particular
and some previoulsy agreed technical solutions https://github.com/oasis-tcs/lexidma/wiki/Documenting-current-consensus-on-possible-technical-solutions/2f879f094e5f904246edd27bc350ecdc8b19b367 in particular Multiword expressiions, homogrpahs etc. The consenus of LEXIDMA TC members was that the proposed model is too flexible and not prescriptive or modular enough to fulfil agreed business objectives and design principles. ELEXIS gathered a large group of industry and academic observers, so that it can design DMLex as a simple, modular, and easily implementable prescriptive standard that will not be able to express all histrically used structures but will instead drive a widely interoperable best practice based solution. Despite being too flexible for the intended DMLex Standard, the curernt proposal seems useful as a metamodel. The model Michal previously propsed https://github.com/oasis-tcs/lexidma/pull/3 seems as a more suitable instance of the same metamodel. [the PR was not merged becuase of incompatibilty with the OASIS template rather than because of its technical merits] Even as a metamodel the currently discussed proposal shouldn't use the term "segment" for the "property bag" that clusters available expressions for lexicographic use in the proposed metamodel. Segment is a term widely used in related industry and standardization areas such as the localization and translation industry and Unicode related standards such as UAX #29 https://unicode.org/reports/tr29/
3. Closing Admin
|
|
Agenda | 1. Administrative
2. Material
3. Closing Admin
|
|
Submitter | Dr. David Filip | |
Group | OASIS Lexicographic Infrastructure Data Model and API (LEXIDMA) TC | |
Access | This event is visible to OASIS Lexicographic Infrastructure Data Model and API (LEXIDMA) TC and shared with
|