Tag Archives: Metadata

Fun Tech Stuff: Going Under the Hood with XML

Posted on by

Here’s the complete series of related posts (in order) on going under the hood with XML and its uses in learning technologies. Click on each to see the full post.

An LMS, or Learning Management System is a software application that provides a framework for the course material, and takes care of all the back-end administration that is necessary to make the learning experience happen.

SCORM stands for “Sharable Content Object Reference Model,” and is a set of technical standards that define how Web-based online learning content and LMSs communicate with each other.

The Tin Can application programming interface, or API, (also known as The Experience API or xAPI) is the next generation of SCORM. It can capture formal as well as informal and social learning and performance as it actually happens, inside our outside an LMS or Web environment.

Metadata is information about information, typically describing a data resource (e.g., a Web page, an image, a document, an e-learning module, an ebook) by specifying information about it (e.g., creation, purpose, structure) to provide context and improve meaning, and help evolve the semantic Web.

XML is the workhorse of metadata and the semantic Web, the means by which we describe the meaning and context of information on the Web. XML stands for eXtensible Markup Language. It pops up all over the place, specifying contents and navigation in elearning, in ebooks, and on the Web.

Here are examples of the use of XML in SCORM and XML in eBooks.

XML Part 3: Ebook Example

Posted on by

This is last in a series of related posts on Fun Tech Stuff going under the hood with XML and its uses in learning technologies: Learning Management Systems, SCORM, Tin Can, Metadata, and XML, as well as examples of XML in SCORM and XML in eBooks.

Most ebooks, including the Kindle (with minor proprietary variations), are based on the open, XML-based EPUB standard. And what does an EPUB ebook look like on the inside? Believe it or not, it is essentially a zip file. And if you unzip it, you will find a folder with a whole set of other files and folders filled with XML files, XHTML files (a stricter version of HTML), image files, and maybe even sound and video files. All these files are stitched together—you guessed it—through the magic of XML, doing it’s semantic job of providing meaning and context to all that surround it.

One of the key files in an ebook is the content.opf file. It tells the ebook reader (e.g., your iPad or Kindle) what the book is, and how to navigate through it.

Let’s take a peek inside.

1. Yay! The file starts with a line that identifies it as an xml file.

2. The next line defines it as a package file, as defined by the Open Packaging Format bit of the EPUB standard.

3. Next comes the metatada section. Notice the “dc:”? That refers to the Dublin Core metadata standard discussed in our previous Metadata post.

4. Next comes the manifest, with its list of all the files that make up the ebook.

5. Finally comes the spine, which tells your ereader the order in which the content should be presented.

content-opf

And those are just a few of the ways in which XML helps people and computers work more closely together to improve the meaning and the context of information.

XML Part 2: SCORM Example

Posted on by

This is next in a series of related posts on Fun Tech Stuff going under the hood with XML and its uses in learning technologies: Learning Management Systems, SCORM, Tin Can, Metadata, and XML, as well as examples of XML in SCORM and XML in eBooks.

As you recall from our previous post, SCORM is a set of technical standards that define how Web-based online learning content and LMSs communicate with each other. SCORM is composed of three sub-specifications, one of which is the content packaging section, which contains an XML file called imsmanifest.xml. The XML manifest file describes how the parts of the course are organized, and lists the associated resources.

Note the following in the example below:

1. The file starts with a line that identifies it as an xml file.

2. The next line defines it as a manifest file (i.e., a file that lists contents).

3. Next comes the metadata tag, describing the list as part of the SCORM standard, version 1.2.

4-5. What follows is the heart of the manifest, defining the learning module items and their titles, and the related resources (e.g., files).

imsmanifest

Thanks to the imsmanifest file and rest of the information defined in SCORM’s XML files and APIs, any LMS that supports the SCORM standard can successfully store, display, and track any Web-based online learning content written to the same standard. The metadata in the XML files discloses the meaning and context of the information in the elearning modules, and the LMS processes it as appropriate.

In our next post, we’ll look at one more example of how XML is used to create the metadata that describes the meaning and context of information, this time in an ebook.

 

XML Part I: Markup Language

Posted on by

This is next in a series of related posts on Fun Tech Stuff going under the hood with XML and its uses in learning technologies: Learning Management Systems, SCORM, Tin Can, Metadata, and XML, as well as examples of XML in SCORM and XML in eBooks.

XML is the workhorse of metadata and the semantic Web, the means by which we describe the meaning and context of information on the Web. XML stands for eXtensible Markup Language. It pops up all over the place, specifying contents and navigation in elearning, in ebooks, and on the Web.

XML is a markup language much like HTML (HyperText Markup Language), the language we use to display the words, pictures, sounds, and video that make up the Web.

Markup Languages

What is a markup language? It is a system of rules and hidden tags (i.e., labels) that let us define how data can be stored, displayed, or processed. It is quite powerful but quite simple in structure. It’s based on plain text and designed to be readable by both humans and machines.

Here’s a simple example of HTML markup.

Let’s say you want your Web page to display a heading and a few short paragraphs. You want it to say this:

html example

So you would mark it up as follows, using angle brackets (< >) and tags to tell the browser how you’d like the text displayed:

<H1>Hopeless Optimist</H1>

<p>Being a hopeless optimist, I think the Chicago White Sox are going to win the World Series this year! People may laugh, but I have hope. </p>

<p>That is the meaning of being an optimist. </p>

As you can see, this is not rocket science! The <H1> tag indicates where the heading should start, and the </H1> indicates where the heading should end. Likewise, the <p> and </p> tags indicate where the paragraphs should start and end.

The basic scheme is as follows:

< tag>
…
< / end tag>

Of course there are lots of tags, and lots of complexity in how those tags can be used and nested, but the underlying scheme is straightforward.

HTML and XML

HTML and XML are similar in nature, both being markup languages, but they have a couple of key differences.

First, HTML is designed to tell Web browsers how to display data; it’s all about marking up text and other assets like images, sound, and video, so the browser knows how to format it: make it a heading, make it bold, put it in a table, turn it into bullet points, make it so tall or so wide, break a paragraph, skip a line. Second, the tags you use to mark up your words and pictures are all predefined; you have to use the right tags if you want to get the right result. If you said:

<Heading1>Hopeless Optimist</Heading1>

instead of:

<H1>Hopeless Optimist</H1>

the browser wouldn’t know what you were talking about, and would not display your heading correctly. HTML is an open standard. And while it is constantly evolving, it is well known to both Web developers and browser developers, so generally what we code is rendered properly.

XML, on the other hand, is not designed to display data, it’s designed to provide meaning and context for data, so the markup is used to do that.

Meaning and Context

In our previous Metadata post, we gave an example of a person using a Web site that contains a monument’s latitude and longitude so that person can locate the monument while walking through a park. The latitude and longitude would be defined in the Web site with XML tags that might look something like this:

<geo:Point>
<geo:lat>41.882406</geo:lat>
<geo:long> -87.62382 </geo:long>
</geo:Point>

XML provides meaning and context for data, and provides it using plain text, so it can be easily written and read by any application (as well as by people).

Not Predefined

Also, XML tags are not predefined; you or an outside organization can define the meaning of the tag and link to its definition. The meaning and context of the data is conveyed both by the tag itself and by the linked definition of the tag, called an XML Name Space (xmlns).

< … xmlns:geo=”http://www.w3.org/ …>

Tags define the data, and name spaces define the tags:

xml tags and name space

Of course the point is not to learn how to code XML, but to understand its power, and how it is used under the hood in Web sites, in e-learning delivery (e.g., SCORM), and in ebooks, all of which are key to the future of learning.

In the next two posts, we’ll look at a couple of examples of how XML is used, first in SCORM, and then in an ebook, to create the metadata that describe the meaning and context of that information.

 

What is Metadata

Posted on by

This is next in a series of related posts on Fun Tech Stuff going under the hood with XML and its uses in learning technologies: Learning Management Systems, SCORM, Tin Can, Metadata, and XML, as well as examples of XML in SCORM and XML in eBooks.

Metadata is information about information. Metadata typically describes an information resource (e.g., a Web page, an image, a document, an e-learning module, an ebook) by specifying its creation, purpose, author, location, and any other data helpful in utilizing it. For example, an image may contain information about its size and resolution, and a document may contain information about its length. Both the SCORM and Tin Can specifications are at heart metadata, since they define how to specify information (e.g., module structure, navigation) about a resource (e.g., the e-learning course) in an organized fashion.

Early Metadata

Metadata is not a new concept; librarians have been using it for years in card catalogs to manage their book collections. Almost every book on the market in the United States today has metadata associated with it in the form of Library of Congress Cataloging-in-Publication information, including author, title, ISBN, subject category and subcategories, number of pages, length of the physical book, Library of Congress Control Number, and cataloging numbers.

Card Catalog
Early Metadata

Unlike the card above, of course, today this information lives in servers and is easily searchable, not only because it’s computerized, but because the Library of Congress previously defined the types of information it thought necessary to collect about each book, allowing searches within a specific category. For example, if you wanted to find a book by an author named Joe Homer, you could search on “author,” and skip all the other books about the Greek poet Homer, the books about Homer Simpson, and books about famous home runs in baseball history. Just specifying that the word Homer is a part of the author’s name, and not a part of a title or a subject, makes your search that much more effective. Thus, a key component of any type of metadata is a specification of the individual types of information to be collected, and a definition of each.

Metadata on the Web

Wouldn’t it be nice if the Web itself had a real digital card catalog and not just a brute force text search, which often returns completely irrelevant (and occasionally quite entertaining) results? There actually are some starting to appear. A number of groups have developed and continue to evolve standards for the incorporation of metadata into Web sites. One of the first is called the Dublin Core Metadata Initiative; two other current standards of interest are Microformats and RDFa.

Let’s take a look at the Dublin Core. It is a set of descriptors that can be used to specify information about Web resources (e.g., video, images, Web pages) as well as books, CDs, and artworks. It consists of information about the resource’s content, intellectual property data, and version:

  • Content information—Title, Subject and Keywords, Description, Resource Type (e.g., image, sound, text), Source, Relation (i.e., related resource), and Coverage (i.e., time period)
  • Intellectual Property information—Creator, Publisher, Contributors, and Rights Management (e.g., copyright)
  • Version information—Date, Format, Resource Identifier (e.g., URL), Language, Audience, Provenance, Rights Holder, Instructional Method, and data about how the resource has changed

Metadata standards such as the Dublin Core not only specify searchable types of information about a resource, they contain a clear definition of that information. A Dublin Core date, for example, is defined as YYYY-MM-DD, so 2014-03-09 means March 9th, not September 3rd. While this may appear trivial, the automated search of metadata by computers requires that the exact meaning of each data element be agreed upon, documented, stored on the Web, and linked to, so it is obvious what metadata definitions are being utilized.

Metadata and the Semantic Web

What’s the purpose of all of this metadata? One purpose is to help computers better understand the meaning behind a Web resource, so that they can do a better job helping you find what you want. Let’s say you do a search for the term “Chicago Fire.” Are you looking for the TV show, the conflagration that burned down the city in 1871, or the Chicago Fire soccer club? If a Web page contained information that better specified its meaning by noting that the Web page was about an event that occurred at a specific time (i.e., 1871), and the search engine was able to take advantage of it, then your search would return a much more meaningful set of results.

Another purpose of metadata is to enable computers to better communicate with one another as they do our bidding. Let’s say you are looking for the location of a monument in a park. If a Web site that contained that monument’s information also contained its precise latitude and longitude (e.g., 41.882406, -87.62382), that would be great, but your app would not necessarily know that those two numbers meant latitude and longitude. With the proper metadata—often just simple text tags in the Web site code—your app could then recognize and utilize that information, and present you with a map that showed the monument’s location as well as your own. The simple addition of metadata describing the meaning and context of the information on a Web site can make a huge difference in its usefulness.

When Tim Berners-Lee, the inventor of the Web, speaks of the Semantic Web, this is what he means: people and computers working more closely together to improve the meaning and the context of the information on the Web. He envisions people creating metadata to disclose meaning and context, and computers cranking through that metadata, processing it as appropriate.

In our next post, we’ll look at how such meaning and context can be added via XML.