Consuming Linked Data in Universities
•Download as PPTX, PDF•
0 likes•693 views
The document discusses how universities can consume linked data from various sources including data from their own institutions and others. It notes that most university data shares common objects like courses, degrees, people, and publications. While the "killer app" is sought to provide benefits like more funding or students, the real advantages of linked data are reducing development costs and enabling information sharing across the organization. Several examples are provided of early applications using linked data within universities including location browsers, podcast browsers, research collaboration tools, and annotation systems. The conclusion states that these examples represent initial steps and that linked data can more easily integrate profiles, courses and other data into existing university systems.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (7)
Similar to Consuming Linked Data in Universities
Similar to Consuming Linked Data in Universities (20)
More from Mathieu d'Aquin
More from Mathieu d'Aquin (20)
Consuming Linked Data in Universities
- 1. Consuming Linked Data from Universities Fouad Zablith, Mathieu d’Aquin Knowledge Media Institute (KMi) The Open University
- 2. Introduction More data is becoming available across universities. E.g.: data.open.ac.uk ecs Southampton Oxford Bristol data.*.ac.uk Most share common objects e.g. courses, degrees, people, publications, places, etc.
- 3. What do we do with that? In search for the killer app, i.e. The one that gives you more funding More students More impact Actually, the most common benefits of Linked Data are less direct. i.e. Reducing the cost of development, and information Sharing With implication on running cost of university core business e.g. course production, student support, management Not one killer app, but many uses across the organisation
- 6. Facebook Course Profiles App
- 8. Video Annotation and Search
- 9. wayOU
- 10. Conclusion The examples shown are the first steps towards producing and consuming Linked Data within universities With current central systems, e.g. Drupal used at the OU, it will be easier to benefit from Linked Data e.g. People’s profiles Course RDFa annotation
Editor's Notes
- Increasing availability of data through linked data, data.open.ac.uk, ecs, oxford, bristol, many will come up data.*.ac.uk. Explosion of data. Common object: courses, degrees, people, publications, places…
- What application does, why useful, iluustrate the point.e.G we have linked data about buildings. Simple browser using ordnance survey postcode. Not very impressive, but this can be done very quickly, reducing the cost of development.
- Having a mobile browser for podcats is now simple
- App where people cndelclare what courses they are taking and what what I intend to study and connect to other people. Simple application, problem: mainting the list of courses and info about them. Not it was much easier with sparql and ld.
- Useful for managers showing dynamics. Point: simple to do and integrate different sources of infoEasy to develop, like building, but also can combine data from different sources e.g. publications and projects involvement, event if data coming from different sources, and before data needed to be integrated.
- Useful: facilitate course production. Useful: taking more data that arre outside the OU ld.Easily connect things, reduce cost of course production. Searching here returns and bring together podcast, courses, people involved, making data easily accessible.
- Mobile application wher users can keep track of where they have been. Useful: can maintain your own kind of network of places with people. Engage the data by creating new connections around them. Data generated is RDF and can be generated and exported to the repository.Ld that supports the engagement of people within the organisation. Connect info about yourself, and push them to the repository.
- We had lot of example. Where this I going is having ld in many different things, usable and consumed in many different places in central systems of the uni. E.g. drupal, and people’s profiles. Most web rely on drupal. We’ll have pages that use and produce ldaccros the uny. The way consuming is by integrating it femo different places. E.g. by using drupal at ou, and natively create rdfa in website, use info e.g. people profile and extract information from them.People profiles: refer to android app, saying that app can declare workplace of person here.