1. accessibility
| Explanation | Size | Order | Value Space | Datatype |
| Root element that groups the accessibility information about the resource. | 1 | Unspecified | - | - |
Technical Implementation Notes
A container for the accessibility information as a whole.The sub-elements in this category are:
1.1 access mode statement
-
1.1.1 original access mode 1.1.2 access mode usage
1.2 control flexibility 1.3 has control flexibility 1.4 display transformability 1.5 has display transformability 1.6 hazard 1.7 has alternative 1.8 has component 1.9 alternative
-
1.9.1 is alternative to 1.9.2 coverage
1.10 is display transformability of 1.11 is control flexibility of 1.12 is component of 1.13 adaptation statement
-
1.13.1 adaptation type 1.13.2 original access mode 1.13.3 coverage
1.13.4 representation form 1.13.5 language 1.13.6 reading rate 1.13.7
education level
1.14 support tool
Text Example
Accessforall:-
Accessmodestatement:
-
Originalaccessmode:
auditory
-
Accessmodeusage
informative
-
Controlflexibility
full keyboard control
-
Hascontrolflexibility
-
LOM identifier:
-
LOM catalog: URI LOM enrty: http://www.hascontrolflexibilitystatement.com
font size
-
Hasdisplaytransformability:
-
LOM identifier:
-
LOM catalog: URI LOM enrty: http://www.hasdisplaytransformability.com
flashing
-
Hasalternative:
-
LOM: identifier
-
LOM catalog: URI LOM entry: http://www.somewhere.org/captions_en/mcluhan.mov
-
Hascomponent:
-
LOM identifier:
-
LOM catalog: URI LOM entry :
-
Isalternativeto: LOM: Identifier
-
LOM catalog: URI LOM entry: http://www.somewhere.org/mcluhan.mov
all
-
Isdisplaytransformabilityof:
-
LOM: Identifier
-
LOM catalog: URI LOM entry: http://www.url.to.resource.being.described.com
-
LOM: Identifier
-
LOM catalog: URI LOM entry: http://www.url.to.resource.being.described.com
-
LOM: Identifier
-
LOM catalog: URI LOM entry: http://www.url.to.compound.resource.com
-
Adaptationtype:
audio representation
-
Originalaccessmode:
auditory
-
Coverage:
part
-
Representationform:
verbatim
-
Language:
eng-CA
-
Readingrate:
60
-
Education level:
undergraduate university
-
Supporttool:
spell checker
XML Example:
<accmd:accessforall>
-
<accmd:accessmodestatement>
-
<accmd:originalaccessmode>auditory</originalaccessmode>
<accmd:accessmodeusage>informative</accessmodeusage>
<accmd:hascontrolflexibility>
-
<
![[LOM]](CancoreAccessForAllMetadataGuidelines_2faccessibility_files/moin-inter.png){kind=small}
identifier>
</identifier>
</accmd:hascontrolflexibility>
-
<accmd:displaytransformability>font size</displaytransformability> <accmd:hasdisplaytransformability>
</accmd:hasdisplaytransformability>
-
<accmd:hazard>flashing</hazard> <accmd:hasalternative>
-
<
identifier>
</identifier>
-
<accmd:isAlternativeTo>
<accmd:coverage>all</coverage>
<accmd:isdisplaytransformabilityof>
-
<
identifier>
</identifier>
</accmd:isdisplaytransformabilityof> <accmd:iscontrolfexibilityof>
-
<
identifier>
</identifier>
</accmd:iscontrolfexibilityof> <accmd:iscomponentof>
-
<
identifier>
</identifier>
</accmd:iscomponentof>
-
<accmd:adaptationstatement>
-
<accmd:adaptationtype>audio
representation</accmd:adaptationtype>
<accmd:originalaccessmode>auditory</accmd:originalaccessmode>
<accmd:coverage>part</accmd:coverage>
<accmd:representationform>verbatim</accmd:representationform>
<accmd:language>eng-CA</accmd:language>
<accmd:readingrate>60</accmd:readingrate>
<accmd:education level>undergraduate
university</accmd:education level>
</accmd:accessforall>
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:
why do we have the complicated URIs in our examples? surely we just want a straight URI of the kind http://.....?
Liddy
Because you don't want to exclude ISBN, ISSN, DOI, etc. Strictly speaking those are not URIs. We want to be inclusive here and say that any standard way of referencing resources can be used. The LOM does this nicely by using a structure that allows one to explicitly state the referencing technique (catalog), and then the actual encoding of the identifier (entry). Dublin Core provides another standard way of accomplishing this, but I don't know the details.
However, this does raise an issue of how to reflect this in our examples. Maybe we should create a generic <resourceReference> element that indicates that lom.identifier, dc.identifier, etc. can be used here to reference a resource.
Joseph
A thought about the complete example of the accessibility element. The ![[WWW]](CancoreAccessForAllMetadataGuidelines_2faccessibility_files/moin-www.png){kind=small}
CanCore LOM guidelines do not actually list an example for the root element (lom). Instead, it provides a "chapter" for each of the major categories (General, Lifecyle, Technical, etc.).
There is wisdom in this since a full example can be quite lengthy and one can get lost in its complexity. Perhaps a similar approach could be used here in that the documentation of accessiblity simply state that it is a container of the other elements, and then list them to show a skeletal structure. The reader can then go to each of them for the details on that element.
Joseph