See also: IRC log
<scribe> scribe: DaveL
http://www.w3.org/community/bpmlod/track/products
jorge: a couple of products
identified
... best practices is one, whihc is under ongoing
development
... the other is the best practice guidelines
daveL: might be helpful to have products at the level of guidelines
jorge: have actually allocated issue to guidelines
http://www.w3.org/community/bpmlod/track/issues/raised
daveL: agrees
jorge;
jorge: poeple can create their own issues as they greate new guides or other issues that arise for discussion
jorge: p2.1, p2.2, p2.3 - reviews
discussion from previous call
... discussion on p2.2 needing a exmaple of bad practice
... next step is to document concensus in a report on the
patterns
... next is patter 2.4, to be explained by jose
<jgracia> P2.4 Divide longer descriptions
jose: for separating out a longer name into parts, since parts may be multilingual
john: there's no two way mapping between the two however as suggest
jose: its not clear always how to divide that, it depends on the context
jorge: this seems to move to
conceptualisation, rather than just the multilingual nature of
text
... so is this different from 2.3/
jose: yes this seems
distinct
... since long descriptions are sometime abused.
john: its a good pattern, but it
should be in addition to providing longer descriptions
... that means these labels should be in addition as annotation
to the string.
Davel: could simply annotate
string using NIF as best practice
... also, if this is more about people name, Gary Lefman has
doen some work on that that could be included
Jorge: suggest adapt pattern to
specify that this is in addition to long description
... and also ask Gary to look at providing more info on person
names
Gary; agrees
Jose; agrees to reprhase pattern description
<scribe> ACTION: Gary to provide info on person name models [recorded in http://www.w3.org/2014/06/19-bpmlod-minutes.html#action01]
<trackbot> Created ACTION-2 - Provide info on person name models [on Gary Lefman - due 2014-06-26].
<scribe> ACTION: jose to reword pattern 2.4 to reflect that it is additive rather than an alternate to long descriptions [recorded in http://www.w3.org/2014/06/19-bpmlod-minutes.html#action02]
<trackbot> Error finding 'jose'. You can review and register nicknames at <http://www.w3.org/community/bpmlod/track/users>.
<GaryLefman> W3C login ID: lefmang
<scribe> ACTION: Jose to reword pattern 2.4 to reflect that it is additive rather than an alternate to long descriptions [recorded in http://www.w3.org/2014/06/19-bpmlod-minutes.html#action03]
<trackbot> Error finding 'Jose'. You can review and register nicknames at <http://www.w3.org/community/bpmlod/track/users>.
jorge: moving to pattern
2.5
... jose; an exmaple provided by john
http://www.weso.es/MLODPatterns/Lexical_information.html
jose: trying to explain lexical information
daveL: could link long description to example from ontolex using NIF
<jgracia> (this is p2.4 though)
john: can use subterm propery to link a bag of lex term to a longer string
<jgracia> nice to see an example, looks complicated
action; John to provide example of linking long description to lexical entries, using both NIF and subterm
<scribe> ACTION: John to provide example of linking long description to lexical entries, using both NIF and subterm [recorded in http://www.w3.org/2014/06/19-bpmlod-minutes.html#action04]
<trackbot> Created ACTION-3 - Provide example of linking long description to lexical entries, using both nif and subterm [on John McCrae - due 2014-06-26].
<scribe> ACTION: labra to reword pattern 2.4 to reflect that it is additive rather than an alternate to long descriptions [recorded in http://www.w3.org/2014/06/19-bpmlod-minutes.html#action05]
jorge: also it would be useful to
identify condition under which it make sense to follow this
pattern and enrich a long description with links to lexical
entries
... asks john
<jgracia> well, not only about enrich longer descriptions but, enriching lexical info of ontology entities in general. under which conditions?
tiziona: for pattern 2.5 NIF
could be used
... but use case isn't clear
jose; use case is perhaps to help localizing the description
scribe: but we need some clearly use cases for helping with the multilingualism of such long descriptions
jose, just added exmaple
http://www.weso.es/MLODPatterns/Structured_literals.html
scribe: so perhaps this can feed processing of content in XML
<jgracia> P2.6: structured literals
<jgracia> dave: related to the use case of terminology localisation
daveL: make link to terminology management use cases, where multiword unit are the norm
<scribe> ACTION: dlewis6 provide examples from terminology domain with multiword unit [recorded in http://www.w3.org/2014/06/19-bpmlod-minutes.html#action06]
<trackbot> Created ACTION-5 - Provide examples from terminology domain with multiword unit [on David Lewis - due 2014-06-26].
daveL: https://www.w3.org/community/bpmlod/wiki/Draft_Guidelines_on_Bitext_as_Linked_Data
<jgracia> Dave, we cannot hear you
DaveL: happy to get feedback on these
jorge: run out of time to get
feedback on reports, babel net is most advanced.
... but we will pick that up at the next call
... we can convert these to W3C working docs the template on
the github
... will do a guided tour on the next call
tiziano: can convert to template for next call
jorge; jose can help also, just send him an email to be added to github
This is scribe.perl Revision: 1.138 of Date: 2013-04-25 13:59:11 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) No ScribeNick specified. Guessing ScribeNick: daveL_ Found Scribe: DaveL Present: Gary Chaals Dave Jorge Jose Tomás Tiziano Agenda: https://www.w3.org/community/bpmlod/wiki/Teleconference,_19/06/2014#Agenda Got date from IRC log name: 19 Jun 2014 Guessing minutes URL: http://www.w3.org/2014/06/19-bpmlod-minutes.html People with action items: dlewis6 gary john jose labra[End of scribe.perl diagnostic output]