1. Package Exchange Notification Services
AICC February 2004 Phoenix, AZ USA
Ed Cohen – Plateau Systems Tom King - Macromedia

2. Authoring System World
Reviewing the Need
Author Content
Authoring System World
Edit API Needed
Launch Content
Publish Content
LMS World
Deploy API Needed
Author Course

3. Rationale for focus on deployment
Clearer path to implementation
Can work for simple content testing
Easier for a desktop application to connect to a server & submit content than vice versa
Existing formats can be leveraged
Direct deployment enables new class of authors

4. Package Exchange Notification
Goals
Focus on learning & training uses
Simplify deployment for authors
Use established & understood technology
Enable evolution & extension

5. Participants

6. Participation Participants plan to implement prototype by June 2004
reflector
subscribe
Weekly telecon Thurs 8:00am Pacific Time (GMT -8:00)

7. Package Exchange Model
Content Server
Package
Package
3. Stage
Build
DEPLOY
LMS
Authoring Tool
Course
2. LMS Approval & Process
1. Notify
4. Deploy
Source

8. Proposed Specification
Package Exchange Notification
Content tool notifies server that a package is available
Package can use existing AICC CSF + ZIP
Notification options
HTTP POST & HTTP GET
Web Services (SOAP/XML)
Transfer options
UNC
FTP & HTTP
SOAP Binary attachment
attachment
Decisions
Keep it simple
Focus on HTTP
Create name-value pairs easily mapped to web services
Provide URL for package without prescribing how it is staged there
Leverage existing formats

9. Package Exchange Notification
Goals
Focus on learning & training uses
Simplify deployment for authors
Use established & understood technology
Enable evolution & extension

10. Package Exchange Notification
Progress
5 meetings
3rd document draft
Scheduled for prototype demonstration by multiple vendors in June

11. Milestones & Schedule December 10, 2003 - Preliminary research
January 23, Spec outline and working draft
February 3, AICC Presentation
February 20, Revised spec for vendor code prototypes
March 26, Standards-ready draft
May 14, Standards-ready + vendor group revisions
Demonstrate protoypes - AICC June 2004

12. Sample Command http://acmelearning.lms.com/pens? &pens-version=0.5.0
&status-url=_self
&command=collect
&package-type=aicc-pkg
&package-type-version=1.0
&package-format=zip
&package-id-scheme=urn
&package-id= urn:publicid:2631e b4c6-8701f960dccc
&package-url= http%3A%2F%2Fmyauthoringtool%2Fmycontentpackage.zip
&package-url-user-id=
&package-url-account=
&package-url-password=
&package-url-expiry= T06%3A51%3A29
&client=Authorware7
&system-user-id=tk007
&system-account=
&system-password=
&receipt=mailto%3Atking%40macromedia.com
&alerts=

13. Current Issues AICC Considerations Define Package Contents
AICC Course Interchange Files
Content & relative pathing
Metadata
Recommend archive format (ZIP)
Unique Identifier for a course (GUID, URN)
Error codes & responses
Potential synergies with “Offline CMI”
June interoperability demo