Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

六合彩|香港六合彩 » SlideShare


Published on






Published in: Education
  • Be the first to comment

  • Be the first to like this

六合彩|香港六合彩 » SlideShare

  1. 1. Implementing IMS Metadata in COSE 1 <ul><li>What is COSE? </li></ul><ul><li>VLE free to HE, FE and others [as of June 2002] </li></ul><ul><li>characterised by it’s pedagogical framework – for structured </li></ul><ul><li>focussed & active learning. also in its reuse of content [but not </li></ul><ul><li>as learning objects in the wider meaning of that term], in the </li></ul><ul><li>quality control inherent in publication of content, in the sharing </li></ul><ul><li>of resources [ importance attached to collaboration working ], </li></ul><ul><li>and its distributed nature so suitable for ‘distance’ learning </li></ul><ul><li>use of specifications / standards – evolving. But IEEE now a </li></ul><ul><li>standard </li></ul>
  2. 2. Implementing IMS Metadata in COSE 2 <ul><li>Overview </li></ul><ul><li>How current version COSE 2.05 implements the metadata spec </li></ul><ul><li>- but this talk / presentation not particularly about metadata (!), </li></ul><ul><li>rather is meant to be contextual, and about metadata issues </li></ul><ul><li>[and presented from our own perspective, so not concerned with </li></ul><ul><li>other metadata initiatives, pro tem] </li></ul><ul><li>1. Demonstrate use of metadata in content packaging </li></ul><ul><li>2. Plans for metadata in context of current phase, </li></ul><ul><li>/ SURF X4L project - Using metadata (**!!) </li></ul><ul><li>3. Discussion of issues </li></ul>
  3. 3. Implementing IMS Metadata in COSE 3 <ul><li>1. Demonstrate use of metadata in content packaging (i) </li></ul><ul><li>COSE 2.05 uses Version 1p2p2 </li></ul><ul><li>instance not system conformant [we say] </li></ul><ul><li>but there is no conformance authority </li></ul><ul><li>what we have instead – best practice established through groups such as </li></ul><ul><li>this and EC SIG. </li></ul><ul><li>at least we can say, COSE is consistent with practice established through </li></ul><ul><li>user community e.g. EC codebash. participants inc. some but not all VLE </li></ul><ul><li>vendors. but important that metadata experts should not be left out of the </li></ul><ul><li>picture [ => why I am here] </li></ul>
  4. 4. Implementing IMS Metadata in COSE 4 <ul><li>1. Demonstrate use of metadata in content packaging (ii) </li></ul><ul><li>COSE 2.05 manual – Appendices E & F </li></ul><ul><li>Appendix E: export procedure: demo </li></ul><ul><li>why tag content with metadata / have to make this as simple as </li></ul><ul><li>possible </li></ul><ul><li>task of supplying metadata divided between individuals </li></ul><ul><li>involved in [content] export procedure </li></ul><ul><li>also automated in some limited sense </li></ul>
  5. 5. Implementing IMS Metadata in COSE 5 <ul><li>1. Demonstrate use of metadata in content packaging (iii) </li></ul><ul><li>Appendix F: metadata used in COSE </li></ul><ul><li>http:// </li></ul>
  6. 6. Implementing IMS Metadata in COSE 6 <ul><li>2. Plans for metadata / SURF X4L project - Using metadata (**!!) </li></ul><ul><li>[ important driver for use of metadata is content exchange / repositories </li></ul><ul><li>(X4L programme) ] </li></ul><ul><li>(a) Export (b) and import of standalone content objects </li></ul><ul><li>v COSE packages - would allow exchange of unpublished content </li></ul><ul><li>demo </li></ul><ul><li>2. options / code for search engine / database? </li></ul>
  7. 7. Implementing IMS Metadata in COSE 7 <ul><li>3. Discussion of issues (i) </li></ul><ul><li>[context: respecting content packaging in particular] </li></ul><ul><li>- conformance requirements too loosely defined in spec docs. </li></ul><ul><li>so we can implement without using metadata (!) </li></ul><ul><li>- extensions: drive spec development but compromise interoperability </li></ul><ul><li>- control documents. different control docs allowed, local copy or web ref </li></ul><ul><li>- vocabularies </li></ul><ul><li>- user issues </li></ul><ul><li>- others described in IMS briefs e.g. multiplicity of elements [no limit (!)], </li></ul><ul><li> use of vCard, unique Ids </li></ul><ul><li>see </li></ul><ul><li> </li></ul>
  8. 8. Implementing IMS Metadata in COSE 8 <ul><li>3. Discussion of issues (ii) </li></ul><ul><li>[ context: some wider issues ] </li></ul><ul><li>use: most systems not [system] conformant / not searching on metadata; </li></ul><ul><li>was true 18 months ago. now ? [ => will find out in course of SURF X4L </li></ul><ul><li>w VLE partners (Bb / Learnwise / Teknical). SCORM conformance ? ] </li></ul><ul><li>metadata: context [and see next slide] </li></ul><ul><li>c.f. CP v (staffs uni) web project </li></ul><ul><li>meta tag / established means of specifying DC metadata </li></ul><ul><li>IMS used for packaged content but not more widely </li></ul><ul><li>e.g. free standing web content / other e.g. library resources </li></ul><ul><li>standardization: what this means. the data model, not any binding, is </li></ul><ul><li>standard </li></ul><ul><li>drivers for use of metadata: content exchange / repositories [ X4L] </li></ul>
  9. 9. Implementing IMS Metadata in COSE 9 <ul><li>3. Discussion of issues (iii) </li></ul><ul><li>[ context: relation of IMS to other specs / standards ] </li></ul><ul><li>IMS and DC: what IMS spec says wrt DC </li></ul><ul><li>DC dot notation – from FAQ - “ Dublin Core metadata can be stored using </li></ul><ul><li>the meta element in the head of HTML documents. An informational IETF </li></ul><ul><li>RFC (2731) titled &quot;Encoding Dublin Core Metadata in HTML&quot; defines the </li></ul><ul><li>standard* way to do this”. – [ ? not ready for IMS dot notation] </li></ul><ul><li>IMS spec 1p2p1 v 1p2p2. SCORM 1p2 uses 1p2p1. </li></ul><ul><li>*the note says not standard </li></ul>
  10. 10. Implementing IMS Metadata in COSE 10 <ul><li>For more on COSE [history, developments, pedagogy, FAQ, </li></ul><ul><li>registration, reports, technical requirements / details etc ..] </li></ul><ul><li> </li></ul><ul><li>For more on interoperability </li></ul><ul><li> </li></ul><ul><li>For manual and downloading from support server </li></ul><ul><li>[need to register] </li></ul><ul><li> </li></ul>