To post messages, you must join the IMS Public Community (free).   |   You also can also join the Common Cartridge Alliance.
IMS GLC Public Forums and Resources
Decrease font size
Increase font size
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 Topic Tools
View topic in raw text format. Print this topic.
 02/25/2011 06:43 PM
User is offline View Users Profile Print this message

Author Icon
jutter

Posts: 1
Joined: 02/25/2011

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?
 02/28/2011 04:29 PM
User is offline View Users Profile Print this message

Author Icon
colinsmythe

Posts: 142
Joined: 03/09/2009

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
Statistics
2936 users are registered to the IMS GLC Public Forums and Resources forum.
There are currently 0 users logged in.

FuseTalk Standard Edition v3.2 - © 1999-2013 FuseTalk Inc. All rights reserved.

By participating in the forum, you agree to the abide by forum rules. You can view the IMS GLC Privacy Statement