<?xml version='1.0'?>
<!-- copyright 2010 by RibbonSoft GmbH -->
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:rs="http://www.ribbonsoft.com/rdf/library">
  <rdf:Description rs:license="Public Domain">
    <rs:title>
      <rdf:li rs:locale="en" rs:resource="Bike" />
      <rdf:li rs:locale="de" rs:resource="Fahrrad" />
    </rs:title>
    <rs:authors>
      <rdf:Bag>
        <rdf:li rs:resource="http://www.clker.com" />
      </rdf:Bag>
    </rs:authors>
    <rs:keywords>
      <rdf:Bag>
        <rdf:li rs:resource="Giant" />
        <rdf:li rs:resource="MTB 327" />
        <rdf:li rs:resource="en_US" />
      </rdf:Bag>
      <rdf:Bag rs:locale="en">
        <rdf:li rs:resource="bike" />
        <rdf:li rs:resource="vehicle" />
        <rdf:li rs:resource="outline" />
        <rdf:li rs:resource="architecture" />
      </rdf:Bag>
      <rdf:Bag rs:locale="de">
        <rdf:li rs:resource="fahrrad" />
        <rdf:li rs:resource="zweirad" />
      </rdf:Bag>
      <rdf:Bag rs:locale="de_CH">
        <rdf:li rs:resource="velo" />
      </rdf:Bag>
    </rs:keywords>
  </rdf:Description>
</rdf:RDF>

• To discuss: Save the license as tag instead of a special field. Pure tag searching is awesome fast. The more special cases that have to be handled different, the slower the search. License tags are quite unique. If something is tagged with “GNU”, it is very likely that the license is meant (expect for the animal named gnu). Same for BSD, Public Domain and CC licenses.

• Mark (gray out) tags that are not available anymore due to the already chosen tags.
• Handle double click / rename
  • if a RDF is present, change the item title
  • if no RDF is present, add a new RDF and set the the title there
• Edit Meta Data dialog
  • add title (both dialog and newly created RDF files)
• Stemmer: Stemming is usually done at the indexing stage.
  • additional field in table keywords (type: 0=word, 1=stem)
  • don’t show stems in completer and tags lists
• Provide “radio button” tags, e.g. “license” or “modification time” cannot have more than one selection.
• rebuild (clear) library browser DB on start if language was changed
• Provide meta information for directories
  • The idea: One can have a directory and assign the author “Donald”. Every item in this directory will have assigned the author “Donald” automatically.
  • This is all RDF based, not editable by the user other than by editing the RDF file.
  • Problems
    • How can that be shown to the user? E.g. someone tags a directory called “architecture” by mistake with “mechanical”. Every item in this directory will now be found for “mechanical”, and will confuse the user.
      • → not shown to the user
    • Author and license could be overridden (if wanted) be setting them in a item. But what about tags? Tags actually just can be added, not replaced. It that comprehensible for the user?
      • → tags that are set on the directory level apply to all items in that directory
  • Stored in a directory named “_META”.
  • Inside “_META”, there’s the RDF file called “meta.rdf”.
  • Let’s keep this simple:
    • When an item’s RDF is parsed, the RDF of the directory is parsed first, then that data is replaced / extended by the item’s RDF. This way we only have to change things in one place (RDF parsing). DB, queries, etc. remain the same.
• the quick info (shown on item mouse over) should show additional information
  • the license
  • the author
• GUI changes according to the attached file
  • every tab should have its own list view (based on RListView) / model / splitter
  • RListView, LibraryBrowserView: use signal / slots mechanism instead of inheritance

• http://babelfish.yahoo.com/translate_txt?urltext=bike&lp=en_DE&doit=done
• http://code.activestate.com/recipes/64937-babelizer-api-for-simple-access-to-babelfishaltavi/

• RDF: add title
  • add item title and use it instead of the file name (avoids “bear01”)
• add item locale
• add authors as tag
• add license as tag
• perspectives (top, side, front)
• make it possible to easily combine common tags, e.g. “DIN-912”, “top viewing direction”, “high level of details”
  • Tags are searched with exact match (in opposite to the “normal” keyword search, which is “*keyword*”).
  • Drawings have additional tags to match this exact search, e.g. a drawing with the tag “DIN-912” has also the tag “DIN” assigned. These additional tags are made programmatically while parsing the RDF.
  • [old] This could be achieved by defining some standardized tags with a special meaning, e.g. viewing direction “view:top”, “view:front”, “view:side”; level of detail “lod:low”, “lod:medium”, “lod:high”. The user interface could show these special tags as filters for the current view or search view.
  • see also http://www.chefkoch.de/rezepte/ for an interesting approach to the problem

• favorites (saved in .ini file as list of paths)

COLUMN_NAME	TYPE_NAME	
id	        INTEGER	
text	        VARCHAR	
locale_id       INTEGER

COLUMN_NAME	TYPE_NAME
id	        INTEGER
text	        VARCHAR

• “locale independent”, always included in search

• filter filename
  • replace ‘_’ with " "
  • replace ‘-’ with " " leave “-”
  • replace numbers [0-9] with “”