Hi all,
On a side note I would like to mention that labels and aliases are
external identifiers, perhaps not as accurate as database IDs, as natural
language users tend to stretch the conceptual boundaries, but they can also
be referenced and sourced.
If, as Lydia says, database IDs will have
On Wed, Oct 22, 2014 at 10:47 AM, svetlana svetl...@fastmail.com.au wrote:
If we have a need in pointing (at Wikibase/Wikidata) to redirects on a
regular basis, it might be time to rethink the relevant project design.
I think that rethinking the project design is the right approach here. To
Another thing that I am seeing now is that parsoid plans to add IDs to all
elements:
https://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec/Element_IDs
I don't know enough about it to see if those element IDs could be used as
section identifiers, but it might be well worth to ask about it.
I'm thinking of possible ways to represent constraints as items (see [1]),
like those in: https://www.wikidata.org/wiki/Property_talk:P19
However some of these are not easy to translate into Wikidata proper. For
example:
place of birth (P19) Conflicts with instance of (P31): criminal delict
On Sat, Oct 18, 2014 at 1:12 PM, Andy Mabbett a...@pigsonthewing.org.uk
wrote:
On 18 October 2014 08:15, Gerard Meijssen gerard.meijs...@gmail.com
wrote:
I think I requested P1472, I forgot all about it. It takes so long before
The proposal was mine:
On Sun, Oct 19, 2014 at 6:54 PM, rupert THURNER rupert.thur...@gmail.com
wrote:
would it make sense to use wikidata for such tasks as well?
Wikidata already represents more granular information than an article, the
real problem is that the only way that we have to bind a piece of
information
Hi Eric,
The idea is to separate in those edge cases the perceptual model (what is
recognized) from the name given to it. As such you can consider ethanol
and chemical compound metaclasses (names) pointing to a label-less class
that represents the model.
In practical terms what it would entail
Hi Eric,
I have been following this issue for a long time, and I haven't found any
satisfactory answer from anyone or from any source. Totally disappointed I
decided to scrap everything and start again from the beginning, working on
a foundation that eventually would allow to represent emergent
/show_bug.cgi?id=70127
Regards,
Micru
On Thu, Aug 28, 2014 at 2:08 PM, Nicholas Humfrey
nicholas.humf...@bbc.co.uk wrote:
Fantastic, thanks!
Could you put linking to the user's preferred language (Accept-Language
header?) on the backlog?
nick.
From: David Cuenca dacu...@gmail.com
Reply
Lydia,
I have a question about pages in Wikidata connected to their items. In the
example you give:
https://www.wikidata.org/wiki/Q914807
How can be the page linked? I guess I have to enter it in the section
Pages on other sites linked to this item, but when I click add, there
is no suggester. I
Thanks for the stats, Gerard. Two thoughts:
- With so many items without description I wonder why we don't have the
automatic descriptions gadget enabled by default.
- There are many items without statements, but not that many articles
without a category -- would it be possible to have a game that
Markus, is this related with the idea of creating a database of
automatically inferred statements that you presented some time ago?
Cheers,
Micru
On Tue, Aug 19, 2014 at 12:30 PM, Markus Krötzsch
mar...@semantic-mediawiki.org wrote:
On 19.08.2014 12:20, Gerard Meijssen wrote:
Hoi,
I
:
On Tue, Aug 19, 2014 at 11:19 AM, David Cuenca dacu...@gmail.com wrote:
Thanks for the stats, Gerard. Two thoughts:
- With so many items without description I wonder why we don't have the
automatic descriptions gadget enabled by default.
I am a bit worried about enabling this by default
On Tue, Aug 19, 2014 at 5:59 PM, Markus Krötzsch
mar...@semantic-mediawiki.org wrote:
I guess it is related, yes. Although currently I am first focussing on
efficient query answering -- inference will come after that :-) Whether one
stores the results in a database or not is an implementation
...@wikimedia.de wrote:
On Sat, Aug 16, 2014 at 5:50 PM, David Cuenca dacu...@gmail.com wrote:
There are 3 columns in the sitelink section: Language, Code and
Linked
page. Usually language-code and wiki-code have a permanent 1:1
correspondence , but not in all projects (incubator, meta, wikidata
They are slightly different. One refers to the work the character appears
in, and the other refers to the fictional universe. For instance:
Frodo Baggins (Q177329) present in work The Lord of the Rings (Q15228)
Frodo Baggins (Q177329) from narrative or fictional universe Tolkien's
legendarium
There are 3 columns in the sitelink section: Language, Code and Linked
page. Usually language-code and wiki-code have a permanent 1:1
correspondence , but not in all projects (incubator, meta, wikidata).
Would it be possible to add a configuration option so that for wikis that
host several
://docs.google.com/spreadsheets/d/18W9xb5KXorotJ7qM58AsqK-
myAHEjiDgnZrqNXHEnwk/edit#gid=716082733
Since I am his main mentor, feel free to ask me further details.
Hope this helps!
Cheers,
Marco
On 8/13/14, 9:14 AM, David Cuenca wrote:
On Wed, Aug 13, 2014 at 12:55 AM, Daniel Kinzler
daniel.kinz
On Wed, Aug 13, 2014 at 12:55 AM, Daniel Kinzler
daniel.kinz...@wikimedia.de wrote:
I think it would be cool to use http://mappings.dbpedia.org/ - it already
has
mappings for hundreds of templates in different language versions to the
dbpedia
vocabulary. If we added a mapping for wikidata -
Yuri and others, I asked not long ago in Commons and there is no opposition
as long as it is for supporting visualizations. It would require modifying
what is allowed in commons, though. There are interesting comments on the
talk page
On Wed, Aug 13, 2014 at 9:52 PM, James Forrester jforres...@wikimedia.org
wrote:
If the infobox really has no options and just builds itself entirely
automatically, why not just move it out of the wikitext/etc. content
entirely and display it always? This makes pages much easier to edit in
Actually you don't even need to specify which infobox because that can be
automated using P1423 (infobox's main topic) and P1424 (topic's main
infobox). For instance if an item has instance of:person, then you can
check which infobox is connected to the item Q5 and use that infobox. These
@Bene*: The WE-Framework already has an interface for dealing with
statement ranks, have you tried the latest version?
https://ru.wikipedia.org/wiki/%D0%92%D0%B8%D0%BA%D0%B8%D0%BF%D0%B5%D0%B4%D0%B8%D1%8F:WE-Framework
As for mapping Wikipedia templates to wikidata properties I think James F.
User:Vlsergey from ruwiki presented yesterday at the Wikidata Meetup a new
wonderful infobox editor for Wikipedia infoboxes:
https://www.wikidata.org/wiki/Wikidata:Project_chat#Edit_directly_from_infocard_.2F_infobox
And also an improved authority template which you can see in action at Obama
, 2014 at 9:46 PM, David Cuenca dacu...@gmail.com wrote:
Exactly! That's the spirit, it is much better to cement openess and
tolerance while they are there :)
And just by setting up that page we'll have a place to chill out :)
Thanks
Micru
On Fri, Jul 25, 2014 at 5:12 PM, Markus Krötzsch
, David Cuenca wrote:
Worried about the harshness that lately has been developing, I have
started a new initiative to counter that by promoting more dialogue,
civility, and friendliness
https://www.wikidata.org/wiki/Wikidata:Shelter
When you are with friends you don't need to put any rule
I noticed that sometimes it is a bit sluggish when showing the suggestions,
maybe it is my network, no idea. And it would be nice if it could suggest
the three basic properties (instance of, sublcass of, part of) when the
item is empty and suggest further properties based on that initial value,
Markus, could your algorithm work together with human direction? Like, if
we entered which properties are common for a class, and then a user creates
an instance of that class, would the algorithm be able to sort those
properties based on how often they appear on the database?
Thanks,
Micru
On
Hi,
Will the monolngual text datatype support old languages? There are
settlements that had an official name in a now dead language. Besides of
no language, will there be an option to mark such names as custom and
use the qualifier language (p407) instead?
Thanks,
Micru
On Sun, Jun 29, 2014 at 3:01 PM, Daniel Kinzler daniel.kinz...@wikimedia.de
wrote:
This is correct. However, there will be no custom option: the set of
languages
supported by wikidata is a well-defined list, controlled by the
configuration of
the site. It's basically the list of languages
PM, Lydia Pintscher
lydia.pintsc...@wikimedia.de wrote:
Hey :)
On Sun, Jun 29, 2014 at 3:08 PM, David Cuenca dacu...@gmail.com wrote:
What about constructed or invented languages? A list will work for most
cases but there always will be edge cases and adding them to the list
will
be too
On Tue, Jun 17, 2014 at 10:50 AM, Lydia Pintscher
lydia.pintsc...@wikimedia.de wrote:
I really don't want us to add this additional complexity at this
point. We're trying really hard to make editing friendlier and easier
to understand. I think this would go in the opposite direction.
Not
Considering how hard is to please everyone I think it is a good start. The
color scheme is much better than the omg-this-is-so-depressing grey that
we have right now. And the picture plus the boxes look like they have the
right size. I'm not so sure about the statements size, but if they can be
This RFC was pending after several discussions. How to clarify the property
part of?
https://www.wikidata.org/wiki/Wikidata:Requests_for_comment/Refining_%22part_of%22
Cheers,
Micru
___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
, this can be
indicated with a qualifier.
In this way it is is a settlement and the rest can be deduced. Having
specific types of settlements for countries is imho not necessary in this
way.
Thanks,
GerardM
On 10 June 2014 22:14, David Cuenca dacu...@gmail.com wrote:
Hi Gerard,
I think
I think we should drop part of and start using a better mereological
system
https://en.wikipedia.org/wiki/Mereology#Various_systems
http://plato.stanford.edu/entries/mereology/image1.png
Cheers,
Micru
On Tue, Jun 10, 2014 at 8:05 PM, Joe Filceolaire filceola...@gmail.com
wrote:
Even where
. It will just alienate them.
Part of is something that is understood. There may be academic reasons
that make sense to the people who care about them. The question I think we
should take serious is if that is really where we want to go.
Thanks,
GerardM
On 10 June 2014 20:21, David
, Jun 5, 2014 at 4:28 PM, David Cuenca dacu...@gmail.com wrote:
When I drafted the functional structure that is appearing on items [1],
Gerard pointed out that it is drifting into the lexical area. That made me
think that while useful to have lexical data as an independent item as we
discussed
On Fri, Jun 6, 2014 at 3:08 PM, Daniel Kinzler daniel.kinz...@wikimedia.de
wrote:
SKOS is a good fit for Wikidata data items. For modeling Wiktionary, LEMON
fits
a lot better http://lemon-model.net/.
Could you please elaborate on how to share the label between q items and
the future lexical
On Fri, Jun 6, 2014 at 5:05 PM, Daniel Kinzler daniel.kinz...@wikimedia.de
wrote:
The software shouldn't know about special properties. A bot could know
about
them, and automatically add aliases.
Labels and aliases are acting as special properties, just that we cannot
decide which property
On Fri, Jun 6, 2014 at 7:08 PM, Lydia Pintscher
lydia.pintsc...@wikimedia.de wrote:
It's really too early to make all these decisions. We're still at
least a year away from any significant progress towards Wiktionary
unless anything changes. Until then we will have learned a lot more
and a
On Thu, Jun 5, 2014 at 3:15 PM, Joe Filceolaire filceola...@gmail.com
wrote:
Note that 'historic name' is not among these. Historic name is just an
official name (or one of the other name types) with an 'end date' qualifier.
These names are, I believe, worth putting in statements so we can
In order to clarify my previous email I have prepared this functional
taxonomy of the elements that in my opinion form an item:
Meta
+ Labels
-- Multilingual main label (no sources, no qualifiers)
-- Multilingual alternative labels (no sources, no qualifiers)
-- Multilingual historic/alternative
can cope with at this time. It makes
sense to first be able to include lexical items because what you are
getting into is firmly in that area.
Thanks,
GerardM
On 3 June 2014 20:30, David Cuenca dacu...@gmail.com wrote:
Continuing with the discussion of last week about the nature
Continuing with the discussion of last week about the nature of properties
I follow with my personal crusade to foster a better understanding of
Wikidata (which sometimes means asking difficult questions :)). This time I
ask about items, or concepts for that matter.
To start with I cherry-pick a
On Thu, May 29, 2014 at 9:04 PM, Andrew Gray andrew.g...@dunelm.org.uk
wrote:
One other issue to bear in mind: it's *simple* to have properties as a
separate thing. I have been following this discussion with some
interest but... well, I don't think I'm particularly stupid, but most
of it is
And to summarize the answer of the original question to future readers. The
point of properties is:
a) to help humans to better understand Wikidata
b) to help programmers (also humans :P) build the software running it
c) to make a distinction between concepts found in the world and the
concepts
Since the very beginning I have kept myself busy with properties, thinking
about which ones fit, which ones are missing to better describe reality,
how integrate into the ones that we have. The thing is that the more I work
with them, the less difference I see with normal items and if soon
On Wed, May 28, 2014 at 10:37 AM, Daniel Kinzler
daniel.kinz...@wikimedia.de wrote:
More fundamentally, they are semantically different: an item describes a
concept
in the real world, while a property is a structural component used for
such a
description.
As I perceive it, a property is a
items for reasons of maintenance.
Best regards,
Markus
On 28/05/14 09:25, David Cuenca wrote:
Since the very beginning I have kept myself busy with properties,
thinking about which ones fit, which ones are missing to better describe
reality, how integrate into the ones that we have
.
Cheers,
Markus
On 28/05/14 12:14, David Cuenca wrote:
Markus,
The explanation about the implications of renaming/deleting makes most
sense and just that justifies already the separation in two.
It is equally true that when we create a property, we might have
cleaned the original concept
Markus,
I share your dissatisfaction with part of because that language construct
hides many different conceptual relationships that should be cleared out, I
think we'll have some community discussion work to do in that regard. One
of the uses is: what is the relationship between a human and his
Hello Jean-Baptiste and welcome!
regarding the bibliographic aspects of your question, I have to mention
that we have a page where we collect and discuss these properties
https://www.wikidata.org/wiki/Wikidata:Books_task_force
As you can see, we already use the FRBR model and we were considering
Markus,
On Thu, May 29, 2014 at 12:53 AM, Markus Krötzsch
mar...@semantic-mediawiki.org wrote:
This is an easy question once you have been clear about what human
behaviour is. According to enwiki, it is a range of behaviours *exhibited
by* humans.
Settled :) Let's leave it at defined as a
Please, leave your comments here too:
https://meta.wikimedia.org/wiki/Requests_for_comment/How_to_deal_with_open_datasets
I've been gathering comments from several people, and in the next days I
will try to summarize these suggestions to be discussed on irc.
Thanks,
Micru
On Tue, May 27, 2014
On Thu, May 15, 2014 at 5:03 PM, Markus Krötzsch
mar...@semantic-mediawiki.org wrote:
I applaud your comparison of inferencing with a form of decompression. I
think this is a nice intuition (in fact, some people have researched
semantic compression where one tries to reduce the size of a
John,
I appreciate that you prepare these summaries so diligently. If you
wouldn't do it I would miss so many important things.
Thank you!
Cheers,
Micru
On Sun, May 25, 2014 at 6:31 PM, John Lewis johnflewi...@gmail.com wrote:
Hey everyone,
Here is the latest weekly summary
Hi,
During the Zürich Hackathon I met several people that looked for solutions
about how to integrate external open datasets into our projects (mainly
Wikipedia, Wikidata). Since Wikidata is not the right tool to manage them
(reasons explained in the RFC as discussed during the Wikidata session),
On Thu, May 15, 2014 at 1:42 PM, Cristian Consonni kikkocrist...@gmail.com
wrote:
Thanks for the pointer, How can I put this open data on Wikidata is a
question that I have been asked many times, this page was needed.
Thanks for your comment!
On Thu, May 15, 2014 at 3:59 PM, Samuel Klein
http://www.slideshare.net/petermurrayrust/the-content-mine-presented-at-uksg
___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Property proposal started as:
https://www.wikidata.org/wiki/Wikidata:Property_proposal/Generic#statement_disputed_by
I guess all additional parameters (page, chapter, etc) can go in the
references section.
We will be able to say things like:
birthfollowed bybaptism
---time span until next event
On Tue, May 6, 2014 at 1:37 PM, Thomas Douillard thomas.douill...@gmail.com
wrote:
We could create a new qualifier like ''contradicted by'' or ''disputed
by''. The sourcs are a problem though as we can source only the totality of
a claim, not only a qualifier of this claim, so we would have
Hi,
I'm having some cases where a work has been attributed to an author by a
source, but the source itself says this attribution is dubious, or it is
contesting a previous attributions as spurious.
As I see it, the rank of the statement is not deprecated (in fact it is
normal or even preferred),
just a question of picking one on Wikidata to
keep the family aspect of the relationship (whichever it is) intact,
and sooner or later one or the other will be chosen. It's a wiki after
all.
Jane
2014-05-05 11:24 GMT+02:00, David Cuenca dacu...@gmail.com:
Hi,
I'm having some cases
On Tue, Apr 29, 2014 at 12:48 PM, Daniel Kinzler
daniel.kinz...@wikimedia.de wrote:
If you have something like between 1846 and 1855, you can use the
before and
after fields of the time value:
time: +0001850-00-00T00:00:00Z,
precision: 9,
before: 4,
after: 5
This means the
On Mon, Apr 28, 2014 at 3:10 PM, Luca Martinelli
martinellil...@gmail.comwrote:
I recalled the fact quite correctly:
https://it.wikipedia.org/wiki/Modulo:Bio takes dates of birth and
death from Wikidata. I think we can talk to extend the possibility to
gender, and later to other fields.
it for
a group of people
https://it.wikipedia.org/wiki/Fratelli_Wright
On Sun, Apr 27, 2014 at 2:51 PM, David Cuenca dacu...@gmail.com wrote:
@Nemo, Apper: Do you think you could import that data into the wd-repo
AND make use of it via an inclusion template? In the past there was some
Hi Daniel,
Interesting report, about WD tagging I would also mention Denny's qLabel:
http://google-opensource.blogspot.de/2014/04/qlabel-multilingual-content-without.html
Regarding cost-efficient tagging options, there are automated
tagging/entity extraction methods like DBpedia Spotlight, which
On Thu, Mar 20, 2014 at 9:45 AM, Gerard Meijssen
gerard.meijs...@gmail.comwrote:
A similar thing can be considered for streets and stuff as well. Obviously
it needs a lot of thought but from an abstract point of view, a street or
an image, it is just another category of data. When it works for
On Thu, Mar 20, 2014 at 1:31 PM, Jo winfi...@gmail.com wrote:
I think wikidata has the potential to tie it all together. There is no
need to split the information over 2 databases.
It depends on how much granularity you want. If you want to use just
well-known entities, then for sure,
On Thu, Mar 20, 2014 at 3:36 PM, Gerard Meijssen
gerard.meijs...@gmail.comwrote:
Given that we want to collaborate with openstreetmap we could host it for
them
I like the idea of a Wikibase-powered OSM data repository, it is a pity
that the WM Incubator is only for language versions of
On Thu, Mar 20, 2014 at 5:17 PM, Susanna Ånäs susanna.a...@gmail.comwrote:
An independent project will require a lot of MediaWiki related knowledge
that is not necessarily found in an initial group of interested
individuals. Or combined OSM, MediaWiki Wikidata knowledge, which may be
even
On Thu, Mar 20, 2014 at 6:28 PM, Jo winfi...@gmail.com wrote:
Using property P402 is not a very good idea since object ids in OSM aren't
guaranteed to be stable. nodes, ways and relations each have their own
'namespace' and sometimes information is refined by moving it from a node
to a way or
Well, that is one part of the problem, which could be addressed in Wikidata
with a property official name with the datatype mono- or multi-lingual
string
(plannedhttps://www.wikidata.org/wiki/Wikidata:Development_plan#Multi-lingual_text_datatype_.28optional.29,
but not available yet) plus the
On Thu, Mar 20, 2014 at 12:53 AM, Andy Mabbett a...@pigsonthewing.org.ukwrote:
P.S. I have just proposed an accession number property for Wikidata,
which may also be of interest:
https://www.wikidata.org/wiki/Wikidata:Property_proposal/Unsorted#Accession_number
I don't think it is
Hi,
I have started writing some thoughts about a possible interaction between
VE and WD.
https://www.wikidata.org/wiki/User:Micru/Interaction_of_VisualEditor_with_Wikidata
I assumed the following requirements:
- link/unlink any template field to WD from VE
- edit WD data from VE
There are so
Hi,
I have started a Request for Comments on how to organize statements,
sitelinks, and external identifiers. Hopefully the feedback gathered can
help with the UI redesign.
https://www.wikidata.org/wiki/Wikidata:Requests_for_comment/Organizing_statements,_sitelinks,_and_external_identifiers
On Wed, Mar 12, 2014 at 2:52 PM, Andy Mabbett a...@pigsonthewing.org.ukwrote:
I'm not sugegsting that we make people enter even more information in
Wikipedia; I'm suggesting that wikidata would benefit from capturing
the data that is /already/ being entered into Wikipedia, not least via
AfC,
On Wed, Mar 12, 2014 at 6:11 PM, Andy Mabbett a...@pigsonthewing.org.ukwrote:
What does this have to do with AfC?
Indeed, nowhere in your post do you mention AfC, once.
Because there is no difference between creating an article through
enwiki-AfC or creating an article on any of the other
On Tue, Mar 11, 2014 at 12:36 PM, Joe Filceolaire filceola...@gmail.comwrote:
I agree that it makes sense that one of the first things to do when
creating a new wikipedia article should be to create an infobox which is
automagically linked to the creation of a wikidata item. There are a number
will truly replace Omegawiki.
Thanks,
GerardM
[1] A defective https://en.wiktionary.org/wiki/defective or
inadequatehttps://en.wiktionary.org/wiki/inadequateitem.
On 10 March 2014 14:03, David Cuenca dacu...@gmail.com wrote:
On Mon, Mar 10, 2014 at 1:50 PM, Gerard Meijssen
On Fri, Mar 7, 2014 at 6:37 PM, Denny Vrandečić vrande...@gmail.com wrote:
I still disagree - let me explain why. I think that trying to express a
query definition into a single statement is very hard. Having a specific
Query namespace allows us to create a completely new UI for them, allows
should it be
different from what it displays today?
Do you want the item pages to have the feature to directly embed query
results, instead of having a one-click distance to the actual query page
and its results?
Or is there more to it?
On Thu Mar 06 2014 at 3:10:44 PM, David Cuenca dacu
/Category:Books_by_Jean-Paul_Sartre
[2] https://en.wikipedia.org/wiki/Category:Books_by_J._R._R._Tolkien
[3] https://en.wikipedia.org/wiki/Books_by_David_Foster_Wallace
[4] https://en.wikipedia.org/wiki/List_of_US_Presidents
On Thu Mar 06 2014 at 1:49:54 PM, David Cuenca dacu...@gmail.com wrote:
The point I
While reading this [1] and observing how other website load large pages
without freezing my computer, I was just wondering why progressive loading
of items was not an option for Wikidata.
Is it too difficult to implement? Or impossible with mediawiki? Or just
undesirable for some other reasons?
for big items).
Cheers,
Micru
On Tue, Feb 25, 2014 at 8:58 PM, Lydia Pintscher
lydia.pintsc...@wikimedia.de wrote:
On Tue, Feb 25, 2014 at 8:55 PM, David Cuenca dacu...@gmail.com wrote:
While reading this [1] and observing how other website load large pages
without freezing my computer, I
Hi Denny,
I asked again about this property because there were some concerns when it
was created. From the comments I infer that the general ethos is not
against, but not thrilled either:
https://www.wikidata.org/wiki/Wikidata:Project_chat#Freebase-Wikidata_mappings
I share the feeling, I don't
The sitelinks are not used directly, they are aggregated by using the work
item as a central hub. Basically the algorithm is:
1.- query all edition-items that are connected to the same work-item using
edition of
2.- make a list of all the sitelinks used on each one of these
edition-items (1
On Tue, Nov 5, 2013 at 5:35 PM, Daniel Kinzler
daniel.kinz...@wikimedia.dewrote:
However, MediaWiki only supports one link per target site in the sidebar.
Maybe an on-page navigation box could be used instead of proper language
links?
With the help of JavaScript, the contents of that nav
On Wed, Nov 6, 2013 at 4:22 PM, Daniel Kinzler
daniel.kinz...@wikimedia.dewrote:
MediaWiki used to handle this inconsistently: multiple links for the same
language where shown in the sidebar, but not recorded in the database. This
inconsistency was fixed a few months ago - now, only one link
On Mon, Nov 4, 2013 at 4:43 PM, Daniel Kinzler
daniel.kinz...@wikimedia.dewrote:
Am 04.11.2013 16:10, schrieb Amir Ladsgroup:
If you're using statement instead of site link who we can trace item from
article of wikisource to wikidata
This will very soon be possible with queries.
Actually
Excellent news! :)
For the author pages it is quite straight-forward. For the bibliographic
metadata the easiest would be to connect wikidata items with the Book:
page generated by the (planned) Book Manager extension. The Book: page is
supposed to provide the book structure and act as a metadata
Hi,
I would like to know your opinion about having the value in the #property
parser function. Right now we have two options:
{{#property:P36}}
{{#property:capital}}
The problem with this model is that editors in wikipedia cannot see the
value unless they render the page (or possibly use the
...@gmail.com wrote:
Il 20/10/2013 20:30, David Cuenca ha scritto:
Hi,
I would like to know your opinion about having the value in the
#property parser function. Right now we have two options:
{{#property:P36}}
{{#property:capital}}
The problem with this model is that editors in wikipedia
Hi Dario,
Thanks for sharing this proposal. As posted in the talk page, I believe
that it would be a great opportunity to partner with dedicated
organizations like Datahub [1] (OKFN/CKAN).
Wikidata could also play an important role in semantically describing how
to interpret the information, for
Hi,
Maybe this is interesting as an import source for bibliographic info
http://blogs.ifla.org/bibliography/2013/08/06/german-national-library-offers-over-11-million-marc21-records-under-cc0-open-license/
Cheers,
Micru
___
Wikidata-l mailing list
If the problem is to automate bibliographic data importing, a solution is
what you propose, to import everything. Another one is to have an import
tool to automatically import the data for the item that needs it. In WP
they do that, there is a tool to import book/journal info by ISBN/doi. The
same
I cannot see it on the new property data type list:
http://test.wikidata.org/wiki/Special:NewProperty
Only item, geocoord, time, string, file...
On Fri, Aug 23, 2013 at 1:21 PM, Lydia Pintscher
lydia.pintsc...@wikimedia.de wrote:
On Fri, Aug 23, 2013 at 7:19 PM, Lydia Pintscher
To add up a couple of comments to what Denny said, from my experience with
Wikisource, reaching out to international, loosely connected communities is
already a big challenge on its own. I would like to invite Wiktionary
contributors to take a look to this Individual Engagement Grant project
that
wiktionar...@lists.wikimedia.orgHi,
If there is someone in Wikimania interested in participating in the talks
about the future support of Wiktionary in Wikidata, we will having a
discussion about the several proposals.
http://wikimania2013.wikimedia.org/wiki/Support_of_Wiktionary_in_Wikidata
1 - 100 of 119 matches
Mail list logo
