[
Lists Home |
Date Index |
Thread Index
]
Upon the request by eligible participants I have created an OASIS
Discussion List whose purpose is to discuss the creation of an OASIS
Technical Committee. Discussion on the list will begin in seven days to
give everyone a chance to subscribe, and the list and its archive will
be deleted after 90 days. The list is
edxml-discuss@lists.oasis-open.org
The proposal for the formation of the list is below.
In order to participate in the discussions on these topics you should
subscribe to the discussion list using the subscription form at
http://lists.oasis-open.org/ob/adm.pl or by sending a message to
edxml-discuss-request@lists.oasis-open.org
with the word "subscribe" as the body of the message. OASIS membership
is not required in order to subscribe to this list. If you do not wish
to subscribe but wish to view the discussion you may view the list
archives at http://lists.oasis-open.org/archives/
</karl>
=================================================================
Karl F. Best
OASIS - Director, Technical Operations
+1 978.667.5115 x206
karl.best@oasis-open.org http://www.oasis-open.org
In accordance with the OASIS Technical Committee Policy (revised August
2001) I hereby request authorization to begin a public discussion list
for the purpose of forming an OASIS Technical Committee. The following
items are submitted in support of this request:
1) The name of the discussion list – edXML_launch
2) A preliminary statement of scope for the proposed edXML TC is
attached
3) The identifying information for the PEOTCPs requesting authorization
TS Vreeland, tvreeland@taconic.net, OpenVES
James Simon, jjs@sun.com, Sun Microsystems
Donald Leclair, donald.Leclair@ca.com, Computer Associates
Ronald Alepin, ralepin@fsw.fujitsu.com, Fujitsu Software Corporation
4) The name of the discussion list leader – TS Vreeland
As you know we are going to be recruiting others to join the discussion
list and contribute to the scope definition next week in Texas. Please
let me know as soon as the discussion list has been created. I
understand that you will share the information I have provided with the
OASIS membership with a call for participation in the discussion list.
Thank you for your support in helping us to get this project underway. I
look forward to have a full fledged Technical Committee operating during
the Summer.
Please let me know if you require any additional information.
Sincerely,
TS Vreeland
Architect and Chief Technologist
edXML Scope
This community will embark on a number of initiatives to fast-track the
documentation of PK12 educational requirements for XML based markup,
controlled vocabularies, ontologies, web services and protocols. It will
pursue areas not currently being addressed in other standards
communities, and will coordinate with IMS and other groups where
important foundation specifications, relevant to PK12 are being
developed. The edXML community will explore the relationships between
other important emerging XML specifications, like ebXML, DSML, SAML,
WSRP, WSXL, and PK12 requirements, and create liaisons between them. The
following activities proposed as the edXML TC scope:
· Coordinate and collaborate with other important PK12 initiatives:
OpenVES, EdNA, EUN SchoolNet, CanCore, APEC, Prometeus, CETIS, USoeC,
Achieve.org, etc.
· Provide a set of international registries for PK12 subject taxonomies,
controlled vocabularies, ontologies, schemas, and best practices
· Work on specifications for Federated PK12 Content Repositories,
Subject and Content gateways, and the protocols to support them
· Work on strategies for deep classification of curriculum standards,
semantic metadata, and extending the metadata model for PK12 education
· Work on a realization of an XML version of a PK12 directory schema
based on DSML and other standards work
· Publish an XML version of the US Department of Education Data
Handbooks
· Create implementation strategies and best practices for use and
extension of OASIS ebXML specifications for purposes of PK12 eduCommerce
· Create, in coordination with other communities, PK12 specifications
for digital rights management, content licensing, and content
distribution to support PK12 digital content
· Recommend strategies for exchange protocols for Curriculum,
Instruction, Assessment, and Content objects based on SOAP protocols and
web services (WSDL)
· Create Implementation strategies for web services deployment of PK12
education applications, tools, resources, services, and content
· Publish and document XML based pattern languages for Collaborative
Patterns, Pedagogical Patterns, Learning Patterns and Assessment
Patterns for PK12
· Coordinate with the Education Markup Language work of the IMS Learning
Design Workgroup to assure that it is extended to address and fully
support PK12 requirements
· Assure that embedded educational research and information collection
needs are addressed in the design and specification of PK12 markup
specifications, ontologies, and vocabularies
· Provide implementation strategies for the integration of the features
of the IEEE 1484.7 Tool Agent Protocol into PK12 education
specifications
· Create accessibility, personalization, and affinity group XML profiles
for PK12 education systems
· Document an implementation of a PPP privacy model for PK12 education
· Document specifications for a modular, portable, and configurable
Acceptable Use Policy markup and service definition for use in PK12
education
· Extend existing InetPerson, and EduPerson, user profile specifications
to create a k12Person specification for use in PK12 education systems
· Assure that embedded decision support and data collection needs are
addressed in the design and specification of PK12 markup specifications,
ontologies, and vocabularies
It may be that as the discussion list proceeds that multiple Technical
Committees may be required to support the breadth and depth of the PK12
specification and standardization effort.
|
