[Wikitech-l] File licensing information support

Hello, As you may have noticed, Roan, Krinkle and me have started to more tightly integrate image licensing within MediaWiki. Our aim is to create a system where it should be easy to obtain the basic copyright information of an image in a machine readable format, as well as querying images with a

Re: [Wikitech-l] File licensing information support

Bryan Tong Minh wrote: > Hello, > > As you may have noticed, Roan, Krinkle and me have started to more > tightly integrate image licensing within MediaWiki. Our aim is to > create a system where it should be easy to obtain the basic copyright > information of an image in a machine readable format,

Re: [Wikitech-l] File licensing information support

2011/1/21 Platonides : > Conceptually, revision table shouldn't link to file_props. file_props > should be linked with image instead. > Maybe, but the current image/oldimage schema resembling cur/old is horrible. For instance, there is no way to uniquely identify an oldimage row. We talked about th

Re: [Wikitech-l] File licensing information support

On 01/20/2011 05:00 PM, Platonides wrote: > I would have probably gone by the page_props route, passing the metadata > from the wikitext to the tables via a parser function. I would also say its probably best to pass metadata from the wikitext to the tables via a parser function. Similar to categ

Re: [Wikitech-l] File licensing information support

Michael Dale wrote: > On 01/20/2011 05:00 PM, Platonides wrote: >> I would have probably gone by the page_props route, passing the metadata >> from the wikitext to the tables via a parser function. > > I would also say its probably best to pass metadata from the wikitext to > the tables via a pars

Re: [Wikitech-l] File licensing information support

Roan Kattouw wrote: > 2011/1/21 Platonides : >> Conceptually, revision table shouldn't link to file_props. file_props >> should be linked with image instead. >> > Maybe, but the current image/oldimage schema resembling cur/old is > horrible. For instance, there is no way to uniquely identify an > o

Re: [Wikitech-l] File licensing information support

The interest of wikisource project for a formal and standardyzed set of book metadata (I presume from Dublin Core) into a database table is obviuos. Some preliminary tests into it.source suggest that templates and Labeled Section Transclusion extension could have a role as "existing wikitext conte

Re: [Wikitech-l] File licensing information support

On 01/21/2011 02:45 AM, Alex Brollo wrote: > The interest of wikisource project for a formal and standardyzed set of book > metadata (I presume from Dublin Core) into a database table is obviuos. > Some preliminary tests into it.source suggest that templates and Labeled > Section Transclusion exte

Re: [Wikitech-l] File licensing information support

> Hello, > > > As you may have noticed, Roan, Krinkle and me have started to more > tightly integrate image licensing within MediaWiki. Our aim is to > create a system where it should be easy to obtain the basic copyright > information of an image in a machine readable format, as well as > querying

Re: [Wikitech-l] File licensing information support

2011/1/21 Platonides : > If we wanted to map it to a page/revision format, it seems quite > straightforward. I'm missing something, right? > You're missing that migrating a live site (esp. Commons, with 8 million image rows and ~750k oldimage rows) from the old to the new schema would be a nightmar

Re: [Wikitech-l] File licensing information support

On Fri, Jan 21, 2011 at 10:43 AM, Roan Kattouw wrote: > 2011/1/21 Platonides : > > If we wanted to map it to a page/revision format, it seems quite > > straightforward. I'm missing something, right? > > > You're missing that migrating a live site (esp. Commons, with 8 > million image rows and ~750

Re: [Wikitech-l] File licensing information support

Roan Kattouw wrote: > 2011/1/21 Platonides : >> If we wanted to map it to a page/revision format, it seems quite >> straightforward. I'm missing something, right? >> > You're missing that migrating a live site (esp. Commons, with 8 > million image rows and ~750k oldimage rows) from the old to the n

Re: [Wikitech-l] File licensing information support

2011/1/21 Platonides : > Do we agree in the target db schema? > That's the important point. > We haven't thought about it in detail. But it would be a fairly large change and require changes throughout the software, as well as possibly elsewhere in the schema. > Migrating a large site like commons

Re: [Wikitech-l] File licensing information support

Roan Kattouw wrote: > 2011/1/21 Platonides : >> Do we agree in the target db schema? >> That's the important point. >> > We haven't thought about it in detail. But it would be a fairly large > change and require changes throughout the software, as well as > possibly elsewhere in the schema. > >> M

Re: [Wikitech-l] File licensing information support

On Fri, Jan 21, 2011 at 3:36 AM, Michael Dale wrote: > On 01/20/2011 05:00 PM, Platonides wrote: >> I would have probably gone by the page_props route, passing the metadata >> from the wikitext to the tables via a parser function. > > I would also say its probably best to pass metadata from the wi

Re: [Wikitech-l] File licensing information support

An internally handled parser function doesn't conflict with showing it as a textbox. We could for instance store it as a hidden page prefix. Data stored in the text blob: "Author: [[Author:Bryan]] License: GPL --- {{Information| This is a nice picture I took }} {{Deletion request|Copyvio from htt

Re: [Wikitech-l] File licensing information support

On Jan 22, 2011 at 21:04 Platonides wrote: > An internally handled parser function doesn't conflict with showing it > as a textbox. > > We could for instance store it as a hidden page prefix. > > Data stored in the text blob: > "Author: [[Author:Bryan]] > License: GPL > --- > {{Information| This is

Re: [Wikitech-l] File licensing information support

Krinkle wrote: > So PHP would extract {{#author:4}} and {{#license:12}} from the > textblob when showing the editpage. > And show the remaining wikitext in the and the author/ > license as seperate form elements. > And upon saving, generate "{{#author:4}} {{#license:12}}\n" again and > prepen

Re: [Wikitech-l] File licensing information support

On Sat, Jan 22, 2011 at 10:09 PM, Platonides wrote: > Krinkle wrote: >> So PHP would extract {{#author:4}} and {{#license:12}} from the >> textblob when showing the editpage. >> And show the remaining wikitext in the and the author/ >> license as seperate form elements. >> And upon saving, genera

Re: [Wikitech-l] File licensing information support

* Magnus Manske [Sun, 23 Jan 2011 00:38:53 +]: > On Sat, Jan 22, 2011 at 10:09 PM, Platonides > wrote: > > Krinkle wrote: > >> So PHP would extract {{#author:4}} and {{#license:12}} from the > >> textblob when showing the editpage. > >> And show the remaining wikitext in the and the author/

Re: [Wikitech-l] File licensing information support

"Platonides" wrote in message news:ihfd31$buv$1...@dough.gmane.org... > An internally handled parser function doesn't conflict with showing it > as a textbox. > > We could for instance store it as a hidden page prefix. > > Data stored in the text blob: > "Author: [[Author:Bryan]] > License: GPL

Re: [Wikitech-l] File licensing information support

On 01/22/2011 08:15 PM, Bryan Tong Minh wrote: > Having a clear separate input text field "Author: " is much more > user friendly {{#fileauthor:}}, which is so to say, a type of obscure > MediaWiki jargon. I disagree. In real life, there are always more compliated cases, where an author is not

Re: [Wikitech-l] File licensing information support

plese see cc rel: http://labs.creativecommons.org/2011/ccrel-guide/ Chinese wikipedia: http://zh.wikipedia.org/ My blog: http://shizhao.org twitter: https://twitter.com/shizhao [[zh:User:Shizhao]] 2011/1/24 Lars Aronsson > On 01/22/2011 08:1

Re: [Wikitech-l] File licensing information support

* Lars Aronsson [Mon, 24 Jan 2011 07:06:02 +0100]: > On 01/22/2011 08:15 PM, Bryan Tong Minh wrote: > > Having a clear separate input text field "Author: " is much more > > user friendly {{#fileauthor:}}, which is so to say, a type of obscure > > MediaWiki jargon. > > I disagree. In real life

Re: [Wikitech-l] File licensing information support

Happy-melon wrote: > Eeeww > > What's any different between this and a {{#author: }} parser function apart > from the inability to access it from the wikitext? As noted, it's perfectly > possible for the data to be in a separate field on the upload form, either > by default or by per-w

Re: [Wikitech-l] File licensing information support

On 01/22/2011 01:15 PM, Bryan Tong Minh wrote: > Handling metadata separately from wikitext provides two main > advantages: it is much more user friendly, and it allows us to > properly validate and parse data. This assumes wikitext is simply a formatting language, really its a data storage, struc

Re: [Wikitech-l] File licensing information support

Before I respond to the recent new ideas, concepts and suggestions. I'd like to explain a few things about the backend (atleast the way it's currently planned to be) The mw_authors table contains unique authors by either a name or a userid. And optionally a custom attribution can be given (f

Re: [Wikitech-l] File licensing information support

Krinkle wrote: > Before I respond to the recent new ideas, concepts and suggestions. > I'd like to > explain a few things about the backend (atleast the way it's currently > planned to be) > > The mw_authors table contains unique authors by either a name or a > userid. > And optionally a cus

Re: [Wikitech-l] File licensing information support

* Michael Dale [Mon, 24 Jan 2011 13:18:00 -0600]: > We should focus on apis for template editing, > Extension:Page_Object_Model seemed like a step in the right direction > but not Something that let you edit structured data across nested > template objects and we could stack validation ontop of t

Re: [Wikitech-l] File licensing information support

Hi, There have been a lot of mails since I last had the the time to reply, so I'll reply to some points in a single mail. On Sat, Jan 22, 2011 at 9:04 PM, Platonides wrote: > An internally handled parser function doesn't conflict with showing it > as a textbox. > > We could for instance store i