Locating Content

In order to facilitate the automatic location of content we extend Sitemap protocol with a new namespace xmlns:ocx that introduces following tags:

Tag	Type	Required	Description
`ocx:type`	Text \| URL	required	Indicates that the URL has OCX compatible content and giving information on specific OER type used to describe the content. Accepted values are existing OER schema or schema.org types or well-defined, publicly available, not-yet-accepted sub-types of schema.org types.
`ocx:format`	Text	optional	The expected format of content metadata. Purpose of this tag is to allow [crawlers] to further filter sitemap URLs and crawl only pages that have relevant metadata and have it in a format [crawler] is capable of processing. Accepted values: `JSON-LD`, `Microdata` and `RDFa`
`ocx:loc`	URL	optional	Provide the URL where metadata is located. Unless metadata is placed on a web page different from content page, this tag can be skipped.
`ocx:xpath`	Text	optional	Provide where exactly the metadata is located inside document. The value should be a `HTML XPath`
`ocx:name`	Text	optional	Resource name or title
`ocx:teaser`	Text	optional	Small text describing the resource content or objective
`ocx:parent`	Text \| URL	optional	identifier or URL (`loc`) for the parent resource.
`ocx:image`	URL	optional	An image or thumbnail for the resource.

This extended sitemap namespace might be included in a site’s main /sitemap.xml file or it might be included in a dedicated sitemap-structured file (index) with a different name such as /ocx.xml.

Each sitemap file that you provide must have no more than 50,000 URL elements. Keep in mind that if you are adding optional tags, you may hit the 50MB uncompressed limit before you hit the 50,000 entries limit.
If you want to list more than 50,000 URLs, you must create multiple Sitemap files then list each of them in a Sitemap index file (sitemaps does not support nesting of index files).
Make sure that your robots.txt file isn’t blocking any of the items included in each sitemap entry
Prefer using full URLs, i.e. locations for content or landing-pages that require ‘hash marks’ or fragment identifier are discouraged

Sitemap Basics

The documentation at Sitemap.org is straightforard and worth reading for any web developer or publisher; here we will give a minimal definition of the protocol and highlight the elements most relevant for publishing curriculum.

A sitemap at its most simple is an XML file that is available at the root URL of a website (e.g. https://www.google.com/sitemap.xml), which tells automated web crawlers what web pages are accessible on the site. Like OCX, the sitemap format is a recommended convention rather than a global specification; however, it has become a de facto standard thanks to adoption among the top search engine (e.g. Google, Microsoft, and Yahoo!). The bare minimum sitemap file would contain nothing more than a list of site URLs, marked up with the appropriate XML tags, e.g.:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
   <url>
      <loc>http://www.example.com/</loc>
   </url>

   <url>
      <loc>http://www.example.org/about-example.html</loc>
   </url>
</urlset>
</xml>

As you can see, each URL in the sitemap has a <loc> tag which describes its location on the web. There are three additional (optional) tags which can describe each URL in the sitemap, and those will be covered below.

Sitemap Conventions for Open Curriculum

While web-crawling “robots” will crawl all public URLs on your site whether or not they are specified in the sitemap (indeed, whether or not the site has a sitemap), you cannot assume the same from the robotic consumers of your curriculum via the OCX manifest. In most cases, those consumers are only interested in the curriculum content and will not attempt to crawl your site for any other reasons. Therefore, it’s critical that the OCX manifest include all of the URLs relevant to the curriculum, whether those URLs are included in the main sitemap.xml file on your site or in a sitemap dedicated to the curriculum section of your site.

In addition to the <loc> tag, the sitemap protocol supports three additional (optional) tags to describe a given URL: <lastmod>, <changefreq>, and <priority>. All of these elements are important for helping consumers stay up to date with changes to the curriculum.

<lastmod> - The lastmod tag identifies when the content at the URL was last updated. The <lastmod> value for each URL should reflect changes to the curriculum’s content at that URL, rather than the HTML page at that URL; this means it should only be included if you are able to reliably track those changes.
<changefreq> - The changefreq tag identifies an estimated frequency for changes to the content. In most cases, K-12 curriculum materials are only significantly changed once per year, aside from corrections and minor wording changes, and consumers of that curriculum will typically be familiar with that same cycle. In those case, the <changefreq> tag will be unnecessary and/or difficult to estimate for most curriculum component URLS; however, any page which tracks the ongoing minor changes to that curriculum should be included in the OCX manifest and described with a sensible <changefreq> value which reflects a realistic frequency of those changes. For example:
```
 <url>
    <loc>http://www.example.org/ela/grade-2/errata.html</loc>
    <changefreq>weekly</changefreq>
 </url>
```
<priority> - The priority tag defines a URL’s importance compared to the rest of the site. If you host multiple versions of a single curriculum, this tag may be used to de-emphasize the old version while still keeping it available for access.

Examples

Minimal example:

<?xml version="1.0" encoding="utf-8" ?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:ocx="http://sitemap.ocx.org/v/1.0">

  <url>
    <loc>http://example.com/</loc>
  </url>

  <url>
    <loc>http://example.com/articles/android-7-released</loc>
    <lastmod>2017-02-18T01:16:08.00-05:00</lastmod>
    <ocx:ocx>
      <ocx:type>http://oerschema.org/Lesson/</ocx:type>
      <ocx:format>JSON-LD</ocx:format>
      <ocx:xpath>/html/head/script[@type="application/ld+json"]</ocx:xpath>
    </ocx:ocx>
  </url>

  <url>
    <loc>http://example.com/resources/class-activities/7</loc>
    <lastmod>2017-05-15T03:30:08.00-05:00</lastmod>
    <ocx:ocx>
      <ocx:type>http://oerschema.org/Activity/</ocx:type>
      <ocx:format>RDFa</ocx:format>
      <ocx:loc>http://example.com/resources/class-activities/7</ocx:loc>
      <ocx:xpath>/html/body/main/section[@class="activity"]</ocx:xpath>
    </ocx:ocx>
  </url>
</urlset>

The manifest below uses sample data from UnboundEd:

  <url>
    <loc>http://pilot.unbounded.org/ela</loc>
    <lastmod>2017-08-14T06:04:13.98+00:00</lastmod>
    <ocx:ocx>
        <ocx:type>http://oerschema.org/Topic</ocx:type>
        <ocx:format>JSON-LD</ocx:format>
        <ocx:xpath>//script[@type="application/ld+json"]</ocx:xpath>
        <ocx:name>ELA Curriculum Map</ocx:name>
    </ocx:ocx>
  </url>
  <url>
    <loc>http://pilot.unbounded.org/ela/grade-2</loc>
    <lastmod>2017-08-14T06:04:46.30+00:00</lastmod>
    <ocx:ocx>
        <ocx:type>http://oerschema.org/Course</ocx:type>
        <ocx:format>JSON-LD</ocx:format>
        <ocx:xpath>//script[@type="application/ld+json"]</ocx:xpath>
        <ocx:name>Grade 2 English Language Arts</ocx:name>
        <ocx:teaser></ocx:teaser>
        <ocx:parent>http://pilot.unbounded.org/ela</ocx:parent>
    </ocx:ocx>
  </url>
  <url>
    <loc>http://pilot.unbounded.org/ela/grade-2/module-1</loc>
    <lastmod>2017-08-14T06:10:23.25+00:00</lastmod>
    <ocx:ocx>
        <ocx:type>http://oerschema.org/Module</ocx:type>
        <ocx:format>JSON-LD</ocx:format>
        <ocx:xpath>//script[@type="application/ld+json"]</ocx:xpath>
        <ocx:name>Listening and Learning</ocx:name>
        <ocx:teaser></ocx:teaser>
        <ocx:parent>http://pilot.unbounded.org/ela/grade-2</ocx:parent>
    </ocx:ocx>
  </url>
  <url>
    <loc>http://pilot.unbounded.org/ela/grade-2/module-1/unit-1</loc>
    <lastmod>2017-08-15T19:27:17.97+00:00</lastmod>
    <ocx:ocx>
        <ocx:type>http://oerschema.org/Unit</ocx:type>
        <ocx:format>JSON-LD</ocx:format>
        <ocx:xpath>//script[@type="application/ld+json"]</ocx:xpath>
        <ocx:name>Fairy Tales and Tall Tales</ocx:name>
        <ocx:teaser>Students are introduced to classic fairy tales and tall tales, and the lessons they teach.</ocx:teaser>
        <ocx:parent>http://pilot.unbounded.org/ela/grade-2/module-1</ocx:parent>
    </ocx:ocx>
  </url>
  <url>
    <loc>http://pilot.unbounded.org/documents/3</loc>
    <lastmod>2018-02-05T16:06:35.17+00:00</lastmod>
    <ocx:ocx>
        <ocx:type>http://oerschema.org/Lesson</ocx:type>
        <ocx:format>JSON-LD</ocx:format>
        <ocx:xpath>//script[@type="application/ld+json"]</ocx:xpath>
        <ocx:name>The Fisherman and His Wife</ocx:name>
        <ocx:teaser>Students will review characteristics of fairy tales.</ocx:teaser>
        <ocx:parent>http://pilot.unbounded.org/ela/grade-2/module-1/unit-1</ocx:parent>
    </ocx:ocx>
  </url>