Hello,
I’ve been learning how to use Moses decoder [1] for creating machine translation models for the Uzbek language and was wondering if anyone else has any experience with. After talking to Amir, we decided to set Moses up in a Labs instance. Is anyone else interested in this? How was your experience with the decoder?
Thanks,
Baha
[1] https://github.com/moses-smt/mosesdecoder
I invite review of this preliminary proposal for a Google Summer of
Code project:
http://www.mediawiki.org/wiki/Accuracy_review
If you would like to co-mentor this project, please sign up. I've been
a GSoC mentor every year since 2010, and successfully mentored two
students in 2012 resulting in work which has become academically
relevant, including in languages which I can not read, i.e.,
http://talknicer.com/turkish-tablet.pdf .) I am most interested in
co-mentors at the WMF or Wiki Education Foundation involved with
engineering, design, or education.
Synopsis:
Create a Pywikibot to find articles in given categories, category
trees, and lists. For each such article, add in-line templates to
indicate the location of passages with (1) facts and statistics which
are likely to have become out of date and have not been updated in a
given number of years, and (2) phrases which are likely unclear. Use a
customizable set of keywords and the DELPH-IN LOGIN parser
[http://erg.delph-in.net/logon] to find such passages for review.
Prepare a table of each word in article dumps indicating its age.
Convert flagged passages to GIFT questions
[http://microformats.org/wiki/gift] for review and present them to one
or more subscribed reviewers. Update the source template with the
reviewer(s)' answers to the GIFT question, but keep the original text
as part of the template. When reviewers disagree, update the template
to reflect that fact, and present the question to a third reviewer to
break the tie.
Possible stretch goals for Global Learning Xprize Meta-Team systems
[http://www.wiki.xprize.org/Meta-team#Goals] integration TBD.
Best regards,
James Salsman
LDQ 2015 CALL FOR PAPERS
2nd Workshop on Linked Data Quality
co-located with ESWC 2015, Portorož, Slovenia
June 1, 2015
http://ldq.semanticmultimedia.org/ <http://ldq.semanticmultimedia.org/>
/*News flash: Invited talk by Prof.Dr.Felix Naumann on "Brave new data,
revisited"*//*
*/http://ldq.semanticmultimedia.org/program/keynote_felix_naumann
<http://ldq.semanticmultimedia.org/program/keynote_felix_naumann>
*Important Dates*
* Submission of research papers: March 16, 2015
* Notification of paper acceptance: April 9, 2015
* Submission of camera-ready papers: April 30, 2015
Since the start of the Linked Open Data (LOD) Cloud, we have seen an
unprecedented volume of structured data published on the web, in most
cases as RDF and Linked (Open) Data. The integration across this LOD
Cloud, however, is hampered by the ‘publish first, refine later’
philosophy. This is due to various quality problems existing in the
published data such as incompleteness, inconsistency,
incomprehensibility, etc. These problems affect every application
domain, be it scientific (e.g., life science, environment),
governmental, or industrial applications.
We see linked datasets originating from crowdsourced content like
Wikipedia and OpenStreetMap such as DBpedia and LinkedGeoData and also
from highly curated sources e.g. from the library domain. Quality is
defined as “fitness for use”, thus DBpedia currently can be appropriate
for a simple end-user application but could never be used in the medical
domain for treatment decisions. However, quality is a key to the success
of the data web and a major barrier for further industry adoption.
Despite the quality in Linked Data being an essential concept, few
efforts are currently available to standardize how data quality tracking
and assurance should be implemented. Particularly in Linked Data,
ensuring data quality is a challenge as it involves a set of
autonomously evolving data sources. Additionally, detecting the quality
of datasets available and making the information explicit is yet another
challenge. This includes the (semi-)automatic identification of
problems. Moreover, none of the current approaches uses the assessment
to ultimately improve the quality of the underlying dataset.
The goal of the Workshop on Linked Data Quality is to raise the
awareness of quality issues in Linked Data and to promote approaches to
assess, monitor, maintain and improve Linked Data quality.
The workshop*topics*include, but are not limited to:
* Concepts
* - Quality modeling vocabularies
* Quality assessment
* - Methodologies
* - Frameworks for quality testing and evaluation
* - Inconsistency detection
* - Tools/Data validators
* Quality improvement
* - Refinement techniques for Linked Datasets
* - Linked Data cleansing
* - Error correction
* - Tools
* Quality of ontologies
* Reputation and trustworthiness of web resources
* Best practices for Linked Data management
* User experience, empirical studies
*Submission guidelines*
We seek novel technical research papers in the context of Linked Data
Quality with a length of up to 8 pages (long) and 4 pages (short)
papers. Papers should be submitted in PDF format. Other supplementary
formats (e.g. html) are also accepted but a pdf version is required.
Paper submissions must be formatted in the style of the Springer
Publications format for Lecture Notes in Computer Science (LNCS). Please
submit your paper via EasyChair at
https://easychair.org/conferences/?conf=ldq2015
<https://easychair.org/conferences/?conf=ldq2015>. Submissions that do
not comply with the formatting of LNCS or that exceed the page limit
will be rejected without review. We note that the author list does not
need to be anonymized, as we do not have a double-blind review process
in place. Submissions will be peer reviewed by three independent
reviewers. Accepted papers have to be presented at the workshop.
*Organizing Committee*
* Anisa Rula – University of Milano-Bicocca, IT
* Amrapali Zaveri – AKSW, University of Leipzig, DE
* Magnus Knuth – Hasso Plattner Institute, University of Potsdam, DE
* Dimitris Kontokostas – AKSW, University of Leipzig, DE
=SMWCon Spring 2015 Second Call for Contributions=
SWMCon Spring 2015 is in need of contributions. This means you!
We are inviting you to submit your contributions to help collect and put together the conference program.
==Call for Contributions==
We need your proposals for talks and tutorials. Talks could be about anything related to semantics, wikis, or yes semantic wikis! We welcome new contributions on the use of semantic wikis in different industries and the development and proposal of new tools in and around the semantic wiki community.
You can propose your contributions on the conference website (http://semantic-mediawiki.org/wiki/SMWCon_Spring_2015) in form of regular talks or short lightning talks. All submitted proposals will be reviewed and we will do our best to consider your proposal in the conference program. If you've already announced your talk it's now time to expand its description.
We are also looking for folks to help us with our tutorial day. We’re looking for presentations on the basics of Semantic MediaWiki and related extensions. The deadline is April 22nd, but we encourage submissions, even in a draft form, as soon as possible to help with planning.
Please note that all tutorials and presentations will be video and audio recorded and made available for others after the conference.
Please add yourself to the informal list of attendees if you’d like to attend.
==Important Facts==
*Submission Deadline is April 22nd (please contact the organizers if you need more time)
*SMWCon is from Wednesday, May 6th to Friday, May 8th 2015
*T-Rex (http://downtowntrex.com), 911 Washington Ave., St. Louis, MO, USA
*Conference site: http://semantic-mediawiki.org/wiki/SMWCon_Spring_2015
*Participants: Everybody interested in semantic wikis, especially in Semantic MediaWiki, e.g. administrators, developers, wiki users, consultants, business representatives and researchers.
==List of Topics==
Here are some suggestions. All submissions are welcome.
Use of wikis in
*Academia
*Business
*Entertainment
*Research
*Sciences
*Social Services
Use of wikis for
*Knowledge Management
*Community Building
*Project Managmeent
*Personal Wikis
*Emergency Response
*Event Planning
Extending Semantic MediaWiki
*Extensions
*Integration with other services (databases, external APIs, etc)
*Visualization and reporting tools
Developments around Semantic MediaWiki
*Community building
*Feature wish lists
*SMW and related extensions roadmaps
*Improving the experience using semantic wikis
*How to contribute to SMW and related projects
*Multilingual support
*Access control
==Registration==
Registration is open with early bird pricing until March 31st. Tickets can be purchased at http://smwcons2015.eventbrite.com
Your registration fee includes:
*3-day Conference Pass (including the tutorial day)
*Breakfast for all three days
*Lunch on the first and 3rd day
*Coffee, snacks
*Evening social event with hors d'oeuvres and drinks
Please note that the registration fee does not cover accommodation or travel expenses.
===Academic Pricing===
Attendees from education organizations can purchase a discounted ticket. Proof of affiliation may be requested.
==Organizing Committee==
*Chris Koerner [Local Chair]
*Paul Boal [Program Chair]
==Sponsors==
*Mercy (http://mercy.net)
*SNPedia (http://www.snpedia.org)
This electronic mail and any attached documents are intended solely for the named addressee(s) and contain confidential information. If you are not an addressee, or responsible for delivering this email to an addressee, you have received this email in error and are notified that reading, copying, or disclosing this email is prohibited. If you received this email in error, immediately reply to the sender and delete the message completely from your computer system.
In the next RFC meeting we will discuss the following RFCs:
* AuthManager
<https://www.mediawiki.org/wiki/Requests_for_comment/AuthManager>
* Allow ContentHandler to expose structured data to the search engine
<https://phabricator.wikimedia.org/T89733>
The second one is not a proper RFC page on mediawiki.org, because
Daniel Kinzler felt like being an anti-wiki rebel this week ;)
The meeting will be on the IRC channel #wikimedia-office on
chat.freenode.net at the following time:
* UTC: Wednesday 21:00
* US PST: Wednesday 13:00
* Europe CET: Wednesday 22:00
* Australia AEDT: Thursday 08:00
-- Tim Starling
Please join us for the following tech talk:
*Tech Talk**:* Hack: An Evolution of PHP
*Presenter:* Josh Watzman from Facebook
*Date:* March 4th
*Time:* 1800 UTC
<http://www.timeanddate.com/worldclock/fixedtime.html?msg=Hack%3A+An+Evoluti…>
Link to live YouTube stream <http://www.youtube.com/watch?v=jqXqdqUhxy8>
*IRC channel for questions/discussion:* #wikimedia-office
Google+ page
<https://plus.google.com/u/0/b/103470172168784626509/events/ckh4leo7qam35mc5…>,
another
place for questions
*Talk description: *Although PHP has several features that allow engineers
to be extremely productive in it, it also has several rough edges and
pitfalls that cause problems (and often give the language a bad name). This
talk will introduce Hack, Facebook's dialect of PHP. Hack keeps most of the
PHP language -- all of the parts that make engineers so productive -- but
sands down several of the more problematic sharp edges. It also introduces
several new features, such as a simple yet extremely powerful syntax for
asynchronous IO, to make the language even more effective for existing PHP
programmers and newcomers alike.
Here are the minutes for this week's VisualEditor weekly triage meeting on
2015-03-04.
*Item 1 – Release criteria*
The release criteria at
https://phabricator.wikimedia.org/project/sprint/profile/1015/ were
considered.
No changes were proposed. N
ote that the lowest priority label in Phabricator was re-labelled to
"Lowest", and this document was adjusted to follow suit.
*Item 2 – Review of fixed tickets since last week*
These accepted items were fixed and so will be released in this week's
production release unless otherwise noted.
…
in VisualEditor:
- *https://phabricator.wikimedia.org/T91299
<https://phabricator.wikimedia.org/T91299>* – Don't show redlinks as
existing links if MediaWiki didn't tell us one way or the other
- *https://phabricator.wikimedia.org/T88386
<https://phabricator.wikimedia.org/T88386>* – ~50ms spent animating
a.oo-ui-buttonElement-button
- https://phabricator.wikimedia.org/T76523 – Show the VisualEditor
toolbar/editor chrome as soon as VE scripts are loaded, rather than
blocking on waiting for the content to load
- https://phabricator.wikimedia.org/T89054 – Adjust the context menu to
be able to display richer data for tools that want it; plus the related
task https://phabricator.wikimedia.org/T71474 – Reference & cite
tooltips should show content snippets, instead of generic labels
- https://phabricator.wikimedia.org/T70590 – If you click out of a link
inspector to somewhere else in the document, the link gets inserted and
selected, moving your cursor away from where you clicked
- https://phabricator.wikimedia.org/T89923 – Categories become "detached
item" after clicking 'Cancel' button
- https://phabricator.wikimedia.org/T89878 – mediawiki.feedback should
use OOjs UI dialog
- https://phabricator.wikimedia.org/T76998 – Random removal of
categories when using Safari; as part of which we also fixed the related
tasks https://phabricator.wikimedia.org/T74048 – VE corruption issue(?)
moving pre-existing categories to the middle of the page and
https://phabricator.wikimedia.org/T72373 – Categories incorrectly moved
up, possibly due to improperly closed table
… plus several items we caught in development and testing before they
became regressions.
The fixed tickets represent 78 "story points". There are 604 remaining
points in the list of items accepted as of the end of the meeting.
… in dependencies:
- – None this week
*Item 3 – Review of nominated tickets*
Nominated tickets accepted:
… as corruption & stability issues:
- – None this week
… as performance issues:
- – None this week
… as testing issues:
- https://phabricator.wikimedia.org/T90673 – Concurrent builds using
local Chromium/Firefox browsers on Linux host fail [dependency of
previously accepted testing task]
… as feature issues:
- https://phabricator.wikimedia.org/T90420 – Initiating VisualEditor via
"Edit" button Firefox scrolls to bottom of page
… as "polish" nice-to-have issues:
- https://phabricator.wikimedia.org/T85622 – New internal links on
/w/index.php?… pages are created relative to /w/ not /wiki/ in the CE and
context menu and so fail to go anywhere
- https://phabricator.wikimedia.org/T89399 – Don't rely on unreliable
DOMNodeInsertedIntoDocument event for autosizing TextInputWidget
[dependency of previously accepted polish task]
- https://phabricator.wikimedia.org/T90454 – Load and display the
welcome dialog straight after the toolbar, without waiting for the content
area
- https://phabricator.wikimedia.org/T91245 – setupSlugs is called twice
during ContentBranchNode setup [polish because performance concerns have
abated]
- https://phabricator.wikimedia.org/T91248 – Using data URI images in
inline slugs (for chimeras) is slow in Chrome (and possibly others) [polish
on performance grounds again]
- https://phabricator.wikimedia.org/T52227 – OOjs UI: Toolbar should
collapse items rather than span multiple lines when the window is narrow
- https://phabricator.wikimedia.org/T90815 – Implement a way to nest
toolbar groups without implementing nesting of toolbar groups [accepted
along with T52227 for quick and dirty implementation now, do proper
implementation later]
- https://phabricator.wikimedia.org/T51806 – Hidden templates should
display as an icon in-page in VisualEditor so they can be interacted with
(e.g. a puzzle piece?)
… as dependencies:
- – None this week
… for investigation and re-triage:
- – None this week
Nominated tickets rejected:
- – None this week
*Item 4 – Other business*
After some discussion, it was agreed that we would use Google Hangouts for
future meetings, to simplify things.
Hope this is of interest. Next week's meeting will be at
19:00 UTC
<http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150311T12&p1=224…>
(
12
:00 PST; note that the time difference has changed due to the US early
adoption of Summer Time) on Wednesday
11
March; hope to see many of you there. Joining instructions are on
mw:Talk:VisualEditor/Portal
<https://www.mediawiki.org/wiki/Talk:VisualEditor/Portal#How_to_join_the_tri…>
. We'll send a reminder before the meeting.
Yours,
--
James D. Forrester
Product Manager, Editing
Wikimedia Foundation, Inc.
jforrester(a)wikimedia.org | @jdforrester
On Thu, Feb 5, 2015 at 5:30 AM, Brion Vibber <bvibber(a)wikimedia.org> wrote:
> I've done an update pass on the patch to TimedMediaHandler adding my
> ogv.js JavaScript Ogg Theora/Vorbis playback engine for IE 10/11 and Safari
> 6.1+ users:
>
> https://phabricator.wikimedia.org/T63823
>
> It now comes in two parts:
> * https://gerrit.wikimedia.org/r/#/c/165477/ - libraries only
> * https://gerrit.wikimedia.org/r/#/c/165478/ - TMH modifications for
> desktop only
>
> (I wasn't happy with the mobile video overlay in the third patch and have
> abandoned it for now, will rewrite it soon but want to sync up with mobile
> web team on integration issues.)
>
> This version should pretty much "just work" on desktops/laptops, including
> seeking, and the JS console spam should be gone now. If folks have strong
> preferences on my plugin code, do let me know and I will tweak further. :)
>
I've rebased these for recent tweaks to TMH, please feel free to take a
peek!
-- brion
>
>
> I have a live wiki running at http://ogvjs-testing.wmflabs.org/ -- note
> that thumbnail images of some videos there are broken due to some kind of
> InstantCommons issue but the actual video plays through.
>
> -- brion
>
Hi,
Sorry, I know I asked about this thing recently, but I can't remember
what the outcome was.
I know it's currently not possible to create cross wiki templates, but
is there any plan to implement this feature? For example pages like
http://enwp.org/Linux contains "Latest version" and probably many
other pages reference this latest version. Not only on english
wikipedia, but many other wikis as well.
We have the people to update all wikis when new version is out, but we
don't have them for every piece of software on the planet, so having a
central template that would contain DATA * that could be accessed
anywhere would be nice.
* Now why I highlighted DATA? Because I was thinking that project
called "wikidata" would actually fit this purpose. Unfortunatelly it's
not. The internal API's of wikidata do not allow for some weird
security reasons to access data for any article from article with
different name. So if there was entry in wikidata for linux, and I
wanted to access property "version" in article [[Linux kernel
history]] I wouldn't be able to do that. {{FIXME}}
Thanks