DRAFT XSD for IMS Content Packaging version 1.1 DRAFT Copyright (c) 2001 IMS GLC, Inc. 2000-04-21, Adjustments by T.D. Wason from CP 1.0.2001-02-22, T.D.Wason: Modify for 2000-10-24 XML-Schema version. Modified to support extension.2001-03-12, T.D.Wason: Change filename, target and meta-data namespaces and meta-data fielname. Add meta-data to itemType, fileType and organizationType.Do not define namespaces for xml in XML instances generated from this xsd.Imports IMS meta-data xsd, lower case element names. This XSD provides a reference to the IMS meta-data root element as imsmd:recordIf the IMS meta-data is to be used in the XML instance then the instance must define an IMS meta-data prefix with a namespace. The meta-data targetNamespace should be used. 2001-03-20, Thor Anderson: Remove manifestref, change resourceref back to identifierref, change manifest back to contained by manifest. --Tom Wason: manifest may contain _none_ or more manifests.2001-04-13 Tom Wason: corrected attirbute name structure. Was misnamed type. 2001-05-14 Schawn Thropp: Made all complexType extensible with the group.anyAdded the anyAttribute to all complexTypes. Changed the href attribute on the fileType and resourceType to xsd:stringChanged the maxLength of the href, identifierref, parameters, structure attributes to match the Information model.2001-07-25 Schawn Thropp: Changed the namespace for the Schema of Schemas to the 5/2/2001 W3C XML SchemaRecommendation. attributeGroup attr.imsmd deleted, was not used anywhere. Any attribute declarations that haveuse = "default" changed to use="optional" - attr.structure.req.Any attribute declarations that have value="somevalue" changed to default="somevalue",attr.structure.req (hierarchical). Removed references to IMS MD Version 1.1.Modified attribute group "attr.resourcetype.req" to change use from optionalto required to match the information model. As a result the default value also needed to be removedName change for XSD. Changed to match version of CP Spec Inclusions and ImportsAttribute Declarationselement groupsAny namespaced element from any namespace may be included within an "any" element. The namespace for the imported element must be defined in the instance, and the schema must be imported.