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
==========
Agenda:
1. Administrative
[need a pool of scribe volunteers to rotate the duty]
2. Material
discuss normtaive keywords style
- DMLex WD Technical discussion
Result of clarification: Link exists at Entry level, has source and target selector, also an attribute for type of 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"
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
Call for a liaison rep
3. Closing Admin
- Recap of agreed actions
- AOB
- Adjourn [no later than 1400 UTC]
==========
Minutes:
==========
Attendance:
| Meeting Statistics |
| Quorum rule |
51% of voting members
|
| Achieved quorum |
yes |
| Individual Attendance |
Contributing Members: 9 of 14 (64%)
Voting Members: 7 of 7 (100%) (used for quorum calculation)
|
| Company Attendance |
Contributing Companies: 6 of 9 (66%)
Voting Companies: 5 of 5 (100%)
|