100 likes | 193 Views
CI Requirements. A first stab at. Purposes. NSDL To allow instructors to publish, discover, reuse, and directly employ learning objects in education. CI To facilitiate interactions between providers and consumers of NSDL entities. NSDL entities. Learning objects Structuring devices
E N D
CI Requirements A first stab at...
Purposes • NSDL • To allow instructors to publish, discover, reuse, and directly employ learning objects in education. • CI • To facilitiate interactions between providers and consumers of NSDL entities. Greg Janée • CITI futures kickoff • January 6-7, 2003
NSDL entities • Learning objects • Structuring devices • Recommendation devices • Classification devices • Educational standards • Services • Tools Greg Janée • CITI futures kickoff • January 6-7, 2003
NSDL entities • Learning objects • library’s raison d’ être • reusable, ergo: • self-contained • guaranteed availability, persistence • Structuring devices • collections • series, other hierarchies • lectures, courses, curricula Greg Janée • CITI futures kickoff • January 6-7, 2003
NSDL entities • Recommendation devices • annotations, reviews, usage • must be trustworthy • Classification devices • vocabularies, concept maps, etc. • Educational standards • (what is a standard?) • authoritative? Greg Janée • CITI futures kickoff • January 6-7, 2003
RECOMMENDATIONS learning object RIGHTS Learning object facets • DESCRIPTION • standardized • framework • object-specific • CONTEXT • place in larger structures • classifications • versions Greg Janée • CITI futures kickoff • January 6-7, 2003
Services • Service: • CI-provided services • support all NSDL entities • example: navigation of vocabularies; discovery of terms; robust references to terms • may be specifications only • Other services may be registered A network-accessible, programmatic function that operates on NSDL entities. Greg Janée • CITI futures kickoff • January 6-7, 2003
Tools • Tool: • CI-provided (?) and registered A network-accessible human interface that operates on NSDL entities via services. Greg Janée • CITI futures kickoff • January 6-7, 2003
What’s not in CI? • Communities • already handled by MERLOT, etc. • Specialized interfaces • Tools? • yes: needed to exploit services • no: not infrastructure Greg Janée • CITI futures kickoff • January 6-7, 2003
Implementation philosophy • Limit centrality • Enlist federated partners • currently-funded projects • permanently-funded libraries Greg Janée • CITI futures kickoff • January 6-7, 2003