Apologies for cross-posting
==================== CALL FOR TUTORIAL PROPOSALS =======================
In conjunction with Hypertext 2015, the 26th ACM Conference on Hypertext
and Social Media.
Middle East Technical University, Northern Cyprus Campus, Cyprus
September 2-4, 2015
http://ht.acm.org/ht2015/http://ht.acm.org/ht2015/cfp_workshoptutorial.html
March 13, 2015: Tutorial and workshops proposals due
=========================================================================
The ACM Hypertext conference focuses on all aspects of modern hypertext
research including social media, semantic web, dynamic and computed
hypertext and hypermedia as well as narrative systems and applications.
The 26th ACM Conference on Hypertext and Social Media conference is pleased
to invite proposals for tutorials to be held with the conference.
The goal of tutorial is to present state-of-the-art theories,
methodologies and
techniques from experts in the field. Topics of interest should be related
to the main conference tracks, in relation on novel aspects to be examined
in deep. Interdisciplinary tutorials are also encouraged.We expect
proposals for half-day tutorials.
The goals of the workshops are to provide a more informal setting
for exchanging opinions, to share experiences, presenting ideas, foster
research
community and identify open problems and/or explore directions for
future research. As such, they also offer a good opportunity for researchers
to present their work and to obtain feedback from an interested community
in an interactive atmosphere. Proposals are especially encouraged on
emerging
topics, somehow related to the main conference tracks (links and connection
between people, open data and the semantic of things, user experience and
adaptive linking), but are not limited to other (novel) topics which might
be of interest for the hypertext community. Acceptance of workshop proposals
will be based on the experience and background of the organizers in the
topic,
and on the relevance of the subject matter with regard to the topics
addressed
in the main conference.We welcome proposals for different types of
workshops,
from working groups on a specific topic to more traditional conference-like
workshops. However, we prefer interactive workshops that guarantee richer
active interactions among participants and provide significant room for
controversial and stimulating discussions.We preferentially would rather
proposals for half-day workshops. The need for a full-day workshop should
be motivated by some particular reason. Potential proposers are invited
to discuss
their ideas with the workshop chair before working out a detailed
proposal.
====================== PROPOSAL FORMAT (TUTORIALS) =========================
The tutorial proposals – not longer than 3 pages - have to be sent by
email to the workshop chairs, and must contain the following information:
- Title of the tutorial
- Tutorial presenters (affiliation, contact details, homepage, and prior
experiences with tutorial organization, if any).
- Keywords (describing the main themes of the tutorial) (from 3 to 5)
- Abstract (up to 70 words)
- Description of the tutorial (topics and goals of the tutorial)
(up to 500 words)
- Motivation (why the topic is of interest for the conference audience)
- Tutorial format (lessons, exercises, etc)
- Intended audience and expected attendance (with historical data of past
versions of the tutorial, if available)
- Previous editions of the tutorial (if applicable) (URLs, conference it
was co-located with, number of participants , and any other relevant
information)
The organizers of accepted tutorials are then expected to prepare a
tutorial Web Site with the information about the tutorial.
====================== PROPOSAL FORMAT (WORKSHOPS) =========================
The workshop proposals – not longer than 5 pages - have to be sent by
email to the workshop chairs, and must contain the following information:
- Title of the workshop and acronym
- Workshop organizers (affiliation, contact details, homepage, and prior
experiences with workshop organization.
- Keywords (describing the main themes of the workshop) (from 3 to 5)
- Abstract (up to 70 words)
- Description of the workshop (topics and goals of the workshop) (up to 500
words)
- Motivation (why the topic is of interest for the conference audience)
- Workshop format (paper presentations, invited talks, panels, demo,
discussion,
etc)
- Submissions format (position papers, research papers, demo, poster,
presentations..) and, for each type of submission, specify the features
(length of the papers, template, etc)
- Intended audience and expected attendance (with historical data of past
versions of the workshop, if available)
- Initial list of (potential) members of the program committee
- Requested duration (half day or full day- in this case, motivation for
the need of a full day)
- Previous editions of the workshop series (if applicable) (URLs,
conference it
was co-located with, number of registrants, number of submissions,
number of accepted papers, and any other relevant information)
The Workshop Proceedings will be published in the ACM Hypertext Extended
Proceedings. If the organizers have addition plans for dissemination (for
example, a special issue of a journal) this needs to specified in the
proposal.
=============== ORGANIZATION OF WORKSHOP===============
After the acceptance of a workshop proposal, the organizer(s) should:
- Create and distribute a Call for Papers and a Call for Participation;
- Create a Web page for the workshop, with the call for papers and the
information about the workshop organization and timeline. The link of the
web site will be published on the Conference Web site;
- Create a Program Committee;
- Review and select contributions to be included in the workshop proceedings
(at least 2 reviewers for each paper);
- Schedule and coordinate the workshop activities.
- Put together accepted papers into electronic workshop proceedings, to be
published in the Extended Proceedings of ACM Hypertext 2015.
=============== IMPORTANT DATES ===============
March 13, 2015: Workshop and tutorial proposals due
March 23, 2015: Decisions announced
September 2, 2015: Workshop and Tutorial day
=============== SUGGESTED TIMELINE ===============
Workshop web site: March 24, 2015
Workshop Call for Papers: March 24, 2015
Paper submission deadline: June 12, 2015
Notification to authors: July 10, 2015
================== WORKSHOP CHAIRS ==================
Alvin Chin, Microsoft, China
E-mail: alvin.chin(a)utoronto.ca
Web: http://www.alvinychin.com
Ethan Munson, University of Wisconsin-Milwaukee, USA
E-mail: munson(a)uwm.edu
Web: https://pantherfile.uwm.edu/munson/www/
--
Federica Cena, Ph. D.
Assistant Professor - Researcher
Dipartimento di Informatica
Universita' di Torino
Corso Svizzera 185, 10149 Torino, Italy
Phone +39 0116706779
Fax +39 011751603
email: cena(a)di.unito.it
web: www.di.unito.it/~cena/
Hoi,
I understand that item descriptions are going to be used in a mobile app.
In my opinion that is seriously disappointing because it is not realistic
to expect enough coverage in any language. Particularly in the small
languages it will not be really useful.
My question is: we have had automated descriptions for a long time. What is
it that they makes that they are not used.?
Thanks,
GerardM
Hi,
TL;DR: How can a red link be annotated in a semantic way with a foreign
article title or a Wikidata Q item number?
Imagine: I'm writing a Wikipedia article in Russian. There's a red link in
it. I don't have time to write the target article for that link now, but
I'm sure that it should exist. In fact, that article does exist in the
English Wikipedia.
I want the link to be red (fr the usual wiki reasons), but until the
Russian article is written, I want to give the software a hint about which
topic it is supposed to be about. Telling it the English article name would
be one way to do it. Giving it the Wikidata Q item number would be an even
better way to do it.
Unfortunately, MediaWiki does not currently have true syntax to do either.
(Correct me if I'm wrong.)
Some Wikipedias may have templates that do something like this (e.g.
Russian: https://ru.wikipedia.org/wiki/Template:En ). But there's nothing
that is uniform to all projects.
*Why* is it useful to give the software this hint in the first place? Most
simplistically, it's useful to the reader - in case that reader knows
English, she can at least read something.
But there's something bigger. When the ContentTranslation extension
translates links, it automatically adapts links that can be found. What to
do about those that can't be auto-adapted? It frequently happens when
Wikipedians translate articles that many links in the created articles turn
out to be red. We'd love to get ContentTranslation to help the translators
make those articles by writing relevant articles with as few clicks as
possible, and that is only possible by annotating the red links with the
topics to which they belong.
So, any ideas?
What do other Wikipedias for such annotation?
Is it imaginable to add wiki syntax for such a thing?
Can anybody think of a hack that reuses the current [[link]] syntax to add
such annotation?
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore
Hey folks :)
Since one of our frontend developers is transitioning to doing more
design work we are looking for someone to join the Wikidata dev team
to work on Wikidata's frontend.
If you know your way around JavaScript and related technologies and
are passionate about Wikidata then this is your gig! Please apply and
join an awesome team. Or do you know someone else who'd be a good fit?
Please forward them the ad.
Details and how to apply are here:
https://www.wikimedia.de/wiki/Software_Developer_Frontend_Development
Cheers
Lydia
--
Lydia Pintscher - http://about.me/lydia.pintscher
Product Manager for Wikidata
Wikimedia Deutschland e.V.
Tempelhofer Ufer 23-24
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.
Dear wikidata lovers,
it took me some months but I'm finally more than happy to announce you
that my prototype of a resources mapper based on wikidata data is now
online! Inventaire.io <https://inventaire.io>
It offers the possibility to make a list of books you have using either
the ISBN or the wikidata Qid. So far, the best use of wikidata's power
is authors' books lists. Example here with Mr Q535:
https://inventaire.io/entity/wd:Q535
You can find the project's code here
http://github.com/maxlath/inventaire but for what is of wikidata, I
extracted the helpers I use in a separated library
https://github.com/maxlath/wikidata-sdk (javascript). Hope it might help
others.
I would be delighted to have your feedback on all that :)
Bests,
Maxime
--
Maxime Lathuilière
maxlath.eu <http://maxlath.eu>
@maxlath
on wikidata: Zorglub27 <https://www.wikidata.org/wiki/User:Zorglub27>
Hey folks :)
It's time to welcome another sister projects into our rounds. It'll be
Wikibooks. They'll get access to the interwiki links on Wikidata on
February 24th. Depending on how that goes I'll set a date for data
access. The page for all things Wikibooks is at
https://www.wikidata.org/wiki/Wikidata:Wikibooks. Please help by
giving them a warm welcome in 2 weeks.
Cheers
Lydia
--
Lydia Pintscher - http://about.me/lydia.pintscher
Product Manager for Wikidata
Wikimedia Deutschland e.V.
Tempelhofer Ufer 23-24
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.