** apologies for cross-posting **
==== Second Call for Tutorials ====
http://2014.eswc-conferences.org/important-dates/call-tutorials
ESWC 2014 invites tutorials that address the interests of its varied audience: people new to the Semantic Web, Semantic Web researchers and practitioners that wish to learn new technologies, users of Semantic Web technologies, and representatives of government and funding agencies as well as potential private investors in Semantic Web technologies. We welcome submissions of tutorial proposals on all major topics related to semantic technologies.
We especially solicit proposals for tutorials of the following types:
- Tutorials with a coherent theme providing an introduction to new semantic technologies and trends.
- Tutorials describing the application of semantic technologies in specific domains (e.g., life-sciences, e-government, e-commerce, cultural heritage, etc.).
- Tutorials presenting techniques from other research fields that are of relevance for Semantic Web research especially in relationship to the tracks of the conference (e.g., techniques from social science, database techniques, NLP techniques etc.).
Tutorials can be half a day or a full day.
We advise having more than one presenter and no more than three, preferably from different institutions, bringing different perspectives to the tutorial topic.
Tutorials may focus entirely on theoretical aspects; however, we encourage organisers to incorporate hands-on sessions where appropriate. The tutorials should reach a good balance between the topic coverage and its relevance to the community.
Timeline for Tutorials
-----------
Proposals due: Nov 22, 2013 - 23:59 Hawaii Time
Notification of acceptance: Dec 6, 2013 - 23:59 Hawaii Time
Tutorial Web site due: Dec 16, 2013 - 23:59 Hawaii Time
Camera-ready material due: Apr 25, 2014 - 23:59 Hawaii Time
Tutorial days: May 25 and May 26, 2014
Responsibilities
-----------
Organizers of accepted tutorials are responsible for preparing and maintaining a Web site that describes the tutorial and includes all relevant information. Organizers are also responsible for submitting the material for attendees (slide sets, additional teaching material, software installation and usage guides for practical hands-on sessions, etc.) to the Tutorial Chair. The ESWC 2014 Organizing Committee is responsible for providing publicity for the tutorials as part of the conference publicity activities, and on-site logistical support to the organizers and attendees. Tutorial attendees must pay the ESWC 2014 workshop registration fee, as well as the conference registration fee.
General Information
-----------
Each tutorial will have one reduced registration fee (pre-conference days registration will be free i.e. one of the chairs will only have to pay the main conference fees).
In the interest of the overall quality of the conference, the Tutorial Chair reserves the right to merge tutorials and/or adjust the scope thereof in case a mimimum number of registrations is not reached by the early registration deadline.
Submission details
-----------
Tutorial proposals should not exceed 5 pages, using an 11 pt font for the body of the text of the proposal and should contain the following information:
- Abstract (200 words maximum, for inclusion on the ESWC 2014 website).
- Tutorial description: More specifically, it should specify the objectives of the tutorial and relevance to ESWC 2014, include enough details on the scope of the material to be covered and the depth to which it will be covered and specify the intended audience and any prerequisite knowledge. Appropriate references to the material to be covered by the tutorial must be included.
- Tutorial length. The tutorial can be full or half day (if the tutorial can be either length, please be sure to identify which material is included for each length).
- Specify other venues to which the tutorial or part thereof has or will be presented, in addition to explaining how the current tutorial differs from the other editions. Links to the slides of those tutorial editions should be included in the proposal.
- Brief professional biography of the presenter(s) indicating previous training and speaking experience (such as teaching and tutorial presentation).
Each proposal will be reviewed by the members of the tutorial programme committee, and ranked based on the overall quality of the proposal and the tutorial's fit to the conference. Their recommendation will determine the final decision on the acceptance/rejection of each proposal.
Submission
-----------
Submission will be through the Easychair system (please note that it is the same site to submit workshops and tutorials) https://www.easychair.org/conferences/?conf=eswc2014workshops-tutorials
Tutorials Chair
Nathalie Aussenac-Gilles (IRIT-CNRS, Toulouse, Fr)
email: aussenac(a)irit.fr
Hey everyone!
It's been a busy week. Here's your chance to catch up:
https://meta.wikimedia.org/wiki/Wikidata/Status_updates/2013_11_08
Cheers
Lydia
--
Lydia Pintscher - http://about.me/lydia.pintscher
Product Manager for Wikidata
Wikimedia Deutschland e.V.
Obentrautstr. 72
10963 Berlin
www.wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das
Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.
Actually the problem isn't that you can only have one link from a
wikisource work from a wikidata item. We have separate wikidata items
for each edition of a work (because these have different metadata) so
multiple editions of the same work on a wikisource link to different
wikidata items.
This creates a different problem. Each language edition of a work is a
different edition so it links to a different wikidata item which has
sitelinks only to that translation of the work. This means you can't
use sitelinks to link to translations of a work on other wikisources.
Does this mean wikidata sitelinks are useless for wikisource?
filceolaire
Hello,
we’d like to work on Lua bindings for Wikidata. I have set up a page to gather ideas and suggestions for what people want to see: https://www.wikidata.org/wiki/Wikidata:Lua_enhancements
Your contributions would make me very, very happy.
Cheers,
Jens
--
Jens Ohlig
Software developer
Wikimedia Deutschland e.V.
Obentrautstraße 72
10963 Berlin
Telefon 030 - 219 158 26-0
www.wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.
Hello,
I submitted bug 56763[1] just now, then realized that this is a part of a
larger issue: what is {{#property: }} expected to output.
Theoretically, there could be two extreme answers: raw data as a string, or
whatever wikitext which could be rendered as what *readers* love best.
I guess the second answer is the goal, because of ValueFormatter,
SnakFormatter::FORMAT_WIKI and $wgContLang->listToText() on final output in
our code, but sadly this is never explicitly defined anywhere, including
MW.org documentations[2] and development notes[3].
With this goal, I imagine the output for each datatype should be:
* Item: WikiLink to the linked article, or maybe the WikibaseRepo item page
when there's not such an article, with label as link text
* Commons media: ImageLink to the specified media file (size and other
params TBD)
* String: Wikitext-escaped form of the string data
* Time / Globe coordinate: See bug 48937[4] and bug 49387[5]
* URL: ExternalLink to the specified URL, see bug 56763[1]
However due to lack of the specification and the current behaviors of
{{#property: }} which is a mix of raw data and fully-constructed wikitext,
template writers have already invented various usages:
* [[{{#property:item-property}}]]
* [[File:{{#property:commons-media-property}}|thumb]]
* [{{#property:url-property}}
{{url-protocol-stripper|{{#property:url-property}}}}]
* {{#ifeq:{{#property:commons-media-property}}|A.png|B|C}}
and obviously work towards the goal described above breaks them (of course
what they want is still doable with Lua), and less obviously, they're
already broken sometimes when multiple statements exist, which are imploded
using $wgContLang->listToText().
Is there any plan here, and what's the real goal of {{#property: }} ?
[1] https://bugzilla.wikimedia.org/show_bug.cgi?id=56763
[2] https://www.mediawiki.org/wiki/Wikibase_Client#Data_transclusion
[3]
https://meta.wikimedia.org/wiki/Wikidata/Notes/Inclusion_syntax#Accessing_I…
[4] https://bugzilla.wikimedia.org/show_bug.cgi?id=48937
[5] https://bugzilla.wikimedia.org/show_bug.cgi?id=49387
-Liangent
On Friday, 8 November 2013 8:11 AM, "wikidata-l-request(a)lists.wikimedia.org" <wikidata-l-request(a)lists.wikimedia.org> wrote:
Mailing list subscription confirmation notice for mailing list
Wikidata-l
We have received a request from ::ffff:106.78.150.27 for subscription
of your email address, "murasupan68(a)yahoo.com", to the
wikidata-l(a)lists.wikimedia.org mailing list. To confirm that you want
to be added to this mailing list, simply reply to this message,
keeping the Subject: header intact. Or visit this web page:
https://lists.wikimedia.org/mailman/confirm/wikidata-l/7271bc8db2e5f7a485a0…
Or include the following line -- and only the following line -- in a
message to wikidata-l-request(a)lists.wikimedia.org:
confirm 7271bc8db2e5f7a485a0d3a6b60803bffa126b68
Note that simply sending a `reply' to this message should work from
most mail readers, since that usually leaves the Subject: line in the
right form (additional "Re:" text in the Subject: is okay).
If you do not wish to be subscribed to this list, please simply
disregard this message. If you think you are being maliciously
subscribed to the list, or have any other questions, send them to
wikidata-l-owner(a)lists.wikimedia.org.
Hoi,
Wikidata supports many more items than any Wikipedia has articles and as
our objective is to "share in the sum of all knowledge", it is obvious that
Wikidata has added value.
Thanks to the latest hack by Magnus, it is now possible to include Wikidata
in your search result. I blogged about this [1].
When you are interested in this functionality as much as I am, add
*importScriptURI("//en.wikipedia.org/w/index.php?title=MediaWiki:Wdsearch.js&action=raw&ctype=text/javascript
<http://en.wikipedia.org/w/index.php?title=MediaWiki:Wdsearch.js&action=raw&…>");
*
to your User::YOUR_USER/common.js.
On the English Wikipedia add
*importScript('MediaWiki:Wdsearch.js');*
You can further improve the results in your language by adding labels in
your language on the items that matter to you in Wikidata.
Thanks,
GerardM
[1]
http://ultimategerardm.blogspot.nl/2013/11/divcon-valerie-sutton-found-on-o…
Hey everyone,
Progress! We now have the long awaited new search backend up and
running for testing on Wikidata. It will still need some tweaking but
please do try it and give feedback. It is running in parallel to the
old one. You will need to visit a special page to use it:
https://www.wikidata.org/w/index.php?search=athens&button=&title=Special%3A…
Please let me know about any issues you can still find with it so
this so we can soon make it the default.
Thanks to Chad and Katie for working on this.
Cheers
Lydia
--
Lydia Pintscher - http://about.me/lydia.pintscher
Product Manager for Wikidata
Wikimedia Deutschland e.V.
Obentrautstr. 72
10963 Berlin
www.wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das
Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.
Hey everyone,
The next sister project to get language links via Wikidata is
Wikisource. We're currently planning this for January 13.
The coordination is happening at
https://www.wikidata.org/wiki/Wikidata:Wikisource On this page we're
also looking for ambassadors to help spread the messages to the
different language editions of Wikisource. Please help if you can.
Cheers
Lydia
--
Lydia Pintscher - http://about.me/lydia.pintscher
Product Manager for Wikidata
Wikimedia Deutschland e.V.
Obentrautstr. 72
10963 Berlin
www.wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das
Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.
Hey, I got an ontology question.
Classes are, in semantic web framework and their foundations like
Description Logic, if I'am not wrong, something like a lohic predicate that
intensionaly or extentionaly defines the properties of their instances.
They are usually not qualified, but in Wikidata, as of now they are
properties like the others, who can also be qualified.
So the question is : could we use qualifier on classes to add predicates on
the class definition ? For example if
<George Bush> is an instance of <United States President> [<from> 1980 <to>
1984] (random years), this would mean that the instanciation add some
predicates on the other predicates we have on the <president of the united
states> ?
Just a random thought, I just realise I just qualified the instanciation,
not the class itself.
--TomT0m