![]() |
IMS GLC Public Forums and Resources | ![]() |
| "Where the World's Leaders in Learning Converge"
join :
help :
calendar :
home
|
||
|
Latest News:
|
latest topics : statistics | |


|
Topic Title: Possible typo in imsmd_strict_v1p3.xsd LOM definition? Topic Summary: Created On: 02/25/2011 06:43 PM Status: Post and Reply |
Linear : Threading : Single : Branch |
Topic Tools
|
|
|
|
|
In the LOM schema imsmd_strict_v1p3.xsd the usage of the 'default="LOMv1.0"' seems to be consistently used on "source" elements when maxOccurs is always equal to 1 with one exception on on MetaMetadata.Type/metadataschema where there it is also set to the default of "LOMv1.0" but the maxOccurs is also "unbounded". I'm curious if the unbounded definition was a typo and should actually be maxOccurs=1?
|
|
|
|
|
|
|
|
|
Hi,
It is NOT a typo. The IEEE LOM spec states: For those LOM XML instances that are strictly conforming to this Standard, if the Metadata Schema element (metadataSchema) is present in a LOM XML instance, the element shall contain the value LOMv1.0, (i.e., <metadataSchema>LOMv1.0</metadataSchema> And the multiplicity for <metadataSchema>is unbounded. Colin S. ------------------------- Colin Smythe IMS GLC Chief Architect |
|
|
|
|
FuseTalk Standard Edition v3.2 - © 1999-2013 FuseTalk Inc. All rights reserved.