Global element and attribute declarations belong to this schema's target namespace.
By default, local element declarations belong to this schema's target namespace.
By default, local attribute declarations have no namespace.
Documentation
XSD Data File Information
-------------------------
Author: Prashant Nayak, Bruce Barton, Colin Smythe
Date: 28th February, 2006
Version: 1.0
Status: Final Release
Description: Deployment descriptor for ProxyToolDeployment.
History: Version 1.0: This is is the first full release of this data model.
Copyright: 2005 (c) IMS Global Learning Consortium Inc. All Rights Reserved.
IMS Global Learning Consortium, Inc. (IMS) is publishing the information
contained in this binding ("Specification") for purposes of scientific
experimental and scholarly collaboration only. IMS makes no warranty or
representation regarding the accuracy or completeness of the Specification.
This material is provided on an "As Is" and "As Available basis".
The Specification is at all times subject to change and revision without
notice. It is your sole responsibility to evaluate the usefulness, accuracy
and completeness of the Specification as it relates to you. IMS would
appreciate receiving your comments and suggestions. Please contact IMS
through our website at: http://www.imsglobal.org.
Source XSLT File Information
----------------------------
XSL Generator: UMLtoXSDTransformv0p7.xsl
XSLT Processor: Xalan
Release: 1.0 Beta 1
Date: 30th November, 2005
Auto-generation Tool
--------------------
This WSDL/XSD was auto-generated using the IMS WSDL/XSD auto-generation tool. While every attempt
has been made to ensure that this tool auto-generates the XSDs correctly, users should be aware
that this is an experimental tool. Permission is given to make use of this tool. IMS makes no
claim on the materials created by third party users of this tool. Details on how to use this tool
are contained in the IMS document: "IMS General Web Services: WSDL/XSD Binding Auto-generation"
available at the IMS web-site.
Tool Copyright: 2005 (c) IMS Global Learning Consortium Inc. All Rights Reserved.
<ContextualProfile Required="xs:boolean[1]" ContextualProfileType="xs:string (value comes from list: {'SimpleUserProfile'|'DeliveryContextProfile'|'AcclipContextProfile'})[1]"/>
<OutcomeProfile Required="xs:boolean[1]" Preference="xs:integer[1]" OutcomeProfileType="xs:string (value comes from list: {'MinimalOutcomeProfile'|'SimpleOutcomeProfile'})[1]"/>
<SecurityProfile Required="xs:boolean[1]" Preference="xs:integer[1]" SecurityProfileType="xs:string (value comes from list: {'SharedSecretProfile'})[1]"/>
One or more contextual profiles for this deployment profile.
Profiles are defined in imsti_pts schema. For each profile
the required flag has to be specified as well as the
ContextualProfileType attribute as defined in the
ims_pts_v0p1 schema
XML Instance Representation
<... Required="xs:boolean[1]" ContextualProfileType="xs:string (value comes from list: {'SimpleUserProfile'|'DeliveryContextProfile'|'AcclipContextProfile'})[1]"/>
The schema for a deployment type. This will include the core
settings (required) and (optional) contextual/security/outcome
profiles and the tool specific settings. Each ProxyTool deployment
will allow one to many deployment profiles
The supported types of outcome profiles.
These are referenced in the deployment
descriptor schema by the OutcomeProfile
element
XML Instance Representation
<... Required="xs:boolean[1]" Preference="xs:integer[1]" OutcomeProfileType="xs:string (value comes from list: {'MinimalOutcomeProfile'|'SimpleOutcomeProfile'})[1]"/>
One or more security profiles for this deployment profile.
Profiles are defined in imsti_pts schema. For each profile
the required flag and preference order have to be specified
as well as the SecurityProfileType attribute as defined in
the ims_pts_v0p1 schema
XML Instance Representation
<... Required="xs:boolean[1]" Preference="xs:integer[1]" SecurityProfileType="xs:string (value comes from list: {'SharedSecretProfile'})[1]"/>
A documented settings definition consists of a documentation block
that describes for administrators and users the use of the settings,
a schema or schemas that can be used to validate an instance of
the settings, and setting instance that includes default settings values.
A simple security profile for a shared secret that is used to
calculate a MD5 digest of an element in the launch or outcome
message, e.g. messageIdentifier.
XML Instance Representation
<... Required="xs:boolean[1]" Preference="xs:integer[1]" SecurityProfileType="xs:string (value comes from list: {'SharedSecretProfile'})[1]">
Any 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.
The extension has a definition of "lax" i.e. they can reuse elements from the target namespace.
XML Instance Representation
Allow any elements from a namespace other than this schema's namespace (lax validation). [0..*]
The XML Instance Representation table above shows the schema component's content as an XML instance.
The minimum and maximum occurrence of elements and attributes are provided in square brackets, e.g. [0..1].
Model group information are shown in gray, e.g. Start Choice ... End Choice.
For type derivations, the elements and attributes that have been added to or changed from the base type's content are shown in bold.
If an element/attribute has a fixed value, the fixed value is shown in green, e.g. country="Australia".
Otherwise, the type of the element/attribute is displayed.
If the element/attribute's type is in the schema, a link is provided to it.
For local simple type definitions, the constraints are displayed in angle brackets, e.g. <<pattern = [1-9][0-9]{3}>>.
If a local element/attribute has documentation, it will be displayed in a window that pops up when the question mark inside the attribute or next to the element is clicked, e.g. <postcode>.
Abstract(Applies to complex type definitions and element declarations). An abstract element or complex type cannot used to validate an element instance. If there is a reference to an abstract element, only element declarations that can substitute the abstract element can be used to validate the instance. For references to abstract type definitions, only derived types can be used.
Collapse Whitespace PolicyReplace tab, line feed, and carriage return characters with space character (Unicode character 32). Then, collapse contiguous sequences of space characters into single space character, and remove leading and trailing space characters.
Disallowed Substitutions(Applies to element declarations). If substitution is specified, then substitution group members cannot be used in place of the given element declaration to validate element instances. If derivation methods, e.g. extension, restriction, are specified, then the given element declaration will not validate element instances that have types derived from the element declaration's type using the specified derivation methods. Normally, element instances can override their declaration's type by specifying an xsi:type attribute.
Nillable(Applies to element declarations). If an element declaration is nillable, instances can use the xsi:nil attribute. The xsi:nil attribute is the boolean attribute, nil, from the http://www.w3.org/2001/XMLSchema-instance namespace. If an element instance has an xsi:nil attribute set to true, it can be left empty, even though its element declaration may have required content.
Prohibited Derivations(Applies to type definitions). Derivation methods that cannot be used to create sub-types from a given type definition.
Prohibited Substitutions(Applies to complex type definitions). Prevents sub-types that have been derived using the specified derivation methods from validating element instances in place of the given type definition.
Replace Whitespace PolicyReplace tab, line feed, and carriage return characters with space character (Unicode character 32).
Substitution GroupElements that are members of a substitution group can be used wherever the head element of the substitution group is referenced.
Substitution Group Exclusions(Applies to element declarations). Prohibits element declarations from nominating themselves as being able to substitute a given element declaration, if they have types that are derived from the original element's type using the specified derivation methods.
Target NamespaceThe target namespace identifies the namespace that components in this schema belongs to. If no target namespace is provided, then the schema components do not belong to any namespace.
