University of Southern Queensland
Please tick these off as I go. 1. The web and the repository & The cloud and the desktop* 2. Knowledge and technology 3. Wild and curated content 4. Linked and isolated data & Ad-hoc and long-term access 5. Disciplinary and institutional systems / Scholars and service providers 6. Ubiquitous and personalized environments
* This is the big one!
Duncan: “A set of purposeful technologies brought together by standard interfaces for data exchange?” Peter: “I needed a single cover-all name for all the different projects we were working on in our , so that I could try to report to the powers that be in a more efficient way.”
The Web and the Repositories
We’re on the web, but are we of the web?
Show and tell
- Repositories need to understand renditions and rendering
- We’re working on small pieces of web-infrastructure that should apply across multiple repositories.
- We’re working on bringing the web to the desktop. <Insert demo of The Fascinator Desktop>
Issue: What will happen when vertically controlled computing platforms are the norm?
Does the desktop/lab/home PC become a server? Or will it live in the cloud?
Idea: How about ePUB as a repository packaging format?
(In my reading of the specs) ePUB is engineered for overloading:
Repository: (SIP/AIP/DIP?) - Serve the content using an in-page eReader (Paquete). - Let the package handle package semantics (pre-print, published version, presentation), repository can continue to handle streams. - Support viewers for data types for defined periods, such as JMOL for chemistry using something like ePUB’s fall-back mechanism and oEmbed.
- If all else fails: unzip the package and click ‘index.html’
- Use with eBook reader software/hardware.
Developer / repository manager:
- Add more packaging info – ORE, METS etc.
Idea: Making linked data, well, links
- Step 1: Approach your repository or ID provider, search for self Note: wrapping this link around some text is essentially meaningless. It’s not the semantic web it’s the old-web.
- Step 2: Copy the link labelled “Assert Authorship”
Word processor-proof linked data – part 2
We (like many others) are building a toolkit for web/repository construction. The key reasons we rolled our own are: - We care about having web-resources not just PDF. - We wanted to be able to deploy the application to the desktop (hence a Java app that can be deployed with Apache Solr).
1 At dinner on Monday night I was told that the ideas we’re pushing here at ADFI are “15 years ahead” of where the users are. Given that this paper was accepted, and doing some quick maths in my head I think that means that we have only 25 months before the things that we’re talking about here are considered relevant, given that we’re working in Internet time.