2012-01-05. Frozen archive - links may not resolve - see directory of files at MoinMoin wiki archive

> CancoreAccessForAllMetadataGuidelines/alternative

1.9: alternative

Explanation Size Order Value Space Datatype
A container that identifies a resource (hereafter the described resource) as an alternative to another referenced resource. The described resource presents all or some of the same intellectual content as the referenced resource. The sub-elements are used to identify the resource that the described resource is an alternative to, and the extent to which it functions as a replacement for the described resource. 0..1 Unspecified - -

Technical Implementation Notes

Subelements for alternative are as follows:

If this element is absent, the described resource is not known to be an alternative to any other resource.

A resource is the alternative of at most one other resource.

Vocabulary Recommendations

None.

Text Example

The following shows two cases. The first alternative is an example where the described resource is a captioned digital video, and can be used as a complete replacement of the same video that has no captions. The second alternative is a case where the described resource consists only of captions. It must describe itself as but a partial replacement for the full (uncaptioned) video.

Case where the described resource is a captioned version of a Mcluhan video:

is alternative to: http://www.somewhere.org/mcluhan.mov coverage: all

Case where resource is captions only, but for the Mcluhan video:

is alternative to: http://www.somewhere.org/mcluhan.mov coverage: part

XML Example

The following markup lists two cases. The first alternative is an example where the described resource is a captioned digital video, and can be used as a complete replacement of the same video that has no captions. The second alternative is a case where the described resource consists only of captions. It must describe itself as but a partial replacement for the full (uncaptioned) video.
<!-- Here is an IEEE-LOM example describing a captioned version of Mcluhan video --> 
<accmd:alternative>
  <accmd:isAlternativeTo>
    <LOM:identifier>
      <LOM:catalog>URI</catalog>
      <LOM:entry>http://www.somewhere.org/mcluhan.mov"</entry>
    </identifier>
  <accmd:coverage>all</coverage>
</accmd:alternative>

<!-- Here is an IEEE-LOM example describing a resource captions only, but for the Mcluhan video -->
<accmd:alternative>
  <accmd:isAlternativeTo>
    <LOM:identifier>
      <LOM:catalog>URI</catalog>
      <LOM:entry>http://www.somewhere.org/mcluhan.mov</entry>
    </identifier>
  <accmd:coverage>part</coverage>
</accmd:alternative>

Discuss This Page

Add your comments below by following the link Discuss This Page then editing and saving the page. Please identify yourself by adding your full name at the end of your comments in parenthesis and optionally, affiliation. Please do not edit comments from other participants.

Discussion so far:

Edit

You can return to the main page after saving edits by clicking here Please only edit things below this line
In the Tech. notes listing the sub-elements, I think the sub-elements of is alternative to (i.e. identifier, catalog and entry) should not be included. They are not technically sub-elements, as is alternative to is described as a character string, with recommendation to use the Repertoire of ISO/IEC 10646-1:2000 for the vocab. (Anastasia Cheetham, ATRC)

I don't know if this addresses your concern, but when I suggested we use the LOM Identifier structure, I was guided by the published CanCore guidelines. For example, go to http://www.cancore.ca/guidelines/CanCore_Guidelines_General_2.0.pdf, and scroll down to 1-5 where Identifier is documented. Identfier's value space and data type are unspecified, but both of Identifier's sub-elements, Catalog and Entry, have value space 'ISO/IEC 10646-1:2000', and data type 'character string'. I assumed that we are writing CanCore guidelines for accessibility metadata; hence, I thought we should be consistent with its existing guidelines. Even so, there is an error in defining the value space and data type of is alternative to as ISO/IEC 10646-1:2000', and 'character string', since these are for the Identfier sub-elements, not for the is alternative to (nor alternative) containers. I suspect other elements we have been working on that use Identifier are also putting the 'ISO/IEC 10646-1:2000' value space, and 'character string' at the wrong level.

(Joseph Scheuhammer, ATRC)


NOTE: the term 'alternative' is due to be changed to 'adaptation'.

This element is used to identify resources for which this resource or component is an adaptation.

Note: Typically, a resource may have any number of adaptations. They should be identified separately and described separately as they may need to be used separately to adapt or augment a resource.

Liddy