Page History

...

Popular schemas such as XHTML suffer from the problem of not relating elements together explicitly. For example, if a heading precedes a paragraph, the heading is related to the paragraph not because it is encoded as such but because it happens to precede it. When these structures are attempted to be translated into formats where these types of relationships are explicit, the translation becomes tedious, and potentially problematic. More structured schemas, like TEI or DocbookDocBook, are domain specific (much like DRI itself) and therefore not suitable for our purposes.

...

A DSpace installation running Manakin may have several Themes associated with it. When applied to a page, a Theme determines most of the page's look and feel. Different themes can be applied to different sets of DSpace pages allowing for both variety of styles between sets of pages and consistency within those sets. The xmlui.xconf configuration file determines which Themes are applied to which DSpace pages (see the Chapter 7. Manakin \[DSDOC:XMLUI\] Configuration and Customization for more information on installing and configuring themes). Themes may be configured to apply to all pages of specific type, like browse-by-title, to all pages of a one particular community or collection or sets of communities and collections, and to any mix of the two. They can also be configured to apply to a singe arbitrary page or handle.

...

There were major structural changes between these two version numbers. Several elements were removed from the schema:includeSet, include, objectMeta, and object. Originally all metadata for objects were included in-line with the DRI document, this proved to have several problems and has been removed in version 1.1 of the DRI schema. Instead of including metadata in-line, external references to the metadata is included. Thus, a reference element has been added along with referenceSet. These new elements operate like their counterparts in the previous version except refrencing metadata contained on the objectMeta element they reference metadata in external files. The repository and repositoryMeta elements were alse modified in a similar mannor manner removing in-line metadata and refrencing external metadata documents.

...

<meta>

    <userMeta> ... </userMeta>

     <pageMeta>

        <metadata element="title">Examlpe>Example DRI
	page</metadata>

        <metadata
	element="contextPath">/xmlui/</metadata>

        <metadata ...> ... </metadata>

        ...

        <trail source="123456789/6"> A bread crumb item
	</trail>

        <trail ...> ... </trail>

        ...

     </pageMeta>

</meta>

...

reference is a reference element used to access information stored in an extarnal external metadata file. The url attribute is used to locate the external metadata file. The type attribute provides a short limited description of the referenced object's type.

...

The repositoryMeta element contains metadata refernces references about the repositories used in the used or referenced in the document. It can contain any number of repository elements.

...

<pageMeta>

    <metadata element="title">Examlpe>Example DRI
	page</metadata>

    <metadata
	element="contextPath">/xmlui/</metadata>

    <metadata ...> ... </metadata>

    ...

     <trail target="/myDSpace"> A bread crumb item pointing to a
	page. </trail> <trail ...> ... </trail>

    ...

</pageMeta>

...

• target: (required) A target for the reference, using either a URL or an id of an existing element as a destination for the xref.

<p>

     <xref target="/url/link/target">This text is shown as a
	 link.</xref>

</p>