Hi Lorna, Andy,
We are rather back to the old chestnut about what an LO is aren't we.
To avoid opening up that old wound, I'll put the stuff in location as
OpenURLs and stop bitching.
If I were to take over the world tommorow, I'd chop the general and
lifeCycle chunks of the LOM and use DC for the bibliographic bits of the
description and what was left of the LOM for the educational
description, technical requirements and classification. This is all
perfectly do-able within a framework like RDF, where you can specify as
many schemas as you want and pick and mix attributes from them. Given an
application profile to ringfence what elements in what schemas to choose
from that is.
Alternatively, most of these issues would vanish if the LOM had a title
added entry type element that was repeatable.
Anyone have any suggestions about what to do with series and collection
titles?
Cheers.
Lorna M. Campbell wrote:
> Andy Powell wrote:
>
>> I'm not sure I understand this...
>>
>> 4.3 location is defined as 'A string that is used to access this
>> learning
>> object.' which is *exactly* what an OpenURL is...
>>
>> 7. relation is defined as 'This category defines the relationship
>> between
>> this learning object and other learning objects, if any.' But we're not
>> providing information about 'other learning objects' we're providing
>> information about 'this learning object'. So, putting this
>> information in
>> relation feels completely wrong to me.
>>
> That's a very good point..... tricky one!
>
> L. :-)
>
> --
> Lorna M. Campbell
> Assistant Director
> Centre for Educational Technology Interoperability Standards (CETIS)
> Centre for Academic Practice, University of Strathclyde
> +44 (0)141 548 3072
> http://www.cetis.ac.uk/
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Paul Hollands <[log in to unmask]>
LTSN-01 Information and Web Support Officer
University of Newcastle, 16/17 Framlington Place
Newcastle upon Tyne, NE2 4AB
0191 222 5888
<http://www.ltsn-01.ac.uk/>
|