On Fri, Oct 29, 2010 at 1:36 PM, Bryan Tong MinhFirst, my using the category system is a "hack" that works right now,
<bryan.tongminh@gmail.com> wrote:
> On Fri, Oct 29, 2010 at 2:25 PM, Krinkle <krinklemail@gmail.com> wrote:
>> For one, tags would not be hierarchical and not stored under a name,
>> rather a number (an id if you will).
>
> I would store the tag-i18n definitions in a separate Tag: namespace.
> Then you don't need to create the history tracking etc. all by
> yourself. You will need a unique identifier though, but I don't see a
> problem making the unique identifier equal to the content language.
and could be converted into a more mature solution at a later date.
As to "tracking", IMHO it would suffice to just add [[Tag:XYZ]] to the
pages; that's rather inelegant from a database POV, but as Bryan
points out, it would take care of version tracking etc. All one would
need to do is to remove them from the rendering and display them
separately, like categories.
Multilanguage tags, as well as synonyms, could simply be implemented
as #REDIRECTs, maybe. [[Tag:Blume]] would redirect to [[Tag:Flower]],
so a search for "Blume" would know about "Flower" easily. However, the
system would then have to search for both Blume and Flower internally.
Also, that could be a problem with "false friends" (en:Gift=present
vs. de:Gift=poison).
Another approach might be to duplicate the "hidden category" mechanism
and impose a special meaning there, e.g. no tags are shown on such a
category page (no tagging of tags), and these categories would then be
shown as tags on e.g. image pages.
Magnus
_______________________________________________
Commons-l mailing list
Commons-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/commons-l