IMS ePortfolio XML Binding

Version 1.0 Final Specification

Copyright © 2005 IMS Global Learning Consortium, Inc. All Rights Reserved.
The IMS Logo is a registered trademark of IMS/GLC
Document Name: IMS ePortfolio XML Binding
Revision: 02 June 2005

Date Issued:	02 June 2005
Latest version:	http://www.imsglobal.org/ep/epv1p0/imsep_bindv1p0.html
Register comments or implementations:	http://www.imsglobal.org/developers/ims/imsforum/categories.cfm?catid=24
	IMS welcomes feedback on informing best practices for formulating portfolio packages: http://www.imsglobal.org/problemtracking/index.cfm
IPR and Distribution Notices Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the specification set forth in this document, and to provide supporting documentation. IMS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on IMS's procedures with respect to rights in IMS specifications can be found at the IMS Intellectual Property Rights web page: http://www.imsglobal.org/ipr/imsipr_policyFinal.pdf. Copyright © IMS Global Learning Consortium 2006. All Rights Reserved. If you wish to distribute this document or use this document to implement a product or service, you must complete a valid license registration with IMS and receive an email from IMS granting the license. To register, follow the instructions on the IMS website: http://www.imsglobal.org/specificationdownload.cfm. This document may be copied and furnished to others by Licensee organizations registered on the IMS website provided that the above copyright notice and this paragraph are included on all such copies. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to IMS, except as needed for the purpose of developing IMS specifications, under the auspices of a chartered IMS work group. Use of this specification to develop products or services is governed by the license with IMS found on the IMS website: http://www.imsglobal.org/ep/epv1p0/epv1p0speclicense.html. The limited permissions granted above are perpetual and will not be revoked by IMS or its successors or assigns. THIS SPECIFICATION IS BEING OFFERED WITHOUT ANY WARRANTY WHATSOEVER, AND IN PARTICULAR, ANY WARRANTY OF NONINFRINGEMENT IS EXPRESSLY DISCLAIMED. ANY USE OF THIS SPECIFICATION SHALL BE MADE ENTIRELY AT THE IMPLEMENTER'S OWN RISK, AND NEITHER THE CONSORTIUM, NOR ANY OF ITS MEMBERS OR SUBMITTERS, SHALL HAVE ANY LIABILITY WHATSOEVER TO ANY IMPLEMENTER OR THIRD PARTY FOR ANY DAMAGES OF ANY NATURE WHATSOEVER, DIRECTLY OR INDIRECTLY, ARISING FROM THE USE OF THIS SPECIFICATION. Please note that the British Standards Institute standard 8788, provisionally known as "UK Lifelong Learner Information Profile" and referred to in this specification, is under development by the BSI. For further information, please consult http://www.bsi-global.com/.

1. Introduction

This document is a part of the IMS ePortfolio specification. The binding details how the ePortfolio Information Model should be represented using XML schema and the IMS Content Packaging specification. Several XML schemas are included in the Specification and are referenced below. The ePortfolio Best Practice and Implementation Guide provides non-normative guidance on how to use the Binding and Information Model. For a conceptual overview of the ePortfolio Specification, please see section 1 of the Information Model [EP, 05a]. For a discussion of potential applications, see the Best Practice Guide, section 1 [EP, 05c]. For a definition of conformance to the ePortfolio Specification, see the Best Practice Guide, section 4 [EP, 05c].

1.1 Scope and Context

This document is the IMS ePortfolio Binding v1.0 specification. As such it will be used as the basis for the production of the following v1.0 documents:

IMS ePortfolio XML XSDs;
IMS ePortfolio Best Practice Guide [EP, 05c].

This Binding document describes how to express the ePortfolio Information Model in XML, and how to incorporate this XML data together with other media within a package for transport between systems using the IMS Content Packaging specification.

1.2 Structure of this Document

The structure of this document is:

2. Narrative Description of Portfolio Package Binding	The description of the use of the IMS Content Packaging specification for exchanging an ePortfolio;
3. Narrative Description of PortfolioPart Binding	The description of the elements and attribute used within the XML binding itself.

1.3 Nomenclature

DTD	Document Type Definition
CSS	Cascading Style Sheets
W3C	World Wide Web Consortium
XML	Extensible Mark-up Language
XSD	XML Schema Definition
XSL	Extensible Stylesheet Language
XSLT	XSL Transformations

1.4 References

[EP, 05a]	IMS ePortfolio Information Model v1.0, C.Smythe, D.Cambridge, IMS/GLC, June 2005.
[EP, 05c]	IMS ePortfolio Best Practice and Implementation Guide v1.0, C.Smythe, D.Cambridge, IMS/GLC, June 2005.
[RUBRIC, 05]	IMS Rubric Specification v1.0, C.Smythe, M.McKell, A.Cooper, IMS/GLC, June 2005.
[ACCLIP, 03]	IMS Learner Information Package Accessibility for LIP v1.0, M.Norton, J.Treviranus, IMS/GLC, June 2003.
[BUND, 01]	Using IMS Content Packaging to Package Instances of LIP and Other IMS Specifications, v1.0, B.Olivier, M.McKell, IMS/GLC, August 2001.
[CP, 04]	IMS Content Packaging, v1.1.4, C.Smythe, A.Jackl, IMS/GLC, October 2004.
[ES, 04]	IMS Enterprise Services v1.0, C.Smythe, IMS/GLC, July 2004.
[LIP, 01]	IMS Learner Information Package v1.0, C.Smythe, F.Tansey, R.Robson, IMS/GLC, March 2001.

2. Narrative Description of Portfolio Package Binding

2.1 Portfolio Packages

The Portfolio Profile of the IMS Content Package is shown in Figure 2.1. This shows the XSD that should be used to validate a Portfolio Package.

Figure 2.1 Portfolio Package profile of IMS Content Packaging.

The constraints applied to manifest of the IMS Content Package to create this portfolio profile are:

All of the extension points, including the extensions for attributes but excluding that for the <metadata> element, have been removed - these are not required in a Portfolio Package;
The multiplicity of the 'version' attribute for the <manifest> element has been changed from [0..1] to [1], i.e., made mandatory;
The multiplicity of the 'default' attribute for the <organizations> element has been changed from [0..1] to [1], i.e., it is mandatory;
The multiplicity for the <organization> element has been changed from [0..*] to [1], i.e., required single occurrence - only a single organization is required;
The multiplicity of the <title> element within the <organization> element has been changed from [0..1] to [1], i.e., a mandatory single occurrence;
The multiplicity of the <title> element within the <item> element has been changed from [0..1] to [1], i.e., a mandatory single occurrence;
The attributes 'isvisible' and 'parameters' on the <item> element have been removed - these are not required in a Portfolio Package;
The attribute 'structure' from the <organization> element has been removed - this is not required in a Portfolio Package;
The <dependency> element and its attributes have been deleted;
The multiplicity of the <file> element in the <resource> element has been changed from [0..*] to [1..*], i.e., made mandatory.

The further features required for the creation of a valid Portfolio Package XML instance are:

The value of the 'default' parameter must be set to the value of the 'identifier' attribute for the <organization>;
The title for the organization must be supplied;
The <organization> can have, at most, five <item> element children. Each of these <item> elements is used to refer to the five different content types for a Portfolio, i.e., the views, the presentations, the owners, the relationships, and the portfolioParts. The <organization> may have any combination of the four types but there is never more than one instance of each;
The structure of the <item> element for the views is:

The content for the <title> element is set as "Views";

Each of the views will be described using its own <item> child for which the corresponding <title> element will be used to supply the title of the view;

Each <item> that is used to identify a view resource must have the resource identifier value allocated to the 'identifierref' attribute of the <item> element;

The structure of the <item> element for the presentations is:

The content for the <title> element is set as "Presentations";

Each of the presentations will be described using its own <item> child for which the corresponding <title> element will be used to supply the title of the presentation;

Each <item> that is used to identify a presentation resource must have the resource identifier value allocated to the 'identifierref' attribute of the <item> element;

The order of multiple <item>s is indicative of the order of presentation, e.g., with multiple XSLs or CSSs;

The structure of the <item> element for the owners is:

The content for the <title> element is set as "Relationships";

Each of the relationships will be described using its own <item> child for which the corresponding <title> element will be used to supply the title of the relationship;

Each <item> that is used to identify a relationship resource must have the resource identifier value allocated to the 'identifierref' attribute of the <item> element;

The structure of the <item> element for the portfolioparts is:

The content for the <title> element is set as "PortfolioParts";

Each of the portfolioparts will be described using its own <item> child for which the corresponding <title> element will be used to supply the title of the view;

Each <item> that is used to identify a portfoliopart resource must have the resource identifier value allocated to the 'identifierref' attribute of the <item> element;

Each resource that is used to identify a portfoliopart XML instance will have the 'type' attribute declared to identify the type of portfoliopart, i.e.:

'imslip-Identification' for identification material conforming to IMS LIP;

'imslip-Accessibility' for products material conforming to IMS Accessibility;

'imslip-Activity' for activities material conforming to IMS LIP;

'imslip-Affiliation' for affiliations material conforming to IMS LIP;

'imslip-Competency' for competencies material conforming to IMS LIP;

'imslip-Goal' for goals material conforming to IMS LIP;

'imslip-Interests' for interests material conforming to IMS LIP;

'imses-Participation' for groups material conforming to IMS Enterrpise Services;

'imslip-Product' for products material conforming to IMS LIP;

'imslip-QCL' for QCLs material conforming to IMS LIP;

'imslip-SecurityKey' for security keys material conforming to IMS LIP;

'imslip-Transcript' for transcripts material conforming to IMS LIP;

'imsep-Assertion' for assertions conforming to IMS Assertion;

'imsep-Reflexion' for reflexions conforming to IMS Reflexion;

'imsep-Rubric' for rubrics conforming to IMS Rubric;

'imsep-RubricCell' for rubric cells conforming to IMS Rubric;

Other portfolioParts should be identified using a similar naming convention that reflects the source and nature of the material and its form of binding;

Each resource that is used to identify a presentation XML instance will have the 'type' attribute declared as "PresentationStyle"; the order of the items ;
Each resource that is used to identify an owner XML instance will have the 'type' attribute declared as "OwnerDescription".

An example of a fully populated Portfolio Package manifest is given below.

<?xml version = "1.0" encoding = "UTF-8"?>
<manifest xmlns = "http://www.imsglobal.org/xsd/imsportfoliocp_v1p0" 
   xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance" 
   xsi:schemaLocation = "http://www.imsglobal.org/xsd/imsportfoliocp_v1p0 
   http://www.imsglobal.org/xsd/imsportfoliocp_v1p0/imsportfoliocp_v1p0.xsd" 
   identifier = "PORTFOLIOMANIFEST-8058760E-63E2-D91D-8CBF-4F283BFFD6C0" 
   version = "1.0">
   <organizations default = "ORG-4433B3DD-E2A4-B0E6-CD76-41A00B73FCFE">
      <organization identifier = "ORG-4433B3DD-E2A4-B0E6-CD76-41A00B73FCFE">
         <title>TestPortfolioPackage</title>
         <item identifier = "ITEM-VIEWS-ROOT">
            <title>Views</title>
            <item identifier = "ITEM-VIEW-001">
               <title>CurriculumVitae</title>
               <item identifier = "ITEM-VIEW-011" 
                     identifierref = "RES-PORTFOLIOPART-001">
                  <title>Personal Identification</title>
               </item>
               <item identifier = "ITEM-VIEW-012" 
                     identifierref = "RES-PORTFOLIOPART-002">
                  <title>Career Summary</title>
               </item>
            </item>
            <item identifier = "ITEM-VIEW-002">
               <title>Qualifications</title>
               <item identifier = "ITEM-VIEW-021" 
                     identifierref = "RES-PORTFOLIOPART-001">
                  <title>Personal Identification</title>
               </item>
               <item identifier = "ITEM-VIEW-022" 
                     identifierref = "RES-PORTFOLIOPART-003">
                  <title>Qualification Summary</title>
               </item>
            </item>
         </item>
         <item identifier = "ITEM-RELATIONSHIPS-ROOT">
            <title>Relationships</title>
            <item identifier = "ITEM-RELATIONSHIP-001" 
                  identifierref = "RES-RELATIONSHIP-001">
               <title>Qualification-Relexion</title>
            </item>
         </item>
         <item identifier = "ITEM-PRESENTATIONS-ROOT">
            <title>Presentations</title>
            <item identifier = "ITEM-PRESENTATION-001" 
                  identifierref = "RES-PRESENTATION-001">
               <title>CurriculumVitae</title>
            </item>
            <item identifier = "ITEM-PRESENTATION-002" 
                  identifierref = "RES-PRESENTATION-002">
               <title>QualificationsList</title>
            </item>
         </item>
         <item identifier = "ITEM-PORTFOLIOPARTS-ROOT">
            <title>PortfolioParts</title>
            <item identifier = "ITEM-PORTFOLIOPART-001" 
                  identifierref = "RES-PORTFOLIOPART-001">
               <title>Identification</title>
            </item>
            <item identifier = "ITEM-PORTFOLIOPART-002" 
                  identifierref = "RES-PORTFOLIOPART-002">
               <title>Activity</title>
            </item>
            <item identifier = "ITEM-PORTFOLIOPART-003"

                  identifierref = "RES-PORTFOLIOPART-003">
               <title>Certificate</title>
            </item>
            <item identifier = "ITEM-PORTFOLIOPART-004" 
                  identifierref = "RES-PORTFOLIOPART-004">
               <title>Assertion</title>
            </item>
            <item identifier = "ITEM-PORTFOLIOPART-005" 
                  identifierref = "RES-PORTFOLIOPART-005">
               <title>Reflexion</title>
            </item>
         </item>
      </organization>
   </organizations>
   <resources>
      <resource identifier = "RES-PRESENTATION-001" type = "PresentationStyle">
         <file href = "qualificationHTMLDocument.xsl"/>
      </resource>
      <resource identifier = "RES-PRESENTATION-002" type = "PresentationStyle">
         <file href = "cvPDFDocument.xsl"/>
      </resource>
      <resource identifier = "RES-PORTFOLIOPART-001" type = "imslip-Identification">
         <file href = "personalDetails.xml"/>
         <file href = "myphoto.jpg"/>
      </resource>
      <resource identifier = "RES-PORTFOLIOPART-002" type = "imslip-Activity">
         <file href = "careerRecord.xml"/>
      </resource>
      <resource identifier = "RES-PORTFOLIOPART-003" type = "imslip-QCL">
         <file href = "degreeCertificate.xml"/>
         <file href = "degreeCertificate.pdf"/>
      </resource>
      <resource identifier = "RES-PORTFOLIOPART-004" type = "imsep-Assertion">
         <file href = "assertionClaim1.xml"/>
      </resource>
      <resource identifier = "RES-PORTFOLIOPART-005" type = "imsep-Reflexion">
         <file href = "reflexion1.xml"/>
      </resource>
      <resource identifier = "RES-RELATIONSHIP-001" type = "imslip-Relationship">
         <file href = "qualificationReflexion.xml"/>
      </resource>
   </resources>
</manifest>

3. Narrative Description of PortfolioPart Binding

The <portfolioPart> consists of:

<accessForAll>
<activity>
<affiliation>
<assertion>
<competency>
<goal>
<identification>
<interest>
<participation>
<product>
<qcl>
<reflexion>
<relationship>
<rubric>
<rubricCell>
<securitykey>
<transcript>
Extensions

3.1 <accessForAll> element

The <accessForAll> element consists of the technical preferences of the learner for interacting with systems and content. It describes the learner's preferences for particular content characteristics, and for the display of content and control of the interface including the use of assistive technology hardware/software. This element is represented using the XML binding of the IMS Learner Information Package Accessibility for LIP (ACCLIP) specification [ACCLIP, 03].

Multiplicity: Occurs zero or more times in a Portfolio Package.

3.2 <activity> element

The <activity> element consists of an education/training, work, and service (military, community, voluntary, etc.) record.

This element is represented using the XML binding of the Activity structure as defined in the IMS Learner Information Package specification.

Multiplicity: Occurs zero or more times in a Portfolio Package.

3.3 <affiliation> element

The <affiliation> element is used to store the description of an organization affiliation associated with the Owner of the ePortfolio, e.g., professional memberships.

This element is represented using the XML binding of the Affiliation structure as defined in the IMS Learner Information Package specification.

Multiplicity: Occurs zero or more times in a Portfolio Package.

3.4 <assertion> element

The <assertion> element is used to represent the <assertion> class in the information model.

Figure 3.1 <assertion> element composition.

This element will be represented using the XML structure shown in Figure 2.4.

Multiplicity: Occurs zero or more times in a Portfolio Package.

Elements

<typename>
<comment>
<contentype>
<authorship>
<rationale>
<date>
<status>
<contactinfo>
<description>
<ext_assertion>

3.4.1 <typename> element

The <typename> element represents the typename attribute in the information model.

Multiplicity: Occurs zero or one time in <assertion>.

3.4.2 <comment> element

The <comment> element represents the comment attribute in the information model.

Multiplicity: Occurs zero or one time in <assertion>.

3.4.3 <contentype> element

The <contentype> element represents the content type attribute in the information model.

Multiplicity: Occurs zero or one time in <assertion>.

3.4.4 <authorship> element

The <authorship> element represents the authorship class in the information model. This element is represented using the XML binding for the authorship structure as defined in the ePortfolio schema.

Multiplicity: Occurs zero or one time in <assertion>.

3.4.5 <rationale> element

The <rationale> element represents the rationale class in the information model. This element is represented using the XML binding for the rationale structure as defined in the ePortfolio schema.

Multiplicity: Occurs zero or more times in <assertion>.

3.4.6 <date> element

The <date> element represents the date attribute in the information model.

Multiplicity: Occurs zero or more times in <assertion>.

3.4.7 <status>

The <status> element represents the status attribute in the information model.

Multiplicity: Occurs zero or one time in <assertion>.

3.4.8 <contactinfo> element

The <contactinfo> element represents the contact information attribute in the information model.

Multiplicity: Occurs zero or more times in <assertion>.

3.4.9 <description> element

The <description> element represents the description attribute in the information model.

Multiplicity: Occurs zero or one time in <assertion>.

3.4.10 <ext_assertion> element

The <ext_assertion> element represents the ext_assertion in the information model.

Multiplicity: Occurs zero or one time in <assertion>.

3.5 <competency> element

The <competency> element consists of the description of a skill the Owner of the ePortfolio has acquired.

This element is represented using the XML binding of the Competency structure defined in the IMS LIP specification.

Multiplicity: Occurs zero or more times in a Portfolio Package.

3.6 <goal > element

The <goal> element consists of the description of a personal objective or aspiration of the Owner.

This element is represented using the XML binding of the Goal structure as defined in the IMS Learner Information Package specification.

Multiplicity: Occurs zero or more times in a Portfolio Package.

3.7 <identification> element

The <identification> element represents the identity of the Owner of the ePortfolio, and may include name, contact information, and demographics.

This element is represented using the XML binding of the Identification structure as defined in the IMS Learner Information Package specification.

Multiplicity: Occurs one time in a Portfolio Package.

Note: In practice, a single occurrence of <identification> would be expected for any single Portfolio.

3.8 <interest> element

The <interest> element consists of descriptions of a hobby or other recreational activity of the Owner of the ePortfolio.

This element is represented using the XML binding of the Interest structure as defined in the IMS Learner Information Package specification.

Multiplicity: Occurs zero or more times in a Portfolio Package.

3.9 <participation> element

Figure 3.2 <participation> element composition.

The <participation> element is used to represent a group of people, which may or may not include the Owner of the Portfolio. The <participation> element may be used to represent a group of people who collaborated on the creation of a Product or who participated together in an Activity. The <participation> element is based upon the IMS Enterprise Services Group data model (more details on the <participation> element can be found in the Enterprise Services specification [ES, 04]). The LIP <contenttype> structure from the LIP specification is used to provide the reference identification mechanism.

Multiplicity: Occurs zero or more times in a Portfolio Package.

3.10 <product> element

The <product> contains materials produced by the Owner. These materials can consist of any material that can be stored or referenced electronically.

This element is represented using the XML binding of the Product structure as defined in the IMS Learner Information Package specification. The actual media referenced by the Product may be incorporated in a Content Package for transfer as described in Section 3.

Multiplicity: Occurs zero or more times in a Portfolio Package.

3.11 <qcl> element

The <qcl> element is used to represent the qualifications, certifications, and licenses awarded to the Owner, that is, the formally recognized products of their learning and work history.

This element is represented using the XML binding of the QCL structure as defined in the IMS Learner Information Package specification.

Multiplicity: Occurs zero or more times in a Portfolio Package.

3.12 <reflexion> element

The <reflexion> element is used to represent reflections upon or about a part of the ePortfolio, such as providing a comment or explanation, identifying strengths and weaknesses, or highlighting particular aspects of the portfolio part.

Figure 3.3 <reflexion> element composition.

This element will be represented using the XML structure shown in Figure 2.5.

Multiplicity: Occurs zero or more times in a Portfolio Package.

Elements

<typename>
<comment>
<contentype>
<authorship>
<rationale>
<date>
<status>
<contactinfo>
<description>
<ext_reflexion>

3.12.1 <typename> element

The <typename> element represents the typename attribute in the information model.

Multiplicity: Occurs zero or one time in <reflexion>.

3.12.2 <comment> element

The <comment> element represents the comment attribute in the information model.

Multiplicity: Occurs zero or one time in <reflexion>.

3.12.3 <contentype> element

The <contentype> element represents the contentype attribute in the information model.

Multiplicity: Occurs zero or one time in <reflexion>.

3.12.4 <authorship> element

The <authorship> element represents the authorship class in the information model

Multiplicity: Occurs zero or one time in <reflexion>.

3.12.5 <rationale> element

The <rationale> element represents the rationale class in the information model.

Multiplicity: Occurs zero or more times in <reflexion>.

3.12.6 <date> element

The <date> element represents the date attribute in the information model.

Multiplicity: Occurs zero or more times in <reflexion>.

3.12.7 <status> element

The <status> element represents the status attribute in the information model.

Multiplicity: Occurs zero or one time in <reflexion>.

3.12.8 <contactinfo> element

The <contactinfo> element represents the contact information attribute in the information model.

Multiplicity: Occurs zero or more times in <reflexion>.

3.12.9 <description> element

The <description> element represents the description attribute in the information model.

Multiplicity: Occurs zero or one time in <reflexion>.

3.12.10 <ext_reflexion> element

The <ext_assertion> element represents the ext_assertion attribute in the information model.

Multiplicity: Occurs zero or one time in <reflexion>.

3.13 <relationship> element

Figure 3.4 <relationship> element composition.

The <relationship> element represents the linking together of two <portfolioPart> elements.

This element is represented using the XML binding for the Relationship structure as defined in the IMS Learner Information Package specification. See the LIP specification [LIP, 01] for details.

Multiplicity: Occurs zero or more times in a Portfolio Package.

3.14 <rubric> element

Figure 3.5 <rubric> element composition.

The <rubric> element is used to represent guidance as to how a PortfolioPart has been, or is to be assessed. It does not provide for marking/grading schemes in their full glory nor does it provide an information model to support automated marking software. The <rubric> element is described in greater detail in the IMS Rubric Specification [RUBRIC, 05].

This element is represented using the XML binding of the Rubric structure, as defined in the Rubric specification.

Multiplicity: Occurs zero or more times in a Portfolio Package.

3.15 <rubricCell> element

Figure 3.6 <rubricCell> element composition.

The <rubricCell> element is used to represent the intersection of dimensions of quality within a Rubric. A <rubricCell> may be used to refer to outcomes that occur at the intersection of dimensions of quality within a <rubric>. RubricCells facilitate representing relationships between other elements and these intersections.

This element is represented using the XML binding of the Rubric structure, as defined in the IMS Rubric specification [RUBRIC, 05].

Multiplicity: Occurs zero or more times in a Portfolio Package.

3.16 <securitykey> element

The <securitykey> element will be used to contain the passwords, security codes, etc. to be used when communicating with the learner.

This element is represented using the XML binding of the SecurityKey structure as defined in the IMS Learner Information Package specification.

Multiplicity: Occurs zero or more times in a Portfolio Package.

3.17 <transcript> element

The <transcript> element is used to store the summary records of the academic performance at an institution. This information may contain an arbitrary level of detail and so there is no prescribed structure for a transcript.

This element is represented using the XML binding of the Transcript structure as defined in the IMS Learner Information Package specification.

Multiplicity: Occurs zero or more times in a Portfolio Package.

3.18 Extensions

Any data, file type, etc. can be stored as a <resource> in the Portfolio Package.

Multiplicity: Occurs zero or more times in a Portfolio Package.

About This Document

Title	IMS ePortfolio XML Binding
Editors	Colin Smythe (IMS), Darren Cambridge (EDUCAUSE), Mark McKell (IMS)
Team Co-Leads	Darren Cambridge (EDUCAUSE), Andy Heath (EPICC)
Version	1.0
Version Date	02 June 2005
Status	Final Specification
Summary	This document describes the XML Binding of the ePortfolio specification.
Revision Information	02 June 2005
Purpose	This document has been approved by the IMS Technical Board and is made available for adoption.
Document Location	http://www.imsglobal.org/ep/epv1p0/imsep_bindv1p0.html

To register any comments or questions about this specification please visit: http://www.imsglobal.org/developers/ims/imsforum/categories.cfm?catid=24

List of Contributors

The following individuals contributed to the development of this document:

Name	Organization
Darren Cambridge	EDUCAUSE
Jessica Finnefrock	Blackboard
Simon Grant	CETIS
Mike Halm	Penn State University
Andy Heath	EPICC
Mark McKell	IMS Global Learning Consortium, Inc.
Colin Smythe	IMS Global Learning Consortium, Inc.
Scott Wilson	CETIS

Revision History

Version No.	Release Date	Comments
Base Document 1.0	29 March 2004	Initial version of the ePortfolio specification.
Public Draft 1.0	20 September 2004	Public Draft version of the ePortfolio XML Binding.
Final Specification 1.0	02 June 2005	Final version of the ePortfolio XML Binding.

Index

B
Binding 1, 2, 3, 4, 5, 6, 7

C
Conformance 1

E
Elements
portfolioPart 1, 2
relationship 1, 2, 3
ePortfolio 1, 2, 3, 4, 5

I
IMS Specifications
     Content Packaging 1, 2
     ePortfolio 1
     Learner Information Package 1, 2, 3, 4, 5, 6, 7
     Learner Information Package Accessibility for LIP 1

L
Learning 1

N
Normative 1

P
Package 1
Portfolio 1
Portfolio Package 1, 2, 3, 4, 5, 6, 7
Preferences 1

R
Records 1
Rubric 1, 2

S
Schema 1
Structure 1, 2, 3, 4, 5, 6, 7, 8

W
W3C 1

X
XML 1, 2, 3, 4, 5, 6, 7, 8, 9
XSD 1
XSL 1
XSLT 1

IMS Global Learning Consortium, Inc. ("IMS/GLC") is publishing the information contained in this IMS ePortfolio XML Binding ("Specification") for purposes of scientific, experimental, and scholarly collaboration only.

IMS/GLC 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/GLC would appreciate receiving your comments and suggestions.

Please contact IMS/GLC through our website at http://www.imsglobal.org

Please refer to Document Name: IMS ePortfolio XML Binding Revision: 02 June 2005

Table of Contents

1. Introduction

1.1 Scope and Context

1.2 Structure of this Document

1.3 Nomenclature

1.4 References

2. Narrative Description of Portfolio Package Binding

2.1 Portfolio Packages

3. Narrative Description of PortfolioPart Binding

3.1 <accessForAll> element

3.2 <activity> element

3.3 <affiliation> element

3.4 <assertion> element

3.4.1 <typename> element

3.4.2 <comment> element

3.4.3 <contentype> element

3.4.4 <authorship> element

3.4.5 <rationale> element

3.4.6 <date> element

3.4.7 <status>

3.4.8 <contactinfo> element

3.4.9 <description> element

3.4.10 <ext_assertion> element

3.5 <competency> element

3.6 <goal > element

3.7 <identification> element

3.8 <interest> element

3.9 <participation> element

3.10 <product> element

3.11 <qcl> element

3.12 <reflexion> element

3.12.1 <typename> element

3.12.2 <comment> element

3.12.3 <contentype> element

3.12.4 <authorship> element

3.12.5 <rationale> element

3.12.6 <date> element

3.12.7 <status> element

3.12.8 <contactinfo> element

3.12.9 <description> element

3.12.10 <ext_reflexion> element

3.13 <relationship> element

3.14 <rubric> element

3.15 <rubricCell> element

3.16 <securitykey> element

3.17 <transcript> element

3.18 Extensions

About This Document

List of Contributors

Revision History

Index