Automatic transformation of XML namespaces/RDF resource format/Grouping examples

This section is non-normative.

Consider the following syntaxes: &lt;a:section> &lt;a:title>...&lt;/a:title> ... &lt;/a:section>

and &lt;b:section> &lt;b:title>...&lt;/b:title> ... &lt;/b:section>

(It may be transformed in HTML with  elements.)

Consider two transformations between namespaces  and , which map corresponding elements from   to   and back.

But then the following would not work: &lt;a:section> &lt;b:title>...&lt;/b:title> ... &lt;/a:section> This means that both   and    namespaces are grouped by descendants. (That is an element may have meaning only together with its descendants.) It is conceivable to write: http://example.org/namespace/a a :GroupedWithDescendants. http://example.org/namespace/b a :GroupedWithDescendants.

Sometimes elements may be grouped even when neither is a descendant of the another: &lt;a:title>Test 1&lt;/a:title> ... &lt;a:title>Test 2&lt;/a:title> When converting this to HTML, chapter numbers may be added.

This is described as  class. This class is the default.

Probably most of XML formats should use  class but using   class by default is more safe.

So, a namespace is of  class if not explicitly specified.

is a subclass of  which in turn is a subclass of.