On 17/04/2011 11:05, Alex Lydiate wrote:
> At which point, I guess, we're talking again of an aggregation of
> resources.
>
> We would also be talking, I suppose, of prescribing that most other
> resources are stored in Git, those that it can handle, whilst those it
> can't are elsewhere? Which is not really part of the whole 'publish
> anywhere' tip, unless what we end up putting into Git is a collection
> of description files.
>
> I think I am not diverted from the OAI-ORE trail :)
Maybe if we step back we can visualise this in a different way.
OAI-ORE is good for describing a finished project, and git is handy for
working projects.
So lets say you want to start making an OER tomorrow.
A git would be a great place to go to get a finished product, either for
remixing or using as is. But neither Git or OAI-ORE are great as a
"recipe book" ( - hat tip to CSAP-OER2 at Birmingham). Let says I want
to see all pictures used in sociology OERs (might be a good place to
start, build other services from) - so ideally you want some sort of
multiview system (i think this might be called a lattice file system).
So ideally you'd submit descriptor files (and maybe file size rather
than files?), which could populate as an OER, and wider
user-configurable views?
This way you could record works in progress, ingredients, and the
finished products / working projects too.
So it's kinda OAI-ORE, as long as you can have 1 file aggregations, and
1 file which changes.
|