** Apologies for cross-posting **
2nd International Workshop on
(Document) Changes: Modeling, Detection, Storage and Visualization
http://diff.cs.unibo.it/dchanges2014/
Part of ACM DocEng 2014
September 16th, 2014, Fort Collins, near Denver, Colorado
CALL FOR PAPERS
===============
DChanges 2014 is the second edition of the International Workshop on (Document) Changes: Modeling, Detection, Storage and Visualization in conjunction with the ACM Symposium on Document Engineering. This year, the workshop will be held in Fort Collins, near Denver, Colorado in September 2014.
The goal of this series of events is to share ideas, common issues and principles about models and algorithms for change tracking and detection, versioning and collaborative editing. We want to look at these topics from different perspectives and want to identify the most common issues and the peculiarities of each domain and each approach. The workshop aims at bringing together researchers and practitioners from industry and academia, to discuss these issues in an informal setting and to foster collaboration among them.
The 2014 edition will be focused on the interpretation, visualisation and exploitation of changes. One of last edition's outcomes was that we identified the need for novel interfaces to better understand and exploit detected changes. Several issues were pointed out as still unsolved: interfaces do not scale when dealing with many changes, changes at different levels of abstraction are often not sufficiently taken into account, detection and visualisation are often inter-mixed, logs are often detailed but underexploited, and versioning techniques are not very well suited for non-technical people.
Submissions on other topics are also welcome. We also seek contributions on, but not necessarily limited to:
* Diffing and change tracking algorithms
* Detecting changes on complex data structures
* High-level differences
* Change modeling and representation
* Novel approaches to tree-based diff
* Detecting changes on trees, graphs, diagrams and any kind of document
* Edit-distance measures
* Quality of deltas and patches
* Editing patterns
* Semantic diff
* Merging
* Management of update conflicts
* N-way merge algorithms
* Propagation of changes
* Applications
* Applications of diff techniques from and to other domains
* software engineering, ontology management, humanities, law, medicine
* Versioning systems
* Collaborative editors
Program
--------
The workshop will run a full day, and be divided in two parts, in order to emphasize both theoretical/algorithmic aspects and practical applications. Ample space will be given to peer discussions and brainstorming about the results of the presentations and the ideas brought forth by participants.
A detailed schedule will be announced in July.
Proceedings
-----------
We will publish workshop post-proceedings in the ACM International Conference Proceedings Series.
Authors are required to submit an extended abstract (2-4 pages long) that will undergo a single bling review process. Accepted extended abstracts will be available during the workshop. The best extended abstracts will also be included in the DocEng proceedings.
Full papers (4-8 pages long) are due after the workshop and will be included in the post-proceedings.
Important Dates
---------------
Authors are required to submit an extended abstract before the workshop and a full paper after the workshop:
* Extended Abstracts (2-4 pages) are due: June 6th
* Acceptance notice: July 4th
* Camera ready: July 20th
* Workshop: September 16th
* Full papers are due (4-8 pages): October 3rd
* Acceptance notice: October 24th
* Camera ready: November 14th
Paper submission
----------------
Papers must be submitted to the EasyChair site (available soon).
Two types of submissions are possible:
* Application/demo notes: showcasing systems or tools
** Extended abstract: 2 pages long
** Full paper: 4 pages long
* Research papers: describing original and unpublished research
** Extended abstract: 4 pages long
** Full paper: 8 pages long
All papers must conform to the ACM SIG Proceedings format. All submissions will undergo a rigorous single blind review process.
Organizers
----------
* Gioele Barabucci, Universität zu Köln
* Uwe M. Borghoff, Universität der Bundeswehr München
* Angelo Di Iorio, Università di Bologna
* Sonja Maier, Universität der Bundeswehr München
* Ethan Munson, University of Wisconsin-Milwaukee
For any question, please contact <dchanges(a)lists.cs.unibo.it>.
Program committee
-----------------
* Serge Autexier, DFKI Bremen
* Anne Etien, INRIA Lille Nord Europe research center
* Boris Konev, University of Liverpool
* John Lumley, PhD
* Pascal Molli, Université de Nantes - LINA
* Sebastian Rönnau, Zalando AG
* Wolfgang Stürzlinger, York University
* Yannis Tzitzikas, University of Crete and FORTH-ICS
* Fabio Vitali, Università di Bologna
* Jean-Yves Vion-Dury, Xerox Research Centre Europe
Hi,
I'm looking for a way to reproduce the autocomplete on wikidata search
field in an external app (to tag resources with wikidata entities ids),
but so far I couldn't find what could allow me to do this in the API doc.
In a little experiment
<https://github.com/maxlath/wikidata-autocomplete>, I tried to use the
API action /wbsearchentities/, but it appear to be inefficient until I
reach the full name... Is there already a way to query such an
"autocomplete API" or any plans to implement one? Or even better, is
there a way to easily re-use the wikidata search field widget? in a
non-PHP project? :D
Any clue welcome :)
Best regards,
Max
--
Maxime Lathuilière
maxlath.eu <http://maxlath.eu>
@maxlath
Zorglub27 <https://www.wikidata.org/wiki/User:Zorglub27>
Contributions
<https://www.wikidata.org/wiki/Special:Contributions/Zorglub27>
Hey folks :)
Last week, the GNOME Foundation announced the interns that were
accepted for the May - August 2014 round of the Outreach Program for
Women (OPW). Eight interns were selected to work on Wikimedia
projects, including two who will contribute to Wikidata outreach
efforts. I will be mentoring them with Thiemo as my backup.
Anjali Sharma of India will be focusing on the design of mobile app
concepts and promoting Wikidata on social media platforms. Her
original project proposal can be found here:
https://www.mediawiki.org/wiki/WikiHunt_the_%27Property%27:_Wikidata_Outrea…
She will be blogging about her progress here:
http://discoveranjali.wordpress.com/
Helen Halbert of Canada will be evaluating and expanding Wikidata
documentation and contributing to a GuidedTours extension for
introducing new users to Wikidata. Her original project proposal can
be found here: https://www.mediawiki.org/wiki/Feed_the_Gnomes_-_Wikidata_Outreach
She will be blogging about her progress here:
http://www.helenhalbert.com/
OPW is part of Wikimedia’s mentorship programs and is intended to
encourage new and intermediate contributors to grow their skills as
well as provide pathways for richer community collaboration. Community
feedback is essential to the success and sustainability of our
interns’ projects and will be sought by Anjali and Helen throughout
their work. They'll be in touch with you as the projects progress.
Please welcome them to Wikidata. I'm really excited to have them here
to help us out.
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.
Hey folks :)
The next deployment is on Tuesday. We've reworked handling of time and
geocoordinates quite considerably. It'd be awesome if you could give
it some testing at test.wikidata.org and let me know about any issues
you encounter.
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.
Suppose I publish a web page about a notable person, building or other
entity; and that the subject has a Wikidata entry.
What's the best meta header, to assert that the page is about the same
subject as the Wikidata entry?
I'm thinking of something like:
<link rel="foo" href="https://www.wikidata.org/wiki/Q42">
or
<meta name="DC.bar" content="https://www.wikidata.org/wiki/Q42">
but what values of foo or bar?
Given the likely ubiquity of Wikidata in the near future, should we mint:
<link rel="wikidata"
or a more generic:
<link rel="datasource" ?
Are there any such headers already in the wild? Should Wikipedia
articles and pages on sister projects include such headers?
--
Andy Mabbett
@pigsonthewing
http://pigsonthewing.org.uk
A friend of mine, noting that Wikipedia uses SVG images
for diagrams, asked if it also had some written guidelines
for how to write the SVG source code, in particular to
express measurement values in the original units rather
than on a pixel scale. He had found some SVG diagram that
made a curve from 140 pixels to 190 pixels, rather than
from 7 million to 9.5 million inhabitants, which was the
unit that the y axis displayed. (Or something like that.)
I said "probably not, your thinking is likely 5 years
ahead of the Wikipedia community".
As this all happened in April 2009, he came back yesterday
to ask where we are now.
Do we have any guidelines for how to hand-write the
source code of SVG diagrams? Should we?
Maybe this is related to Wikidata?
--
Lars Aronsson (lars(a)aronsson.se)
Aronsson Datateknik - http://aronsson.se