Heya folks :)
Denny just took the time to write down some of the high-level things
that the Wikidata development will take as a base and guideline for
all the work that is to be done over the next year. You can find them
at http://meta.wikimedia.org/wiki/Wikidata/Notes/Requirements I hope
this helps to get everyone on the same page and clarifies some basic
things a bit more. If any of this is unclear let me know please.
We now also have a Twitter and identi.ca account that you can
subscribe to if you like. They are at http://twitter.com/wikidata and
http://identi.ca/wikidata
Cheers
Lydia
--
Lydia Pintscher - http://about.me/lydia.pintscher
Community Communications for Wikidata
Wikimedia Deutschland e.V.
Eisenacher Straße 2
10777 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.
On Mon, Apr 2, 2012 at 8:35 PM, Nadja Kutz <nadja(a)daytar.de> wrote:
>
> Am 02.04.2012 um 20:22 schrieb Lydia Pintscher:
>
>> On Mon, Apr 2, 2012 at 7:37 PM, Nadja Kutz <nadja(a)daytar.de> wrote:
>>> Hello,
>>>
>>> Is there any plan to use some kind of project management tool like trac (trac.org) ? Or at least a forum software?
>>> I find neither the mailing list nor the wiki very well suited for keeping track of the various discussion threads and
>>> software development issues.
>>
>> We'll be doing SCRUM and there will be a public SCRUM log for that.
>
>
> trac has a scrum plugin (which I havent yet tried out). It has also a direct hub to subversion http://en.wikipedia.org/wiki/Apache_Subversion
>
>> No there will not be a forum. I don't want to split discussions even further.
>
> the problem is that on this mailing list it is even problematic to identify a discussion thread.
> Whats so bad about to split discussions?
It would not be so much of a problem if people would change the
subject of emails when they reply to a thread with a completely
different topic ;-) (Like I did with this email now.)
Splitting discussions over even more media is bad because it makes it
even more impossible for people to keep up with everything.
>> I will be doing weekly summaries starting next week probably. These
>> should be good to keep track of everything if you don't want to read
>> all the emails.
>>
>
> Eventually one would like to reply to a discussion, I dont know wether this works very well if you just read the summary.
I'm afraid it is difficult to both keep up with everything and not.
Cheers
Lydia
--
Lydia Pintscher - http://about.me/lydia.pintscher
Community Communications for Wikidata
Wikimedia Deutschland e.V.
Eisenacher Straße 2
10777 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.
Hello everybody! My Wikipedia username is IWorld and I'll help on the
Wikidata project. I have created 2 logo candidates. You can see that on
the talk page of Wikidata
(https://meta.wikimedia.org/wiki/Talk:Wikidata). I hope you like them.
Sincerely,
IWorld
Hi all, I didn't think I'd be answering many threads on this list but when I saw the points about "moons of Uranus" and "cities through history" examples I couldn't resist mentioning the LIDO Schema (www.lido-schema.org) and the CIDOC-CRM ontology that it's based on (www.cidoc-crm.org/) - they have the descriptive power and range to cope with alternative historical viewpoints and "takes" on entities that you might need. Happy to discuss further.
Lydia,
Thank you for your answers. They help us better understand your project.
>2) Has this Wikidata project some Charter or terms of reference
>(TOR), or dedicated web site, you could give the URL?
>http://wikidata.org is > redirected to http://en.wikipedia.org/wiki/Main_Page
>
>No
Is one foreseen?
>5) What is the Wikidata's architectural framework? WDE (whole
>digital > ecosystem)? Human communications? The Internet services?
>Users > applications? Wikimedia?
>
>6) What are the normative choices, strategic objectives
>and constraints imposed by the sponsors and the WMF?
>This is a really broad question ;-)
>If you have more concrete questions I can try to find answers.
Conformance in terms of metadata registries standard?
Also, I do not find back the page where the two technical
responsibles of the project were introduced. Knowing who is who is
certainly a need. May be participants to the list/project could have
a dedicated introductory page?
Then, is the project be in charge of initial operations themselves
(design of the logo, installation, test, control)?
Good luck with all this and thanks.
jfc
Hi,
I've just subscribed to this list and would like to help the project.
My focus is to help on designing an API for the Wkidata project. So how
could I get involved?
Regards
Jan Ehrhardt
I invite you to the yearly Berlin hackathon. It's scheduled for 1-3
June and registration is now open. If you need financial assistance or
help with hotel/hostel/visa, just mention it in the registration form,
and please try to register by May 1st.
https://wmberlin.eventbrite.com/
This is the premier event for the MediaWiki and Wikimedia technical
community. We'll be hacking, designing, and socialising, primarily
talking about Gadgets, the switch to Lua for MediaWiki templates,
Wikidata, and Wikimedia Labs.
Our goals for the event are to bring 100-150 people together, with
lots of people who have not attended such events before. User
scripts, gadgets, API use, Toolserver, Wikimedia Labs, mobile,
structured data, templates -- if you are into any of these things, we
want you to come!
Details: https://www.mediawiki.org/wiki/Berlin_Hackathon_2012
Thanks to Wikimedia Germany for hosting and coordinating this event.
(Venue still to be determined.)
--
Sumana Harihareswara
Volunteer Development Coordinator
Wikimedia Foundation
[since it is my first intervention here, I quickly introduce myself: math
PhD student, hobbist coder, interested by the semantic universe but I
don’t know much than the general ideas for now.]
Le Mon, 02 Apr 2012 15:56:37 +0200, JFC Morfin <jefsey(a)jefsey.com> a écrit:
> 3. Then, the third problem no one has addressed yet except ISO 3166,
> is variance : two identical particulars (effects, names, data, etc.)
> may be different. eg. there are many ways to compute and present the
> same date. Are the results to be stored in Wikidata in all these ways
> every day and bridges to be built? or are they to be stored as a
> single data with the formulas to compute them, then how to be sure
> some parameters have not changed (i.e. death of the Emperor) and
> computation was not tampered with? Variance is everywhere (actually
> variance is most probably Life). ISO 3166 has no variance, because it
> is the sovereign reference: the list of States and laws languages
> (however, Palestine is in it already, Taiwan is there). ISO documents
> are in French, English and possibly in Russian. ISO 3166:1 states
> which are the normative languages in every country by reference to
> ISO 639 (list of language names). ISO 3166 defines the ccTLDs and is
> used in langtags to document languages and cultures. ISO 10646
> (supported by UNICODE) is the scripts character coded tables. At
> binary layer it is full of variants (same graphs being supported by
> different code points).
I’m interested in this point since one often encounter on Wikipedia
uncertainty/variance about some data:
* dates can be known with some uncertainty (e.g. "born between -345 and
-342", or "born in 734 or 736, depending of sources")
* fixed dates could not be sufficient (e.g. "not born"/"not dead" for some
mythological/religious characters, or "eternal" for the Eternal President
of the Republic of North Korea)
* some physical constants are defined up to a given precision (e.g.
Avogadro constant)
* names whose the writing is not fixed because of an oral tradition
* the nationality of some people changed during their life so it cannot be
considered in some specific cases as "one" data (e.g. Einstein)
Sébastien
PS: just curious: from what I understood, Unicode define some
normalization rules to assure the unicity of a glyph vs code point (form
C), no?