Hello.
I think I see what Dan is driving at with his main point, but I think it
needs some thinking about and clarification.
To be pedantic, there is no informal mapping to the DCAM in 1484.12.1.
There can't be since the DC Abstract Model wasn't available in 2002.
There is a mapping between 1484.12.1 and the "Simple" Dublin Core
Element Set. That's fine, since both define element sets. It's not
clear to me how you would map from the Abstract Model to 1484.12.1. So
my question is, Dan, do you mean a mapping showing how any DC term
defined in accordance with the DCAM can be mapped to the 1484.12.1 or
just some? (Supplementary question: if you mean some, then which?)
I'm trying to understand how much extra work would be involved. Clearly
some of the reverse mappings would immediately drop out of the LOM ->
DCAM mapping; some LOM->DC mappings might be "lossy" and so not give a
reverse mapping (which would be useful to document); some DC-LOM
mappings might need new LOM elements to be coined.
Phil.
Daniel Rehak wrote:
> I see requirements for bi-directional representations (LOM <-> DCAM).
> While 1484.12.1 has an informal mapping, this is not to the same level
> of rigor as the proposed best practice. Since this BP appears to be
> only a one-way mapping, the Scope section of the PAR should explicitly
> state that a DCAM -> LOM is out of scope, and the purpose section
> should indicate why.
>
> Suggested editorial revision to the drafts below to address:
> -- titles/numbering ("P" go away on final).
> -- make the PAR address contents, not potential work
> -- eliminating time frames since these are speculative.
>
> - Dan
>
> Title: Recommended Practice for Expressing IEEE Learning Object Metadata
> Instances Using the Dublin Core Metadata Initiative Abstract Model
>
>
> Scope:
>
> This Recommended Practice describes how to define IEEE LTSC 1484.12.1
> Learning Object Metadata instances in the Dublin Core Metadata
> Initiative Abstract Model. The Recommended Practice describes how to
> use the definitions of metadata terms defined by the IEEE LTSC
> 1484.12.x "Standard for Resource Description Framework (RDF)
> vocabulary for IEEE LOM Data Elements" for expressing metadata
> conforming to the IEEE LOM Standard 1484.12.1 in Dublin Core
> metadata. The Recommended Practice includes a description of how to
> combine the specified terms so that metadata instances conforming to
> this Recommended Practice also conform to the IEEE LOM Standard
> 1481.12.1.
>
> Purpose:
>
> 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
> address part of this problem by describing how to use IEEE LOM and
> Dublin Core terms together in Dublin Core metadata instances. This
> represents a partial solution to the overall issue, which will be of
> value for implementers that are struggling with these metadata
> interoperability issues. The Recommended Practice will also be of
> value in the 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.
>
>
> Title: Standard for Resource Description Framework (RDF) vocabulary for
> IEEE LOM Data Elements
>
> Scope:
> This Standard defines a Resource Description Framework (RDF)
> vocabulary for data elements from the IEEE LTSC 1484.12.1 Learning
> Object Metadata standard. The Standard will make use of modeling
> primitives from the RDF Vocabulary Description Language (RDF Schema)
> and the Dublin Core Metadata Initiative Abstract Model. The Standard
> will include the specification of RDF terms, including properties,
> classes, vocabularies, syntax encoding schemes and vocabulary encoding
> schemes, that may be used for expressing RDF metadata using LOM data
> elements and vocabularies. The recommendation will include the
> specification of URIs to use for the terms. The Standard will not
> define new terms for data elements that can be appropriately expressed
> using sufficiently stable, existing RDF vocabularies (notably Dublin
> Core). This Standard does not address the construction of conforming
> IEEE LOM metadata instances using RDF technology.
>
> Purpose:
> There is an increasing demand for interoperable definitions of IEEE LOM
> data elements which allow these elements to be used in applications
> using Semantic Web technologies such as the Resource Description
> Framework. This Standard will form an important basis for making IEEE
> LOM metadata terms useful in this larger metadata context.
>
> On Nov 20, 2007 4:54 AM, Mikael Nilsson <[log in to unmask]> wrote:
>
>> Hi all!
>>
>> I'd like to use the next taskforce meeting (Monday 26th) to make a final
>> decision on what PARs to submit to the IEEE. The background is that
>> while we *do* have a formulation of the LOM->DCAM mapping specification,
>> it seems to me and others that it would be appropriate to produce *two*
>> specifications: one for the LOM RDF vocabulary, and one for the LOM ->
>> DCAM mapping.
>>
>> My proposal is to use the following Scope And Purpose statement for the
>> mapping:
>>
>> Title: Recommended Practice for Expressing IEEE Learning Object Metadata
>> Instances Using the Dublin Core Abstract Model
>>
>>
>> Scope:
>> 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 describe how to use the definitions
>> of metadata terms defined by the IEEE LTSC P1484.12.x "Standard for
>> Resource Description Framework (RDF) vocabulary for IEEE LOM Data
>> Elements" for expressing metadata conforming to the IEEE LOM Standard in
>> Dublin Core metadata. The recommendation will include a description of
>> how to combine the specified terms so that metadata instances conforming
>> to this Recommended Practice also conform to the IEEE LOM Standard.
>>
>> Purpose:
>> 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.
>>
>> And the vocabulary Standard would be:
>>
>> Title: Standard for Resource Description Framework (RDF) vocabulary for
>> IEEE LOM Data Elements
>>
>> Scope:
>> This Standard defines a Resource Description Framework (RDF) vocabulary
>> for data elements from the IEEE LTSC P1484.12.1 Learning Object
>> Metadata standard. The Standard will make use of modeling primitives
>> from the RDF Vocabulary Description Language (RDF Schema) and the DCMI
>> Abstract Model. The Standard will include the specification of RDF
>> terms, including properties, classes, vocabularies, syntax encoding
>> schemes and vocabulary encoding schemes, that may be used for
>> expressing RDF metadata using LOM data elements and vocabularies. The
>> recommendation will include the specification of URIs to
>> use for the terms. The Standard will not define new terms for data
>> elements that can be appropriately expressed using sufficiently stable,
>> existing RDF vocabularies (notably Dublin Core). This Standard does not
>> address the construction of conforming IEEE LOM metadata instances using
>> RDF technology.
>>
>> Purpose:
>> There is an increasing demand for interoperable definitions of IEEE LOM
>> data elements which allow these elements to be used in applications
>> using Semantic Web technologies such as the Resource Description
>> Framework. This Standard will form an important basis for making IEEE
>> LOM metadata terms useful in this larger metadata context.
>>
>> Comments?
>>
>> /Mikael
>> --
>> <[log in to unmask]>
>>
>> Plus ça change, plus c'est la même chose
>>
>>
>
>
>
>
--
Phil Barker Learning Technology Adviser
ICBL, School of Mathematical and Computer Sciences
Mountbatten Building, Heriot-Watt University,
Edinburgh, EH14 4AS
Tel: 0131 451 3278 Fax: 0131 451 3327
Web: http://www.icbl.hw.ac.uk/~philb/
|
