See also: IRC log
<fsasaki> hi labra, all - . How many people do we expect today?
<labra> I am not sure...
<labra> Probably not many
<labra> I am trying to get access to the call using skype
<fsasaki> do you think a bridge for six people would be sufficient
<labra> probably so
<fsasaki> ?
<fsasaki> . Please dial in with passcode 26632
<fsasaki> regrests+ dom, john
<fsasaki> jorge: started with naming, talked about descriptive URIs
<fsasaki> jorge going through http://www.w3.org/community/bpmlod/wiki/Best_practises_-_previous_notes
<mihael> hi all, sorry, I still don't know how to dial in
<mihael> yes felix, thank you, just took a while
<fsasaki> ok
jose: changed local name by "Internationalized paths only"
(proposal)
<fsasaki> +1 to internationalized path
+1, clarifying that it might include fragment
<fsasaki> agree with jorge
internazionalised path. Pros:
- less security risks
- path readable for one languages
Cons:
- Unreadable for speakers of other languages
<fsasaki> jose: dbpedia is a good example of that pattern
<chaals> [example: namespace is http://w3.org/html so full name is http://w3.org/htmldiv]
<fsasaki> [apologies in advance, I have to leave in 5 min]
<chaals> [The problem case is where the namespace does not end in / or #, because it can be difficult to see where the term is]
<chaals> [On the plus side, copy-paste works fine even if you can't understand the text being copied]
<labra> Can you hear Chaals?
<labra> I cannot
with difficulties
<chaals> The implication is that you should define prefixes that end with / or # ...
<fsasaki> [sorry, I have to go, bye]
<dvilasuero> *everyone having trouble hearing here :(
bye and thanks felix
<chaals> (already a common practice, but not universal and not technically required)
<labra> bye and thanks...
we can include chaals' comment when formulate the best practise
other pattern: Include Language in URIs
Pros:
- practical reasons: divide in different datasets, as in DBpedia
Cons:
- where do we put it? (beginning, end, ..)
- dialects
<chaals> [what is the code for valenciano?]
chaals: description of languages should be in the description of the resource not in the uri
dani: "es" in dbpedia uri identifies not the language but the source
<labra> hy-Latin-IT-arevela
chaals: using usi to identify language is a BAD practice
<chaals> [Don't rely on something in the URI to convey the language being used]
<dvilasuero> this is an example of a Lexicon in English hosted by the initiative linguistic.linkeddata.es, which is in fact linked to other lexica in many languages http://linguistic.linkeddata.es/terminesp/lexiconEN
Which pattern is better and for which requirements?
descriptive: for English, latin alphabet
jose: Add a column with this information
Dani: study IDN more
... deeper discusion needed
before reaching conclusions
<chaals> [I have the email address chaals@яндекс.рф and it works fine]
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) Succeeded: s/zakim, room for 6// Succeeded: s/dbpedia/jose: dbpedia/ Succeeded: s/we need to use an adhoc zakim bridge// Succeeded: s/ok, we can use above bridge// Succeeded: s/languages in the/languages should be in the/ No ScribeNick specified. Guessing ScribeNick: jorge_gracia Inferring Scribes: jorge_gracia Default Present: fsasaki, +34.66.051.aaaa, jose, [IPcaller], vilasuero, chaals, +3539149aabb, mihael Present: vilasuero fsasaki jose jorge chaals mihael Regrets: gordon dom john Agenda: http://lists.w3.org/Archives/Public/public-bpmlod/2013Oct/0001.html Got date from IRC log name: 18 Oct 2013 Guessing minutes URL: http://www.w3.org/2013/10/18-bpmlod-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]