> DCMIIEEELTSCTaskforce/ScopeAndPurpose

The following 217 words could not be found in the dictionary of 550 words (including 550 LocalSpellingWords) and are highlighted below:

able   Abstract   abstract   achieve   actually   agree   align   allow   also   an   analysis   and   Andy   anyone   approach   appropriate   are   as   aspects   balloting   be   between   Both   both   by   carried   combine   commenting   Comments   communities   community   conform   conforming   Consensus   considered   consist   contribute   Core   data   definitions   demand   describes   describing   description   detail   details   do   documents   draft   Dublin   dublincore   each   editors   Education   education   elements   encoding   expected   expressing   final   following   for   formal   formalizing   formulated   from   fundamental   great   group   groups   handling   have   high   hosted   how   However   ieeeltsc   if   implementers   in   In   include   including   incompatibilities   increasing   initial   Initiative   instances   intention   interact   interim   interoperability   interoperable   is   Is   issue   issues   it   It   Johnston   joint   Jon   lead   Learning   list   locus   longer   mailing   mandatory   Mason   medium   members   Membership   Metadata   metadata   Mikael   Model   models   necessary   need   Nilsson   not   Object   of   on   one   open   organization   organizations   other   out   overall   P1484   part   partial   participate   Pete   Powell   Practice   priorities   process   production   properties   provide   Publication   publication   publish   Purpose   purpose   recognize   recommendation   Recommendation   Recommended   referenced   regardless   represents   resolved   right   schemes   Scope   scope   Self   set   shared   short   site   situation   so   solution   specification   specified   Standard   standard   standards   still   stopped   structure   struggling   study   syntax   Taskforce   taskforce   technical   term   terms   that   The   the   There   there   these   they   This   this   through   Thus   to   together   trying   two   up   use   used   value   veto   vocabularies   vocabulary   web   well   where   which   will   with   within   work   worked   working  

Clear message

Scope and Purpose of the joint DCMI/IEEE LTSC Taskforce

The scope and purpose are formulated to be appropriate for an IEEE PAR.

Scope of the recommendation

This Recommended Practice describes IEEE LTSC P1484.12.1 Learning Object Metadata instances in the Dublin Core Metadata Initiative Abstract Model. The Recommended Practice will include the specification of DCMI Abstract Model terms, including properties, vocabularies, syntax encoding schemes and vocabulary encoding schemes, that may be used for expressing metadata conforming to the IEEE LOM Standard in Dublin Core metadata. The recommendation will include the specification of URIs to use for the terms, as well as a description of how to combine the specified terms so that metadata instances conforming to this Recommended Practice conform to the IEEE LOM Standard.

Purpose of the recommendation

There is an increasing demand for interoperable definitions of Dublin Core metadata terms and IEEE LOM data elements which allow these to be used together in metadata instances. This Recommended Practice will approach part of this situation by describing how to use IEEE LOM and Dublin Core terms together in Dublin Core metadata instances. This represents a partial and short-term solution to the overall issue, which will still be of great value in the short to medium term for implementers that are struggling with these metadata interoperability issues. The Recommended Practice will also be of great value in the longer-term process of trying to align the abstract models of IEEE LOM and Dublin Core, as it will provide an analysis of fundamental incompatibilities between the two models.

Publication

The intention is to publish the recommendation as both an IEEE Recommended Practice and a DCMI Recommendation. The details of the formal process necessary to achieve that are still to be worked out in detail. However, the following are high priorities for the publication process:

Taskforce structure

The taskforce will consist of members of both DC-Education and IEEE LTSC. The taskforce will interact with the DCMI through the DC Education working group. It is expected that there will also be an IEEE LTSC working group handling the formal aspects of the IEEE process. In the process of formalizing the PAR for the IEEE LTSC working group, an interim IEEE LTSC study group will be set up. However, the work will be carried out within the joint taskforce. The LTSC and the DCMI will need to recognize this joint taskforce as the locus for the work on the recommendation.

Membership in IEEE LTSC will not be mandatory, and the mailing list will be open to anyone. It is expected that taskforce documents will be referenced both from the [WWW]IEEE LTSC web site and the [WWW]DC Education working group web site, regardless of where they are actually hosted.

The initial technical editors will include:

The taskforce will be lead by [Self]Mikael Nilsson and Jon Mason.