On Thu, Oct 27, 2011 at 10:30:07AM +0100, Graham Triggs wrote: [snip] > Whilst bundles are poor for describing structure, they are useful bags > for organising content on broad themes. (i.e. whether it's a > thumbnail, original, structmaps, content related to a module). Without > a rigid definition of how to classify that content, it becomes harder
I'm not sure that what we need is bags. It seems to me that it's less interesting, for example, that these bitstreams are all THUMBNAILs than that this-bitstream IS_DERIVED_FROM that-bitstream USING a-method (where a-method in this case is thumbnail extraction). It gets back to extending metadata across all objects: a bitstream needs a set of labels to explain its origin, type, and use. In a sense this is just looking at bundles from a different angle, but I think it's important to help ourselves choose the most useful angles. What we call these concepts and how we represent them when we explain them will shape our thinking when we employ them. When we tell ourselves that "Item contains Bundle contains Bitstream", that imposes some expectations which may be unhelpful. "Item maps-to Bitstream(attributes)" should lead to quite different thinking. -- Mark H. Wood, Lead System Programmer [email protected] Asking whether markets are efficient is like asking whether people are smart.
pgp16MohpA5fK.pgp
Description: PGP signature
------------------------------------------------------------------------------ The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev
_______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
