[an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] (none) [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] (none) [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive]
 
[an error occurred while processing this directive] [an error occurred while processing this directive]
Skåne Sjælland Linux User Group - http://www.sslug.dk Home   Subscribe   Mail Archive   Forum   Calendar   Search
MhonArc Date: [Date Prev] [Date Index] [Date Next]   Thread: [Date Prev] [Thread Index] [Date Next]   MhonArc
 

Re: [LOCALE] Test-database design



Preben Mikael Bohn skrev:

> Hej alle, jeg fik aldrig at vide hvor langt database
> designet var nået, så jeg antog det værste. :-)

Rimeligt nok.  Og godt initiativ at skrive på engelsk (det
kan jeg ikke huske om Makholm, Grove og jeg fik gjort).

> På http://speling.chin.dk/dbtables.html er mit første
> udkast til indhold i databasen.

Der er mig bekendt ikke noget sprog med sprogkoden "uk".
Der er "da", "da_DK", "en", "en_UK" (eller er det "en_GB"),
"en_US", m.fl.

> Jeg har for så vidt muligt holdt mig til hvad jeg kunne
> forstå fra noterne fra databasedesignmødet,
> http://jacob.sparre.dk/temp/referat-2002-03-12.ps.gz .

Fint.  Og det du ikke har forstået må jeg hellere prøve at
forklare.

(af hensyn til eventuelle fremtidige ikke skandinaviske
 brugere og udviklere skriver jeg argumenterne på engelsk,
 så de kan klippes direkte ind i et rationale for designet
 - undskyld)

All words
=========

 1) Technically the field name "word" is inappropriate,
    since we should also be able to keep information about
    possible misspellings in the database.  Or should they
    be kept elsewhere?  Where?

 2) With the field "word_class" you assume that one from the
    first time a word is added to the database has certain
    knowledge of which word class a given word (string)
    belongs to.  If we add "misspelling" and "unknown" to
    the table "word_classes" one can argue that it is okay.
    But it removes the option of letting the reviewers vote
    for or aginst the classification.  Or is it your idea
    that each reviewer should add the word (string) to the
    table with the classification that he finds correct?

 3) What kind(s) of operations will there be on this table
    when reviewers add or update information in the
    database?  And what kind(s) of operations will be batch
    oriented?

Descriptions
============

 1) Should every reviewer add his preferred description for
    each word?  Or how can the reviewers vote for a
    description for a word?  And how can reviewers vote
    against a description for a word?

 2) Should all strings (including possibly misspelled words)
    be allowed to have descriptions associated with them?

    Since a description can be added before a reviewer
    notices that a word is incorrect, the answer to this
    question is most likely "yes".

Synonyms
========

 1) Why are reverse (or "redundant") synonym links not
    allowed in the table?

 2) The problem of allowing reviewers to vote for or against
    information in the table has been ignored.

Language identifiers
====================

 1) "dk" is a country code, not a language code.

 2) Why not handle "international name" by looking up the
    name of a language in the relevant dictionary?  If you
    need the Italian (it) name for Danish (da), then you
    look up what Danish is called in Danish in a language
    information database and find the word "dansk".  In the
    same database you can also look up a reference to a
    Danish dictionary (for example "da.speling.org").  You
    can then look up the Italian (it) translation of the
    word "dansk" in the dictionary "da.speling.org" and find
    the word "danese".

 3) Is it really necessary to use an integer and not the
    language identifier itself as the key in this table?

> Jeg har lavet en "minimal"-database, dvs. indeholdende kun
> de data jeg har ment var relevante. Lige nu kører den i
> Gadfly (nemmest at håndtere i Zope :-)) men den skal
> selvfølgelig konverteres til f.eks. mysql. Herfra tror jeg
> at den bedste strategi for at komme videre er at få noget
> hurtigt op og køre. Jeg havde forestillet mig noget alá:
>
> 1) Lave et minimal-web-interface til databasen, f.eks. kun
> til at addere/korrigere ord (dvs. ikke fancy ting som
> ord-træer, ordklasser, etc). Jeg er selv gået i gang med
> dette i Zope (kigger lidt på bl.a.
> http://jacob.sparre.dk/temp/ordlisteopdateringseksempel ),
> men hvis der er andre der allerede har lavet det er det jo
> også fint.

Det lyder fint nok.  Men husk på at korrekturlæserne ikke
bare retter i ordlisten.  De stemmer bare på oplysningerne.

> 2) Hælde nuværende ordliste ind i databasen

God idé.

Jacob
-- 
"Those who will not reason, are bigots,
 those who cannot, are fools, and
 those who dare not, are slaves."


 
Home   Subscribe   Mail Archive   Index   Calendar   Search

 
 
Questions about the web-pages to <www_admin>. Last modified 2005-08-10, 20:53 CEST [an error occurred while processing this directive]
This page is maintained by [an error occurred while processing this directive]MHonArc [an error occurred while processing this directive] # [an error occurred while processing this directive] *