1. This ReadMe.txt file explains content of zip file.
  2. This zip contains a MySQL database dump of two files

    http://rdf.dmoz.org/rdf/structure.rdf.u8.gz
    http://rdf.dmoz.org/rdf/content.rdf.u8.gz

    Published by http://rdf.dmoz.org/ And transformed from RDF format to MySQL database.

    The file dbDmozRdf2MySQL-Mon-Year.zip includes the full converted information from Dmoz Rdf file.

    The file dbDmozRdf2MySQL_Topics(Categories)Structure.zip includes only one table: tTopics, which contains DMOZ structure from the most recent dbDmozRdf2MySQL-Mon-Year.zip file. The MySQL scripts (see below) are updated to load that single table.

  3. This zip also contains two MySQL scripts which restore the database. Both scripts should be run from mysql client. But BEFORE running, they should be slightly adapted according to user specific environment.
    One needs to have some MySQL programming skills to change these scripts.

  4. The first script (it should be run the first!): DumpCreateTables.sql creates the database and tables and gives grants to some users. Here you should change database name and grants.
  5. The second DumpLoadTables.sql script loads data to created tables. It assumes the archive has been unzipped to folder:

    e:/MysqlBackup/dbDmozCopy/

    Here you should change the database name and replace all instances of above folder name to the full folder name where the archive has been really unzipped in your environment.

  6. Most table names are feeded from RDF tags: tTopics, tExtLinks, tTypes etc.
    Table field names are feeded from RDF attributes.
    Most tables have unique primary key id. By that key their records are referred by other tables.

    For example:
    tTopicLinks records are referred to:

    tTopics records by field idTopic,
    tExtLinks records by field idExtLink,
    tTypes records by field idType.

    Other tables are organized the same way.

    Of cause, one can define these derivative fields as KEY, to speed up database search.
    This dump is a raw RDF => MySQL conversion.
    One can modify it to meet his specific needs.
  7. For Term of use see: http://dmoz.org/termsofuse.html
    License information: http://dmoz.org/license.html
  8. If you find this conversion is useful, please, put the following back link in your site:
    Dmoz Rdf2MySQL Conversion by <a href="http://www.we-globe.net/WebLab/Download/">www.we-globe.net</a>
  9. The loading process has been tested on:
    WIN-XP SP2, Home edititon.
    MySQL - 5.0.21-community-nt
    4G Memory
    MySQL allocated 1G.
    Loading time 1 hour.
  10. IMPORTANT: before using the dump you should valide it's MD5 hash to one, published here
  11. Update history: here


The present conversion from RDF to MySQL is a we-globe.net private initiative. We-globe.net is NOT sponsored by and is NOT affiliated with DMOZ in any way.

The conversion may contain errors and the following disclaimer is valid:

Disclaimer / Limitation of Liability

WE MAKE NO REPRESENTATIONS AS TO THE ACCURACY, QUALITY, TIMELINESS, AVAILABILITY, OR COMPLETENESS OF THE INFORMATION, SOFTWARE, PRODUCTS, OR OTHER MATERIALS AVAILABLE THROUGH THE ODP, AND YOU SHOULD NOT RELY UPON THEM. WE PROVIDE THE ODP ON AN "AS IS, AS AVAILABLE" BASIS. YOU USE IT AT YOUR OWN RISK, AND NETSCAPE, ITS EMPLOYEES, DISTRIBUTORS, DIRECTORS, AND AGENTS ARE NOT LIABLE FOR ANY ERRORS OR OMISSIONS IN ITS CONTENT OR DELIVERY, OR FOR ANY FORM OF LOSS OR DAMAGE (INCLUDING ANY CONSEQUENTIAL, INDIRECT, INCIDENTAL, SPECIAL, OR EXEMPLARY DAMAGES, EVEN IF KNOWN TO US) THAT MAY RESULT FROM ITS USE. WE EXPRESSLY DISCLAIM ALL WARRANTIES, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. NO WARRANTY NOT SET FORTH IN THIS AGREEMENT WILL BE VALID. IF ANY OF THE ABOVE PROVISIONS ARE VOID UNDER GOVERNING LAW, OUR LIABILITY SHALL BE LIMITED TO THE EXTENT PERMITTED BY LAW.

Have, fun!

Update History (in reverse order)