OASIS Open

Find connection link within this action item

https://www.oasis-open.org/apps/org/workgroup/lexidma/members/action_item.php?action_item_id=3939

1. Administrative

• roll call

Carole, Mark, John, Simon, Iztok, Ilan, Miloš, dF

• appoint scribe

dF

• approve minutes from previous meeting
  https://markmail.org/message/n32su4wiu6ktwpfh

Simon seconded dF move, no objections​​

2. Material

• DMLex Working Draft format Docbook template set up pending https://github.com/oasis-tcs/lexidma

discuss normtaive keywords style

skipped

• DMLex WD Technical discussion
  • Based on technical contributions received by 11th May 2020
    • None received
  • Continue discussion of design principles and data model diagrams
    Miloš: https://www.oasis-open.org/committees/download.php/66840/LEXIDMA_ER_version1.pdf
  • John: https://github.com/oasis-tcs/lexidma/wiki/Data-Model-based-on-OntoLex-TEI-Lex0
  • Design principles: https://github.com/oasis-tcs/lexidma/wiki vs https://www.w3.org/community/ontolex/wiki/Goals_and_Scope_of_Ontology-Lexica_Community_Group#General_Requirements_on_the_Model

John's and Miloš's diagrams were discussed in parallel

Miloš spoke against recursibity in data models.

Short Link object intro and discussion:

Result of clarification: Link exists at Entry level, has source and target selector, also an attribute for type of relationship

Detailed discussion about POS, inflectional form and their relationship:

a possible @POS data model, instead of free form as proposed by Miloš

lex:NMTOKEN

[authority]:NMTOKEN

possible authority prefix examples:

[universal part of speech tagging]

upos:

clarin:

lemon:

[how to relate (inflectional) forms to POS?]

Morphology object with possible value pairs

@POS="[authority]:NMTOKEN" 

@formsLink="[formsURI]"

example: @relationshipType="imperative"

dF summarized that John's and Miloš's diagrams serve as far points that need to be brought together before spec writing can start

the situation is really a triangle with Lemon<>Lex-0 zero being more fine grained, Miloba and Lemon being more prescriptive in allowed relationships -: better for industry interoperability

• LEXIDMA TC liaisons and appointement of reps
  • TEI Lex-0 appointement of rep pending

Ilan discussed shortly. Siomon confirmed that neither Laurent nor Toma are interested in LEXIDMA membership. Simon suggested that Iztok could serve as our liaison towards Lex-0. Iztok hasn't volunteered, yet..

3. Closing Admin

• Recap of agreed actions
  • John to provide version of Lex-0<>Lemon diagram that would reflect the Lemon restrictive set of relationships
  • Miloš to amend his digram based on today's discussion
  • All to continue discussion on mailing list and GitHub wiki
• AOB
• Adjourn [no later than 1400 UTC]

This preliminary agenda will be finalized by 11th May 2020.

1. Administrative

• roll call
• appoint scribe
• approve minutes from previous meeting
  https://markmail.org/message/n32su4wiu6ktwpfh

​​2. Material

• DMLex Working Draft format Docbook template set up pending https://github.com/oasis-tcs/lexidma

discuss normtaive keywords style

• DMLex WD Technical discussion
  • Based on technical contributions received by 11th May 2020
  • Continue discussion of design principles and data model diagrams
    Miloš: https://www.oasis-open.org/committees/download.php/66840/LEXIDMA_ER_version1.pdf
  • John: https://github.com/oasis-tcs/lexidma/wiki/Data-Model-based-on-OntoLex-TEI-Lex0
  • Design principles: https://github.com/oasis-tcs/lexidma/wiki vs https://www.w3.org/community/ontolex/wiki/Goals_and_Scope_of_Ontology-Lexica_Community_Group#General_Requirements_on_the_Model
• LEXIDMA TC liaisons and appointement of reps
  • TEI Lex-0 appointement of rep pending

3. Closing Admin

• Recap of agreed actions
• AOB
• Adjourn [no later than 1400 UTC]

• OASIS Open (General Membership)
• General Public