Distributable Educational Material Markup LanguageTM


First Alpha version of schema published.

Though it is still rough and only covers the fundamental constituents of a DEMML™ topic, the DEMML_0.1 schema is available for viewing here.

Created DEMML™ blog site.

It took me a while to get around to creating a blog but it is finally up. (Updated July 8, 2009)
click here...

Added new Features and Benefits page.

DEMML is truely unique but I seem to have a hard time getting people to see that. Hopefully this will help. (Updated Dec. 10, 2007)
full story...

New Powerpoint about Communications Systems

full story...


How DEMML™ was Invented

Necessity truly is the mother of invention.
full story...

DEMCS™ Basics / Background

Storing Content: basic storage methods

In order to understand why certain decisions were made when designing the DEMCS™ it is important to understand the why certain other decisions were made in relation to the way DEMML™ content is stored. There are two basic ways that data can be stored: in a database or as separate files simply stored on a hard drive.


A database is a system where lots of individual bits of data are put together in one file or a limited set of really large files in a very organized system of tables with certain fields used to relate one table to another. This system can be indexed in multiple ways so that data can be found based on specific fields within the data. Once the indexes are created, finding things can be very fast, as long as the appropriate indexes have already been built. Each additional index increases the amount of work that the database software - often called a "database engine" - must do. The data can also be presented in multiple different ways depending on the needs of the user. Unfortunately, databases also require special, proprietary software to present that data. When there is a lot of data and it is on a server being accessed by lots of people, that "database engine" software must be very robust and powerful which can make it very expensive to create or maintain.

Many web sites are actually databases with a web based front end. When the user searches for all the ink-jet printers on a shopping web site, a database engine is retrieving all the matching items from its database and sending that data to another program which then sends it out to the user in the form of a temporary, custom-made web page. This requires a lot of complicated, expensive, customized software that must work correctly all the time or the user can't do their shopping.

A wiki is another example of a database with a web based front end. When a user edits a wiki they are not editing the web site directly. They are editing a form which is sent to software which deciphers which parts of the content the user edited, then sends those changes to a database which stores them along with all the other changes made by all the other users. The final version of that article is built up from all the changes made by all the users. This software is usually very robust and has become very popular. But it is still a database with all the problems that come along with maintaining a database.

The main problem with a database is that users must have access to the database engine in order to use the content in any meaningful way. Yes, one can cut and paste from a web page presented by a wiki but that data then becomes nothing more than text marked up with some html. It has lost all context and any metadata that may have been associated with that content within the back-end database. A user can't just copy a part of the database to their computer and use it in the same way it was used within the database.

Finally, if you want to add more types of data to a database, you must redesign the database and convert all of the existing data, even if none of that data will use the additions. This can be a huge, costly, and time-consuming process.

To sum up, a database:


In contrast to a database system, simply placing files in folders is very simple to do and maintain. Basically, the files just sit there. The only "maintenance" that is required is simply backing up the files on a regular basis. But even this is far simpler and less expensive than backing up a database.

Why DEMML™ uses Files-in-Folders

Databases can be incredibly useful and powerful. Otherwise they wouldn't have been invented in the first place. But a database of the magnitude required to hold all the educational material in the world would be quite a behemoth. It would require loads of processing power and significant people and brain power to keep it running. Either all the students in the entire world would have to access the data on the same server or special software would have to be devised to copy subsets of database to other servers. Then, custom software would need to be created just to display the data to students either through their web browsers or using software on their desktops. If the structure of the data changed then all of that software would have t be redesigned as well. Finally, students wouldn't be able to simply copy files in order to acquire new content to study.

By using the basic files-in-folders storage system, DEMML™ allows simple servers to distribute content and it allows the most flexibility in how that content is distributed. Users can keep that content on a thumb-drive and easily share that content with others. Content can be e-mailed, or even just cut and pasted from a web site.

The final and very important reason for using the files-in-folders data storage method, is that a strictly enumerative classification system can also be used as the naming system for all the folders in the file system. If a user wants to know where to store a particular file, all they need to do is look at the classification code for the content in the file. If they want to know the classification code for a file or set of files (which are already in their correct locations), all they have to do is look at the path name for the current folder. This consistency is very important for the long term usability of the DEMML™ system.

Next: DEMCS™ tree structure...

First Published: May 15, 2007 — Last Modified: May 15, 2007
DEMML Logo  About Us | Contact Us | ©2010 Grant Sheridan Robertson