Title: AGENDA
1AGENDA
- Approval of the agenda
- Meeting Rules
- Working Group Reports and Associated Motions
- ODRL PAR Proposal (Tyde)
- Treasurers Report
- Secretarys Report (Including action items)
- Information Officer Report
- Web Site
- PP Discussion
- New Business
2Meeting Rules
- Open meeting observers welcome
- Only SEC members may vote
- SEC members
- Chairs of WG groups (groups with approved PARs,
active or not 1,3,9,11,12,14,15,18,20) - LTSC Officers (Ch. VC., SEC., TR, IO)
- One person one vote
3WG Reports Actions Items
- 1484.1 (LTSA) In sponsor Ballot closing March
22, 2002 - 1484.3 (Glossary) Report
- 1484.11 (CMI)
- Report
- Name Change Committee
- Motions on next page
41484.11 Motions
- Moved that the SEC approve the initiation of the
sponsor ballot process for 1484.11.1 and
1484.11.2 and task the LTSC and WG Chair to
proceed with all due haste. - Moved that the SEC submit CMI WG documents
meeting the 1484.11.1 and 1484.11.2 PARs for
sponsor ballot when they have been finalized and
a ballot group has been formed. - Moved that the PAR revisions (on following slide)
be submitted to NesCOM to meet comments made
during continuous processing.
5SCOPE COMMENTS RECEIVED
- P1484.11.1 and P1484.11.2 - These two items are
different parts of a multipart standard but the
scope and purpose for each of the two parts have
not been explained. - Editorially, consider changing "single" to one
part of a multi-part standard. Consider changing
the third sentence in the Scope so that it
applies to the subject of the PAR (Part 1 of a
multi-part standard) or moving it under the scope
statement for the multi-part standard. Recommend
first stating the scope of the multi-part
standard and then identify the scope of Part 1
and identify the title of the other parts - Approve pending verification of dates and
Purpose. Can PAR be put in ballot by 6/2002? Can
Purpose be made more specific, eg Employ CMI
specifications in learning management systems...
6IP COMMENTS RECEIVED
- Scope states that the standard is based upon work
done by AICC and will include contributions from
other specification development organizations.
But in item 15, no other standards or projects of
similar scope are cited. This appears to
contradict the scope. The other work should be
cited in 15. - Both of these standards are intended to
incorporate existing material and material that
may be the IP of other standards groups. It is
not clear if there has been any agreement with
these groups, and it would be wasted effort if
later on the permissions cannot be obtained. In
addition, one of our roles is to ensure that
there is no overlap of standards activity to
avoid conflicting standards. The submission does
not indicate that this has been addressed.
7 PROPOSED .1 PAR REVISION
This standard is one Part of a multipart standard
that covers a current industry practice called
"CMI -- Computer Managed Instruction". This CMI
specification is based on work originally
developed and submitted for standardization by
the AICC (Aviation Industry CBT Committee) and
will include contributions from other
organizations that have used the AICC
specifications. This Part of the standard is Part
1 Data Model for (Content to LMS) Communication.
This Part covers the development of a common
data model for content to Learning Management
System (LMS) communications to support multiple
communication bindings to the data model. This
multipart standard codifies and harmonizes
existing practice. The scope of this multipart
standard is to build consensus around, resolve
ambiguities within, and correct defects in
existing CMI specifications. Purpose of
Proposed Project The CMI specifications have
been implemented and adopted in commercial
products (originally in the aviation industry).
There is widespread acknowledgement that these
specifications have broad applicability in the
area of learning management systems. The purpose
of this standard is to facilitate the use of CMI
specifications and thereby promote
interoperability among learning systems and
learning content.
8PRPOSED .2 PAR REVISION
same preamble This Part of the standard is
Part 2 ECMAScript API Binding for IEEE
1484.11.1. This Part covers the development of
the ECMAScript API binding. This Part is
harmonized with the existing AICC CMI
specification and the ADL SCORM (Sharable Content
Object Reference Model) specification. The
ECMAScript-based API binding enables the
communication of information between content and
Learning Management System (LMS) via common API
services using the ECMAScript language. This
multipart standard codifies and harmonizes
existing practice. The scope of this multipart
standard is to build consensus around, resolve
ambiguities within, and correct defects in
existing CMI specifications. Same purpose
91484.12 LOM Motions
- Moved The LTSC shall
- report to SC36 that the LOM data model is nearing
standardization - Explain its status
- Request SC36 instructions concerning when to
submit the document according to New York
Resolution 6. - Moved The SEC approve the forwarding to NesCOM
of a revised PAR for LOM approved by the WG and
consisting of editorial changes and stating that
the PAR is part of a multi-part standard.
10WG REPORTS CONTINUED
- 1484.14 (SXB) Report 45 day ballot period for
.1, .2, and .3 documents. Initiation of Sponsor
ballot to be deferred until comments are resolved
from document approval ballot. - 1484.15 (Protocols) Report
- 1484.16 (Platform Profiles) Report
- 1484.20 (Competency Definitions) Report A
request for formal reactivation of the WG will be
considered at the June 2002 meeting. LTSC Chair
will request change in numbering if re-activated.
11ODRL WG PROPOSED
- OPEN DIGITAL RIGHTS LANGUAGE
- Proposed by IPR systems
- PAR on next slide
- Suggested Acceptance Criteria (Chairs remark)
- Existing Specification
- Existing Implementations and Industry Support
- Relevance to Learning
- Tyde Richards to summarize
- Motions entertained
12PROPOSED ODRL SCOPE
- This project will codify existing practice in a
standard for expressing rights information in
Digital Rights Management (DRM) systems. The
language, based on the Open Digital Rights
Language (ODRL) Version 1.0, will cover the
expression of permissions, constraints,
conditions, and requirements in both the offers
and agreements made between content owners and
content users. The language will also manage the
entitlements of rights holders. The language will
be applicable to a wide range of communities (eg
education, media, mobile, publishers, etc) and
wide range of media types (eg web, video,
documents, audio, etc).
13Proposed ODRL Purpose
- The purpose of this standard is to enable
interoperability between Digital Rights
Management (DRM) systems by providing a standard
language for expressing rights over content. This
will also enable greater use and reuse of
content, benefiting learning content producers,
managers, distributors, and users as is
appropriate for educational applications. The
wide availability of an open, lightweight, and
concise standard in this area is critical for the
interoperation of rights-enabled content and the
adoption of systems that manage that content.
14Reports
- Treasurer
- Membership
- Email campaign
- Secretary
- Election/ballot actions items
- Information Officer (next slide)
15Web Site
- Changes required
- Membership form
- Restrict Reflector Postings to Members
- Mission statement for the LTSC and the groups for
the homepage - Some statements on activities, progress, plans -
the new structure has been created after March
2001 meeting where the groups were encouraged to
provide this kind of information to outline and
monitor their progress. - Information on implementation of standards and
related projects - Stop posting documents to company Web sites and
post to LTSC site
16PP Discussion
- 30 Day ballot after meeting
- Discussion of Changes
17NEW BUSINESS
- MOVED The LTSC expresses its gratitude and
appreciation for DEST and the financial support,
local arrangements made by Jon Mason, and the
unparalleled Australian hospitality. - Other New Business?
- Adjournment