The document discusses the OAI Object Reuse and Exchange (ORE) interoperability framework. It describes how ORE takes a resource-centric approach using the Web architecture and Semantic Web technologies like URIs, RDF, and Linked Data. The key aspect of ORE is that it publishes Resource Maps on the Web that instantiate, describe, and identify aggregations of web resources using the ORE vocabulary.
Keynote presentation delivered at ELAG 2013 in Gent, Belgium, on May 29 2013. Discusses Research Objects and the relationship to work my team has been involved in during the past couple of years: OAI-ORE, Open Annotation, Memento.
The presentation explores the trend towards a scholarly communication system that is friendly to machines. It presents 3 exhibits illustrating the trend and 1 exhibit illustrating inertia in the system. It makes the point that machine-actionability can be much easier achieved if content and metadata are available in Open Access and under a permissive Creative Commons license. It also observes that even with content and metadata openly available, new costs related to advanced tools to explore the scholarly record will emerge. Finally, it points at significant challenges regarding the persistence of the scholarly record in light of increasingly interconnected and actionable content and advanced tools to interact with it.
The slides were used for a plenary presentation at the LIBER 2011 Conference in Barcelona, Spain, on June 30 2011.
As the scholarly communication system evolves to become natively web-based and starts supporting the communication of a wide variety of objects, the manner in which its essential functions – registration, certification, awareness, archiving - are fulfilled co-evolves. This presentation focuses on the nature of the archival function based on a perspective of the future scholarly communication infrastructure. This presentation, prepared for a meeting in June 2014, is based on and updates a previous one that was prepared for a January 2014 meeting. The latter is available at http://www.slideshare.net/atreloar/scholarly-archiveofthefuture
Keynote presentation delivered at ELAG 2013 in Gent, Belgium, on May 29 2013. Discusses Research Objects and the relationship to work my team has been involved in during the past couple of years: OAI-ORE, Open Annotation, Memento.
The presentation explores the trend towards a scholarly communication system that is friendly to machines. It presents 3 exhibits illustrating the trend and 1 exhibit illustrating inertia in the system. It makes the point that machine-actionability can be much easier achieved if content and metadata are available in Open Access and under a permissive Creative Commons license. It also observes that even with content and metadata openly available, new costs related to advanced tools to explore the scholarly record will emerge. Finally, it points at significant challenges regarding the persistence of the scholarly record in light of increasingly interconnected and actionable content and advanced tools to interact with it.
The slides were used for a plenary presentation at the LIBER 2011 Conference in Barcelona, Spain, on June 30 2011.
As the scholarly communication system evolves to become natively web-based and starts supporting the communication of a wide variety of objects, the manner in which its essential functions – registration, certification, awareness, archiving - are fulfilled co-evolves. This presentation focuses on the nature of the archival function based on a perspective of the future scholarly communication infrastructure. This presentation, prepared for a meeting in June 2014, is based on and updates a previous one that was prepared for a January 2014 meeting. The latter is available at http://www.slideshare.net/atreloar/scholarly-archiveofthefuture
Specimen-level mining: bringing knowledge back 'home' to the Natural History ...Ross Mounce
A talk given at the Geological Society of London, UK on 2016/03/09 as part of the Lyell meeting on Palaeoinformatics. http://www.geolsoc.org.uk/lyell16 #lyell16
The common use by archaeologists of ubiquitous technologies such as computers and digital cameras means that archaeological research projects now produce huge amounts of diverse, digital documentation. However, while the technology is available to collect this documentation, we still largely lack community accepted dissemination channels appropriate for such torrents of data. Open Context (http://www.opencontext.org) aims to help fill this gap by providing open access data publication services for archaeology. Open Context has a flexible and generalized technical architecture that can accommodate most archaeological datasets, despite the lack of common recording systems or other documentation standards. Open Context includes a variety of tools to make data dissemination easier and more worthwhile. Authorship is clearly identified through citation tools, a web-based publication systems enables individuals upload their own data for review, and collaboration is facilitated through easy download and other features. While we have demonstrated a potentially valuable approach for data sharing, we face significant challenges in scaling Open Context up for serving large quantities of data from multiple projects.
Linking Universities - A broader look at the application of linked data and s...Mathieu d'Aquin
Presentation at the VIVO - International Research Network about Linked Universities, data.open.ac.uk, linkedup, linked data for universities, education and research.
The European Open Science Cloud: just what is it?Carole Goble
Presented at Jisc and CNI leaders conference 2018, 2 July 2018, Oxford, UK (https://www.jisc.ac.uk/events/jisc-and-cni-leaders-conference-02-jul-2018). The European Open Science Cloud. What exactly is it? In principle it is conceived as a virtual environment with open and seamless services for storage, management, analysis and re-use of research data, across borders and scientific disciplines. How? By federating existing scientific data infrastructures, currently dispersed across disciplines and Member States. In practice, what it is depends on the stakeholder. To European Research Infrastructures it’s a coordinated mission to organise and exchange their data, metadata, software and services to be FAIR – Findable, Accessible, Interoperable, Reusable – and to use e-Infrastructures, either EU or commercial. To EU e-Infrastructures offering data storage and cloud services, it’s a funding mission to integrate their services, policies and organisational structures, and to be used by the Research Infrastructures. To agencies it’s a means to promote Open Science, standardisation, cross-disciplinary research and coordinated investment with a dream of a “one stop shop” for researchers. And for Libraries?
Specimen-level mining: bringing knowledge back 'home' to the Natural History ...Ross Mounce
A talk given at the Geological Society of London, UK on 2016/03/09 as part of the Lyell meeting on Palaeoinformatics. http://www.geolsoc.org.uk/lyell16 #lyell16
The common use by archaeologists of ubiquitous technologies such as computers and digital cameras means that archaeological research projects now produce huge amounts of diverse, digital documentation. However, while the technology is available to collect this documentation, we still largely lack community accepted dissemination channels appropriate for such torrents of data. Open Context (http://www.opencontext.org) aims to help fill this gap by providing open access data publication services for archaeology. Open Context has a flexible and generalized technical architecture that can accommodate most archaeological datasets, despite the lack of common recording systems or other documentation standards. Open Context includes a variety of tools to make data dissemination easier and more worthwhile. Authorship is clearly identified through citation tools, a web-based publication systems enables individuals upload their own data for review, and collaboration is facilitated through easy download and other features. While we have demonstrated a potentially valuable approach for data sharing, we face significant challenges in scaling Open Context up for serving large quantities of data from multiple projects.
Linking Universities - A broader look at the application of linked data and s...Mathieu d'Aquin
Presentation at the VIVO - International Research Network about Linked Universities, data.open.ac.uk, linkedup, linked data for universities, education and research.
The European Open Science Cloud: just what is it?Carole Goble
Presented at Jisc and CNI leaders conference 2018, 2 July 2018, Oxford, UK (https://www.jisc.ac.uk/events/jisc-and-cni-leaders-conference-02-jul-2018). The European Open Science Cloud. What exactly is it? In principle it is conceived as a virtual environment with open and seamless services for storage, management, analysis and re-use of research data, across borders and scientific disciplines. How? By federating existing scientific data infrastructures, currently dispersed across disciplines and Member States. In practice, what it is depends on the stakeholder. To European Research Infrastructures it’s a coordinated mission to organise and exchange their data, metadata, software and services to be FAIR – Findable, Accessible, Interoperable, Reusable – and to use e-Infrastructures, either EU or commercial. To EU e-Infrastructures offering data storage and cloud services, it’s a funding mission to integrate their services, policies and organisational structures, and to be used by the Research Infrastructures. To agencies it’s a means to promote Open Science, standardisation, cross-disciplinary research and coordinated investment with a dream of a “one stop shop” for researchers. And for Libraries?
These slides accompany the LDOW2010 paper "An HTTP-Based Versioning Mechanism for Linked Data". The paper is available at http://arxiv.org/abs/1003.3661. It describes how the combination of the Memento (Time Travel for the Web) framework, and a resource versioning approach that is aligned both with the Cool URI notion and with Tim Berners-Lee concept of Time-Generic and Time-Specific, yields the ability to collect current and prior versions of resource merely using "follow your nose" HTTP navigation. The proposed combination further extends the value of a URI, and allows the emergence of a novel realm of temporal Web applications.
Slides used for a presentation at the CNI 2013 Fall meeting. Discusses the problem domain of the Hiberlink project, a collaboration between the Los Alamos National Laboratory and the University of Edinburgh, funded by the Andrew W. Mellon Foundation. Hiberlink investigates reference rot in web-based scholarly communication.
This presentation introduces the Memento solution to allow time travel on the Web. Slides used at the first presentation about Memento at the Library of Congress, November 16 2009. Please consult the February 2010 slides (http://www.slideshare.net/hvdsomp/memento-updated-technical-details-february-2010) for up-to-date technical details. More info at http://www.mementoweb.org
Presentation for PIDapalooza 2016. PIDs need to be used to achieve their intended persistence. Our research (reported at WWW2016, see http://arxiv.org/1602.09102) found that a disturbing percentage of references to papers that have DOIs actually use the landing page HTTP URI instead of the DOI HTTP URI. The problem is likely related to tools used for collecting references such as bookmarks and reference managers. These select the landing page URI instead of the DOI URI because the former is what's available in the address bar. It can safely be assumed that the same problem exists for other types of PIDs. The net result is that the true potential of PIDs is not realized. In order to ameliorate this problem we propose a Signposting pattern for PIDs (http://signposting.org/identifier/). It consists of adding a Link header to HTTP HEAD/GET responses for all resources identified by a DOI, including the landing page and content resources such as "the PDF" and "the dataset". The Link header contains a link, which points with the "identifier" relation type to the DOI HTTP URI. When such a link is available, tools can automatically discover and use the DOI URI instead of the other URIs (landing page, PDF, dataset) associated with the DOI-identified object.
Memento: Big Leaps Towards Seamless Navigation of the Web of the PastHerbert Van de Sompel
These slides provide an explanation of the Memento Framework (time travel for the Web) from the perspective of resource versioning. It also details progress that has been made with deploying the framework since it was first introduced in November 2009, including standardization, development of tools, and advocacy. In addition, it touches upon new challenges (discovery, branding) and announces plans to make transactional Web archiving software available in the course of 2011.
DBpedia Archive using Memento, Triple Pattern Fragments, and HDTHerbert Van de Sompel
DBpedia is the Linked Data version of Wikipedia. Starting in 2007, several DBpedia dumps have been made available for download. In 2010, the Research Library at the Los Alamos National Laboratory used these dumps to deploy a Memento-compliant DBpedia Archive, in order to demonstrate the applicability and appeal of accessing temporal versions of Linked Data sets using the Memento “Time Travel for the Web” protocol. The archive supported datetime negotiation to access various temporal versions of RDF descriptions of DBpedia subject URIs.
In a recent collaboration with the iMinds Group of Ghent University, the DBpedia Archive received a major overhaul. The initial MongoDB storage approach, which was unable to handle increasingly large DBpedia dumps, was replaced by HDT, the Binary RDF Representation for Publication and Exchange. And, in addition to the existing subject URI access point, Triple Pattern Fragments access, as proposed by the Linked Data Fragments project, was added. This allows datetime negotiation for URIs that identify RDF triples that match subject/predicate/object patterns. To add this powerful capability, native Memento support was added to the Linked Data Fragments Server of Ghent University.
In this talk, we will include a brief refresher of Memento, and will cover Linked Data Fragments, Triple Pattern Fragments, and HDT in more detail. We will share lessons learned from this effort and demo the new DBpedia Archive, which, at this point, holds over 5 billion RDF triples.
The Open Archives Initiative Object Reuse and Exchange ProjectRIBDA 2009
Michael L. Nelson
Digital Library Research & Prototyping Team
Research Library
Los Alamos National Laboratory
Department of Computer Science
Old Dominion University
myExperiment and the Rise of Social MachinesDavid De Roure
Talk at hubbub 2012, Indianapolis, 25 September 2012. The talk introduces myExperiment and Wf4Ever, discusses the future of research communication including FORCE11, and introduces the SOCIAM project (Theory and Practice of Social Machines) which launches in October 2012.
Jean-Claude Bradley presents on "Peer Review and Science2.0: blogs, wikis and social networking sites" as a guest lecturer for the “Peer Review Culture in Scholarly Publication and Grantmaking” course at Drexel University. The main thrust of the presentation is that peer review alone is not capable of coping with the increasing flood of scientific information being generated and shared. Arguments are made to show that providing sufficient proof for scientific findings does scale and weakens the tragedy of the trusted source cascade.
Using Architectures for Semantic Interoperability to Create Journal Clubs for...James Powell
In certain types of _slow burn_ emergencies, careful accumulation and evaluation of information can offer a crucial advantage. The SARS outbreak in the first decade of the 21st century was such an event, and ad hoc
journal clubs played a critical role in assisting scientific and technical responders in identifying and developing various strategies for halting what could have become a dangerous pandemic. This paper describes a process for leveraging emerging semantic web and digital library architectures and standards to (1) create a focused collection of bibliographic metadata, (2) extract semantic information, (3) convert it to the Resource Description Framework /Extensible Markup Language (RDF/XML),
and (4) integrate it so that scientific and technical responders can share and explore critical information in the collections.
systems.
IP LodB project (for more details see iplod.io ) capitalizes on LOD database thinking, to build bridges between patented information and scientific knowledge, whilst focusing on individuals who codify new knowledge and their connected organizations, including those who apply patents in new products and services.
As main outputs the IP LodB produced an intellectual property rights (IPR) linked open data (LOD) map (IP LOD map), and has tested the linkability of the European patent (EP) LOD database, whilst increasing the uniqueness of data using different harmonization techniques.
These slides were developed for NIPO workshop
2012 03-28 Wf4ever, preserving workflows as digital research objectsStian Soiland-Reyes
Presented on 2012-03-28 at EGI Community Forum 2012, Munich.
http://www.wf4ever-project.org/
http://purl.org/wf4ever/model
http://cf2012.egi.eu/
https://www.egi.eu/indico/sessionDisplay.py?sessionId=66&confId=679#20120328
Similar to An Overview of the OAI Object Reuse and Exchange Interoperability Framework (20)
Presentation about reference rot given at the Complexity Science Hub in Vienna, November 2021.
Links to web resources frequently break (link rot), and linked content can change at unpredictable rates (content drift). These dynamics of the Web are detrimental when references to web resources provide evidence or supporting information.
This presentation will report on research that assessed the extent of these problems for links to web resources in scholarly literature, by using three vast corpora of publications and a range of public web archives. It will also describe the Robust Link approach that offers a proactive, uniform, and machine-actionable way to combat link rot and content drift. Finally, it will introduce the Robustify web service and API that was devised to generate links that remain functional over time, paying special attention to challenges related to deploying infrastructure that is required to be long lasting.
Researcher Pod: Scholarly Communication Using the Decentralized WebHerbert Van de Sompel
The presentation provides an overview of the motivation and direction of the Mellon-funded Researcher Pod project that investigates technical aspects of scholarly communication in a decentralized web setting.
Presentation for a workshop about persistent identifiers organized by the Royal Library of The Netherlands and DANS. Highlights the non-trivial commitments required of all parties involved in persistent identifier systems to actually keep links based on persistent identifiers ... err ... persistent.
Various FAIR criteria pertaining to machine interaction with scholarly artifacts can commonly be addressed by means of repository-wide affordances that are uniformly provided for all hosted artifacts rather than through artifact-specific interventions. If various repository platforms provide such affordances in an interoperable manner, devising tools - for both human and machine use - that leverage them becomes easier.
My involvement, over the years, in a range of interoperability efforts has brought the insight that two factors strongly influence adoption: addressing a burning issue and delivering a KISS solution to tackle it. Undoubtedly, FAIR and FAIR DOs are burning issues. FAIR Signposting <https://signposting.org/FAIR/> is an ad-hoc repository interoperability effort that squarely fits in this problem space and that purposely specifies a KISS solution, hoping to inspire wide adoption.
Registration / Certification Interoperability Architecture (overlay peer-review)Herbert Van de Sompel
Presentation for the COAR meeting on Overlay Peer-Review held at INRIA, Paris, France. It provides overall context regarding a scholarly communication system in which the core functions of scholarly communication (registration, certification, awareness, archiving) are implemented in a decoupled manner and whereby each function can simultaneously be fulfilled by different parties, potentially in different ways. It shows how notifications can be used to achieve loosely coupled, point-to-point interoperability in such an environment, zooming in on interoperability between registration and certification aka interoperability between repositories and overlay peer-review services.
Slides used for a keynote presentation at the VIVO 2019 Conference in Podgorica, Montenegro.
Abstract: The invitation to present a keynote at the VIVO Conference and the goal of the VIVO platform, as stated on the DuraSpace site, to create an integrated record of the scholarly work of an organisation reminded me of various efforts that I have been involved in over the past years that had similar goals. EgoSystem (2014) attempted to gather information about postdocs that had left the organisation, leaving little or no contact details behind. Autoload (2017), an operational service, discovers papers by organisational researchers in order to upload them in the institutional repository. myresearch.institute (2018), an experiment that is still in progress, discovers artefacts that researchers deposit in web productivity portals and subsequently archives them. More recently, I have been involved in thinking about the future of NARCIS, a portal that provides an overview of research productivity in The Netherlands. The approach taken in all these efforts share a characteristic motivated by a desire to devise scalable and sustainable solutions: let machines rather than humans do the work. In this talk, I will provide an overview of these efforts, their motivations, the challenges involved, and the nature of success (if any).
Presentation for PIDapalooza 2019, Dublin, Ireland.
The Scholarly Orphans project, funded by the Andrew W. Mellon Foundation, explores technical approaches aimed at capturing and archiving scholarly artifacts that researchers deposit in web productivity portals as a means to collaborate and communicate with their peers. These artifacts are not collected by other frameworks aimed at archiving the scholarly record (e.g., LOCKSS, Portico, Institutional Repositories) and are only incidentally captured by web archives. The project explores an institution-driven approach inspired by web archiving. To demonstrate the ongoing thinking, the project has devised an experimental automated pipeline that continuously discovers, captures, and archives artifacts. These are created by actual researchers who, for the purpose of the experiment, were virtually enlisted in a fictive research institution. A portal at myresearch.institute provides an overview of the artifacts that were discovered and provides access to archived versions stored in both an institutional and a cross-institutional archive. The set-up leverages a range of technologies that share a flavor of persistence: Memento, Memento Tracer, Robust Links, Signposting.
As a memento of my last week of working at LANL, I put together a slide deck that provides an overview of major efforts conducted during the time I was there.
Presentation given at EuropeanaTech 2018 in Rotterdam, The Netherlands. Provides a summary of insights gained from working for about a decade on challenges related to temporal aspects of the web, persistence.
"Scholarly Communication: Deconstruct and Decentralize" was presented at the Fall 2017 Meeting of the Coalition for Networked Information. It explores working towards a Scholarly Commons by applying decentralized web ideas to scholarly communication.
Looks at hyperlinks from the perspective of a managed collection of resources for which link persistence/integrity is considered a quality of service concern. Distinguishes between links into other managed collections and to the web at large. Considers link rot and content drift.
This slide deck provides an overview of proposals to use HTTP Links as a means to address some long standing problems related to scholarly resources on the web.
This slide deck provides an overview of proposals to use HTTP Links as a means to address some long standing problems related to scholarly resources on the web.
These slides go with the paper "Reminiscing About 15 Years of Interoperability Efforts" which is available at http://dx.doi.org/10.1045/november2015-vandesompel
Slides were used for a presentation at the Fall 2015 Membership Meeting of the Coalition for Networked Information.
This presentation looks back at several efforts, conducted in the past fifteen years, aimed at establishing interoperability for web-based scholarly communication. It tries to characterize the perspectives/approaches taken by these efforts and, based upon that, proposes an HATEOS-based approach to interlink scholarly nodes on the web. This was first presented at the Research Data Alliance meeting in Paris, France, September 22 2015.
Extended version of slides presented at the "404/File Not Found" symposium held at Georgetown University on October 24 2014, see http://www.law.georgetown.edu/library/404/ . The presentation provides a brief overview of the link/reference rot problem and then discusses three complimentary strategies to combat it: Pro-actively capturing web resources that are linked from a seed collection; Referencing the captures by means of annotated links; Accessing the captures using Memento infrastructure.
This presentation introduces ResourceSync, a specification aimed to enable web-based synchronization of resources. The specification is the result of a collaboration between NISO and the Open Archives Initiative funded by the Sloan Foundation and JISC. The proposed resource synchronization approach is based on several existing specifications (e.g. Sitemaps, PubSubHubbub, well-known URI) and is aligned with common architectural principles (e.g. REST, follow your nose).
A 15 minute video version of these slides is available at https://www.youtube.com/watch?v=ASQ4jMYytsA
This presentation provides an overview of the Memento "Time Travel for the Web" framework that is aligned with the stable version of the Memento protocol, specified in RFC 7089.
The slides were used to accompany an overview of the outcomes of the ResourceSync project at the 2014 Spring Membership Meeting of the Coalition for Networked Information (CNI).
The launch of ResourceSync, a joint project of the National Information Standards Organization (NISO) and the Open Archives Initiative (OAI) funded by the Alfred P. Sloan Foundation, was motivated by the ubiquitous need to synchronize resources for applications in the realm of cultural heritage and research communication. After an initial problem definition and scoping phase, the project has designed, specified, and tested a framework for web-based synchronization that is based on SiteMaps, a protocol widely used by web servers to advertise the resources they make available to search engines for indexing. This choice allows repositories to address both search engine optimization and resource synchronization needs using the same technology.
The ResourceSync framework specifies various modular capabilities that a repository can support in order to allow third party systems to remain synchronized with its evolving resources. For example, a Resource List provides an inventory of resources whereas a Change List details resources that were created, deleted or updated during a given temporal interval. Support for capabilities can be combined in order to meet local or community requirements. The framework specifies capabilities that require a third party to recurrently poll for up-to-date information about a repositories’ resources but also publish/subscribe capabilities that keep third parties informed about changes through notifications, thereby significantly reducing synchronization latency.
Persistent Identifiers and the Web: The Need for an Unambiguous MappingHerbert Van de Sompel
Presentation given at the International Digital Curation Conference in San Francisco, February 26 2014. Highlights the lack of machine-actionability of persistent identifiers assigned to scholarly communication assets. Proposes an approach to address the issue that meets requirements that take into account the changing nature of web based research communication. A draft paper provides more details: http://public.lanl.gov/herbertv/papers/Papers/2014/IDCC2014_vandesompel.pdf
"Impact of front-end architecture on development cost", Viktor TurskyiFwdays
I have heard many times that architecture is not important for the front-end. Also, many times I have seen how developers implement features on the front-end just following the standard rules for a framework and think that this is enough to successfully launch the project, and then the project fails. How to prevent this and what approach to choose? I have launched dozens of complex projects and during the talk we will analyze which approaches have worked for me and which have not.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
Search and Society: Reimagining Information Access for Radical FuturesBhaskar Mitra
The field of Information retrieval (IR) is currently undergoing a transformative shift, at least partly due to the emerging applications of generative AI to information access. In this talk, we will deliberate on the sociotechnical implications of generative AI for information access. We will argue that there is both a critical necessity and an exciting opportunity for the IR community to re-center our research agendas on societal needs while dismantling the artificial separation between the work on fairness, accountability, transparency, and ethics in IR and the rest of IR research. Instead of adopting a reactionary strategy of trying to mitigate potential social harms from emerging technologies, the community should aim to proactively set the research agenda for the kinds of systems we should build inspired by diverse explicitly stated sociotechnical imaginaries. The sociotechnical imaginaries that underpin the design and development of information access technologies needs to be explicitly articulated, and we need to develop theories of change in context of these diverse perspectives. Our guiding future imaginaries must be informed by other academic fields, such as democratic theory and critical theory, and should be co-developed with social science scholars, legal scholars, civil rights and social justice activists, and artists, among others.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
Neuro-symbolic is not enough, we need neuro-*semantic*
An Overview of the OAI Object Reuse and Exchange Interoperability Framework
1. An Overview of the OAI Object Reuse
and Exchange Interoperability
Framework
<http://www.openarchives.org/ore/toc>
Herbert Van de Sompel - herbertv@lanl.gov
Digital Library Research & Prototyping Team
Research Library
Los Alamos National Laboratory, USA
OAI-ORE was funded
by the Andrew W. Mellon Foundation, the National
Science Foundation, JISC, and Microsoft
The ORE Editors are: Carl Lagoze (Cornell U.), Herbert Van de Sompel (LANL), Pete Johnston (Eduserv Found.),
Michael Nelson (Old Dominion University), Robert Sanderson (U. of Liverpool), Simeon Warner (Cornell U.)
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
2. OAI Object Reuse and Exchange: Support
• The Andrew W. Mellon Foundation
• The Coalition for Networked Information
• Joint Information Systems Committee
• Microsoft Corporation
• The National Science Foundation
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
3. OAI Object Reuse and Exchange: Technical Experts
ORE Technical Committee
Chris Bizer Freie Universität Berlin
Les Carr University of Southampton
Tim DiLauro Johns Hopkins University
Leigh Dodds Ingenta
David Fulker UCAR
Tony Hammond Nature Publishing Group
Pete Johnston Eduserv Foundation
Richard Jones HP Labs
Carl Lagoze Cornell University
Peter Murray OhioLINK
Michael Nelson Old Dominion University
Ray Plante NCSA and National Virtual Observatory
Rob Sanderson University of Liverpool
Herbert Van de Sompel Los Alamos National Laboratory
Simeon Warne r Cornell University
Jeff Young OCLC
ORE Liaison Group
Leonardo Candela Consiglio Nazionale delle Ricerche - DRIVER
Tim Cole University of Illinois Urbana-Champaign - Aquifer
Julie Allinson JISC
Jane Hunter University of Queensland - DEST
Savas Parastatidis Microsoft Corporation
Sandy Payette Fedora Commons
Thomas Place University of Tilburg - DARE
Andy Powell Eduserv Foundation - DCMI
Robert Tansley Google, Inc. - DSpace
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
4. OAI Object Reuse and Exchange
Subject: Aggregations of Web resources
Approach: Publish Resource Maps to the Web that
Instantiate, Describe, and Identify Aggregations
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
5. OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
6. Instantiate, Describe, and Identify Aggregations
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
7. 1. The URI of the human
Aggregations start page for the arXiv
document.
2. The formats in which the
document is available:
constituents of the
aggregation.
3. The title of the document.
4. The authors of the
document.
5. The creation and last
modification date of the
document.
6. Identifiers of entities that are
in some manner equivalent to
this document. For example,
the DOI of a peer-reviewed
article.
7. The versions of this
document.
8. Links to other arXiv
documents in the same
collection.
9. Citations made by this
document, and citations it
received from other
documents.
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
8. Aggregations!
Flickr Set Items
http://www.flickr.com/photos/fortphoto/sets/72157594190371016/
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
9. Aggregations!!
Resolutions
http://www.flickr.com/photos/fortphoto/sets/72157594190371016/
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
10. Object Reuse and Exchange: A Resource-Centric Approach
• Prior efforts had the repository and metadata records as the center of the
interoperability thinking:
o Including OAI-PMH
o Including initial OAI-ORE thinking cf. “Augmenting Interoperability across
Scholarly Repositories”
o Unclear what the metadata records were about …
• This approach does not vibe well with the Web:
o The Web Architecture knows resources and URIs
o Requires special treatment by applications that dominate the Web.
- Keep dreaming!
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
11. Object Reuse and Exchange: A Resource-Centric Approach
• Fundamental shift in the chosen approach towards interoperability
• The Web Architecture as the platform for interoperability
• Resources, URIs, and representations as
the tools of the ORE interoperability trade
• De-facto integration with existing Web
applications
• Potential of adoption by other
communities
• Potential of tools created by other
communities
• ….
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
12. Foundations of the OAI-ORE solution to handle Aggregations
• Web Architecture
o <http://www.w3.org/TR/webarch/>
• Semantic Web, Resource Description Framework (RDF)
o <http://www.w3.org/TR/rdf-primer/>
• Semantic Web, Linked Data, Cool URIs for the Semantic Web
o <http://linkeddata.org/>
o <http://www4.wiwiss.fu-berlin.de/bizer/pub/LinkedDataTutorial/>
o <http://www.w3.org/TR/cooluris>
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
13. W3C Web Architecture
Representation 2
URI
Represents
Identifies
Resource Content Negotiation
The tools we have to solve the Represents
interoperability problem are:
• Resource Representation 1
• URI
• Representation
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
14. Semantic Web, Resource Description Framework (RDF)
URI
Semantic RDF
Web
Vocabularies
The tools we have to solve the
interoperability problem are:
• URI
• RDF
• Vocabularies
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
15. Resource Description Framework (RDF)
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
16. Resource Description Framework (RDF)
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
17. Resource Description Framework (RDF)
Subject Predicate Object
R1 hasChapter R2
R1 hasChapter R3
R3 follows R2
R1 createdBy “Herbert” Triples
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
18. Semantic Web, Linked Data
~ March 2008
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
19. Semantic Web, Linked Data
4.5 billion RDF triples,
interlinked by 180 million
RDF links March 2009
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
20. Semantic Web
• On the Web as we know it, URIs are for documents.
• On the Semantic Web, things are also given URIs:
o Real world objects, e.g. a person, a star, a car, …
o Concepts, ideas, abstractions, …
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
21. Semantic Web, Linked Data
• In order to allow distinguishing between URIs that identify documents
and URIs that identify things, a convention is introduced:
o The document-URI has a Representation (the document)
o The thing-URI has no Representation
• So how do we ever find out what the thing is about?
o Publish a document about the thing at a URI different than the
thing-URI;
o In that document, describe the thing;
o Use a network mechanism to point from the thing-URI to its
describing document-URI.
o This means using HTTP URIs for both the thing-URI and its
describing document-URI.
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
22. Cool URIs for the Semantic Web
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
23. Cool URIs for the Semantic Web
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
24. Cool URIs for the Semantic Web
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
25. Cool URIs for the Semantic Web
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
26. Semantic Web, Linked Data (again)
• The Linked Data Tutorial has recommendations regarding the useful
information to return about a thing resource:
o The description: all triples with the thing-URI as subject
o Backlinks: all triples with the thing-URI as object (sometimes
redundant but allows bidirectional traversal)
o Related descriptions: triples about resources related to the thing
resource
o Metadata: information about the document that contains all of the
above: e.g. authorship, rights, publication datetime, etc.
o Syntax: at least RDF/XML
• Linked Data Tutorial also has recommendations about which RDF
features not to use for Linked Data publishing.
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
27. OAI Object Reuse and Exchange: The Approach
Subject: How to handle an Aggregation
of Web resources?
Approach: Publish Resource Maps to the Web that
Instantiate, Describe, and provide an Identity for
the Aggregation
Aggregation: a thing resource
Resource Map: a document resource
that describes an Aggregation
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
28. The Web
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
29. An Aggregation and the Web
• Resources of an
aggregation are
distinct URI-identified
Web resources
• To handle
aggregations, missing
are:
o The boundary
that delineates
the aggregation in
the Web
o An identity (URI)
for the
aggregation
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
30. Introduce a Resource that stands for the Aggregation
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
31. Publish a Resource Map that describes the Aggregation
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
32. Discover the Resource Map via the Aggregation
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
33. OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
34. OAI Object Reuse and Exchange: The Basics
Aggregation
Aggregated Resources
ore:aggregates
Resource Map
ore:describes
Relationships and Types
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
35. It starts with some resources that belong together
HTTP GET
This resource has URI AR-1
The resource has a representation
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
36. Introduce the Aggregation
This resource is an Aggregation
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
37. Express the ore:aggregates relationship
The inverse is ore:isAggregatedBy
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
38. The ore:aggregates relationship
This resource is an Aggregated Resource
Aggregated Resources are just resources
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
39. The ore:aggregates relationship
Aggregated Resources can be aggregated by multiple Aggregations
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
40. Introduce the Resource Map
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
41. Express the ore:describes relationship
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
42. The ore:isDescribedBy relationship
The inverse is ore:isDescribedBy; subproperty of rdfs:seeAlso
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
43. Express metadata about the Resource Map
This corresponds to metadata from the Linked Data recommendations
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
44. A Resource Map can describe a lot …
This corresponds to the description, related descriptions, backlinks, metadata
from the Linked Data recommendations
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
45. But minimally it describes this …
This corresponds to the description (minimal), and metadata from the Linked
Data recommendations
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
46. A lot about the Aggregation and the Aggregated Resources
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
47. A Resource Map can describe a lot …
but the graph expressed by the Resource Map must be connected
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
48. OAI Object Reuse and Exchange: Advanced Concepts
Aggregated Resource is member of another Aggregation ; is itself
an Aggregation
ore:isAggregatedBy ; ore:isDescribedBy
Expressing non-protocol-based URIs
ore:similarTo
Proxy: Aggregated Resource in Context of an Aggregation
ore:isProxyFor ; ore:isProxyIn
Authoritative Resource Maps
Lineage of an Aggregated Resource
ore:lineage
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
49. OAI Object Reuse and Exchange: Advanced 1
Aggregated Resource member of another Aggregation
ore:isAggregatedBy
Aggregated Resource is an Aggregation
ore:isDescribedBy
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
50. A resource is an Aggregated Resource is another Aggregation
Use ore:isAggregatedBy to express membership of another Aggregation
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
51. An Aggregated Resource is itself an Aggregation
Use ore:isDescribedBy to point at a Resource Map that describes that Aggregation
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
52. OAI Object Reuse and Exchange: Advanced 2
Expressing non-protocol-based URIs
ore:similarTo
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
53. The ore:similarTo relationship
To express non-protocol-based URIs …
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
54. The ore:similarTo relationship
DOI-1 connects the graphs
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
55. OAI Object Reuse and Exchange: Advanced 3
Proxy: Aggregated Resource in Context of an
Aggregation
ore:isProxyFor
ore:isProxyIn
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
56. Alice and Bob observe cats in Eve’s Lab
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
57. Alice and Bob observe cats in Eve’s Lab
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
58. Alice observes cats in Eve’s Lab
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
59. An agent merges information and gets confused
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
60. What did we mean by hasNext?
• Resource Map 1: Bob’s observation on 2008-04-02 is the next
observation after Alice’s observation on 2008-04-01 in the sequence
of observations in Eve’s Lab
• Resource Map 2: Alice’s observation on 2008-04-03 is the next
observation after her observation on 2008-04-01 in the sequence of
Alice’s observations in Eve’s Lab
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
61. Modeling a Resource in the Context of an Aggregation: Proxy
• Two components:
o The (Aggregated) Resource
o The context in which it is aggregated, i.e. the Aggregation
• In the Web Architecture, a new concept needs a new resource (and
hence URI): we named it the Proxy
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
62. Modeling a Resource in the Context of an Aggregation: Proxy
ore:proxyFor and ore:proxyIn to introduce a Proxy for an Aggregated Resource
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
63. Alice’s observations in context
hasNext expressed as a relationship between Proxies
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
64. Citation to a resource in a specific context
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
65. OAI Object Reuse and Exchange: Advanced 4
Multiple Resource Map Serializations
Authoritative Resource Maps
e.g. HTTP 303
Discovery of Resource Maps
ore:isDescribedBy
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
66. Relationship between Aggregation and Resource Map
• An Aggregation is a Resource with a URI
• A Resource Map is a Resource with a URI
• A Resource Map asserts (identifies) and describes one
Aggregation
o A Resource is an Aggregation due to an assertion by (at
least) one Resource Map
o A Resource Map must have one representation
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
67. Multiple Resource Maps for an Aggregation; serializations
Aggregation Graph shared by both Resource Maps. Also Proxies shared.
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
68. Multiple Resource Maps for an Aggregation; discovery
Use ore:isDescribedBy to facilitate discovery of other Resource Maps
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
69. Multiple Resource Maps for an Aggregation; authoritative
Authoritative: dereference of URI of Aggregation leads to Resource Map
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
70. Authoritative and. Non-Authoritative Resource Maps
• Authoritative
o Created by same authority (usually)
o Must be minimally equivalent (same Aggregated Resources
and Proxies)
o Should assert mutual existence (ore:isDescribedBy)
• Non-authoritative
o Best practice is to not create them
o Assert your own Aggregation instead
o Use rdfs:seeAlso to assert relationship between two
Aggregations
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
71. OAI Object Reuse and Exchange: Advanced 5
Lineage of an Aggregated Resource
ore:lineage
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
72. An Aggregated Resource originated in another Aggregation
ore:lineage is a relationship between Proxies
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
73. • Version 1.0 released October
17th 2008
• ORE Primer
• Atom Resource Maps
• RDF/XML Resource Maps
• RDFa Resource Maps
• HTTP implementation
• Discovery of Resource Maps
• Data Model
• Vocabulary
• Tools and Resources
• OAI-ORE Google Group
http://www.openarchives.org/ore/toc
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
74. OAI Object Reuse and Exchange
Playing ORE in two worlds
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
75. Interoperability Stacks
Atom profiles, Vocabularies,
APP, Special- SPARQL
purpose APIs
Feed RDF, RDF
technologies, serializations
RSS, Atom
HTTP URI HTTP URI
Web 2.0 Semantic
Web; Linked
Data
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
76. Interoperability Stacks
ORE add-ons for Atom profiles, Vocabularies, ORE terms,
Atom APP, special- SPARQL dcterms, foaf
purpose APIs
Atom ReM Feed RDF, RDF RDF-based data
technologies, serializations model; HTTP
RSS, Atom 303; RDF/XML
ReM, RDFa
ReM
HTTP URI for HTTP URI HTTP URI HTTP URI for
Aggregation, Aggregation,
Resource Map, Resource Map,
Proxies Proxies
ORE Web 2.0 Semantic ORE
Web; Linked
Data
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
77. OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
78. Interoperability Stacks
ORE extensions Atom profiles, Vocabularies, ORE terms,
for Atom APP, special- SPARQL dcterms, foaf
purpose APIs
Atom ReM Feed RDF, RDF RDF-based data
technologies, serializations model; HTTP
RSS, Atom 303; RDF/XML
ReM, RDFa
ReM
HTTP URI for HTTP URI HTTP URI HTTP URI for
Aggregation, Aggregation,
Resource Map, Resource Map,
Proxies Proxies
ORE Web 2.0 Semantic ORE
Web; Linked
Data
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
79. Atom
• Feed technology
• Attempt to rationalize RSS 1.x, 2.x divergence
• IETF FRC 4287
o http://www.ietf.org/rfc/rfc4287
• Encoding is up-to-date with current XML standards
o namespaces
o Relax-NG schema
• Content model
o Distinguishes between metadata and content (plain text, HTML, base-64
binary, linked content)
• Relationship types defined in IESG Atom Link Relations registry
o http://www.iana.org/assignments/link-relations.html
• Well-defined extensibility model
o Elements from external namespaces
o Relationships from external namespaces
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
80. Atom Feed/Entry Structure
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
81. An Atom Feed in XML
<?xml version=quot;1.0quot; encoding=quot;utf-8quot;?>
<feed xmlns=quot;http://www.w3.org/2005/Atomquot;> Feed
<title>Dan’s Blog</title>
<link @rel=“self” href=quot;http://netzoid.com/blog/quot;/> Feed
<updated>2007-11-07T18:30:02Z</updated> Meta
<author>
<name>Dan Diephouse</name>
</author>
<id>urn:uuid:60a76c80-d399-11d9-b91C-0003939e0af6</id>
<entry>
…
<entry>
</feed>
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
82. An Atom Entry in XML
<?xml version=quot;1.0quot; encoding=quot;utf-8quot;?>
<feed xmlns=quot;http://www.w3.org/2005/Atomquot;>
…
<entry> Entry
<title>Building services with AtomPub</title>
<link @rel=“self” href=quot;http://netzoid.com/blog/122cquot;/>
<link @rel=“alternate” Entry
href=quot;http://netzoid.com/blog/building_atompub.htmquot;/> Meta
<id>urn:uuid:1225c695-cfb8-4ebb-aaaa-80da344efa6a</id>
<updated>2007-11-07T18:30:02Z</updated>
<content>
(optional. by-value or by-reference. Must provide Entry
a <summary> if by-reference or by-value is base64) Content
</content>
</entry>
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
83. Using Atom Extensibility: GData Example
Click Here
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
84. ORE Atom Serialization
• Result must be valid Atom
• Don’t distort Atom semantics
• Indicate this is an ORE Atom Entry by specifying a <category
term=quot;http://www.openarchives.org/ore/terms/Aggregation”>
• Convey as much information as possible about the Aggregation
using native Atom elements
o But /entry/id, /entry/updated, /entry/published, /entry/rights
are about the Entry/ResourceMap
• Use Atom extensibility:
o Express relationships of ORE model by means of special
purpose ORE URIs
o Use <ore:triples> extension element to convey information
about Aggregated Resources (and some about Aggregation)
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
85. ORE Atom Example
Click Here
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
86. ORE Atom Example
<link rel=“alternate” …>
Entry
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
87. Entry URI
atom:id mandatory (atom)
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
88. URI-A of Aggregation
URI-A
mandatory (ORE)
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
89. URI-R of Resource Map
URI-R
mandatory (ORE)
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
90. URIs of Aggregated Resources
URI-AR
mandatory (ORE)
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
91. URI of Splash Page
URI-S
atom:link@rel=“alternate”: mandatory if no atom:content (atom)
recommended (ORE)
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
92. Title and Summary for the Aggregation
atom:title mandatory (atom)
atom:summary mandatory if no content (atom)
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
93. Authors for the Aggregation
mandatory (ORE). To prevent author-inheritance from Feed.
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
94. ORE Relationships for the Aggregation
recommended (ORE)
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
95. ORE Relationships for the Aggregation
optional: say what you can and say it right (ORE)
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
96. Types for the Aggregation
…/Aggregation mandatory (ORE)
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
97. Dates for the Aggregation
optional: say what you can and say it right (ORE)
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
98. Dates for the Resource Map
atom:updated mandatory (atom)
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
99. Rights pertaining to the Resource Map
recommended (ORE)
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
100. Authorship of the Resource Map
Of feed that
encompasses
the entry
atom:author mandatory (ORE)
other elements shown: recommended (atom)
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
101. And all the rest …
optional: say what you can and say it right (ORE)
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
102. Validating ORE Atom Entries
• ORE validator
o http://www.openarchives.org/ore/atom-validator
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
103. Extracting RDF triples from ORE Atom Entries
• ORE GRDDL
o http://www.openarchives.org/ore/atom-grddl
• Insert this in ORE entries:
<atom:entry …
xmlns:grddl=quot;http://www.w3.org/2003/g/data-view#quot;
grddl:transformation=quot;http://www.openarchives.org/ore/atom-grddlquot;
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
104. OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
105. OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
106. OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
107. OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
108. OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
109. OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
110. OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
111. OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
112. OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
113. OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
114. OAI Object Reuse and Exchange
HTTP Implementation
Aggregation URI
Resource Map URI
Splash Page URI
Proxy URI
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
115. HTTP implementation
information resource - protocol based URI
The Web is built of HTTP URIs
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
116. HTTP implementation
non-information resource - cite A-1, get ReM-1
Access to URI Aggregation yields a Resource Map: various approaches
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
117. Cool URIs
• Want simple, stable, manageable URIs
o stability important for citation
• Certainly no technology baggage (.php, .asp etc.)
• Aggregation URI not tied to format of ReM
A-1 = http://example.org/foo
ReM-1 = http://example.org/foo.atom
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
118. HTTP 303 & Content Negotiation
• Web server support for 303 redirection is
available.
• Web server support for content negotiation is
available.
• Support multiple Resource Maps is required.
• Desire to integrate Splash Pages into the solution.
• Desire to allow easy extensibility to additional
Resource Maps and/or Splash Pages
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
119. HTTP 303 & Content Negotiation
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
120. HTTP 303 & Content Negotiation
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
121. HTTP 303 & Content Negotiation
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
122. HTTP 303 without Content Negotiation
• There is just one Resource Map for each
Aggregation
• Web server support for content negotiation is not
available
• Web server support for HTTP 303 redirection is
available
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
123. HTTP 303 without Content Negotiation
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
124. HTTP 303 without Content Negotiation
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
125. Simple Implementation using Hash URIs
• There is just one Resource Map for each
Aggregation
• Web server support for 303 redirection is not
available
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
126. Simple Implementation using Hash URIs
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
127. Simple Implementation using Hash URIs
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
128. HTTP Proxy URIs
ore:proxyFor and ore:proxyFor to introduce a Proxy for an Aggregated Resource
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
129. Requirements for HTTP URIs for Proxies
1. Redirect to the Aggregated Resource with:
HTTP status code quot;303 See Otherquot; and Location: URI-AR
2. Indicate the Aggregation context with:
HTTP Link header Link: <URI-A>; rel=quot;aggregationquot;
3. No restriction on URI syntax, but...
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
130. ORE Proxy URI resolver
• Operated by OCLC (thanks!)
• Simple construction syntax:
http://oreproxy.org/r?what=URI-AR&where=URI-A
> parameter order important
> careful to URI encode (potentially doubly)
• Resolver is compliant with required behaviour
• Allows the use of Proxy URIs at no extra cost
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
131. OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
132. Resource Map Discovery: Outline
• Batch Discovery
o Atom Feeds, OAI-PMH, SiteMaps,
• Embedding Discovery Links
o With HTML “link” element
o With HTTP “Link” response header
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
133. Batch Discovery
• There are several techniques to expose batches of Resource Maps:
o Atom Feed in which Entries are Resource Maps serialized in Atom
o OAI-PMH in which records are Resource Maps (Atom and/or RDF/
XML)
o SiteMaps in which URLs point at Resource Maps (Atom and/or
RDF/XML)
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
134. Atom Feed
ReM
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
136. OAI-PMH
http://www.foo.edu/oai?verb=ListRecords&metadataPrefix=oai_rem_atom
<?xml version=quot;1.0quot; encoding=quot;UTF-8quot;?>
<OAI-PMH xmlns=quot;http://www.openarchives.org/OAI/2.0/quot;
xmlns:xsi=quot;http://www.w3.org/2001/XMLSchema-instancequot;
xsi:schemaLocation=quot;http://www.openarchives.org/OAI/2.0/
http://www.openarchives.org/OAI/2.0/OAI-PMH.xsdquot;>
<responseDate>2007-02-08T08:55:46Z</responseDate>
<request verb=”ListRecords” metadataPrefix=quot;oai_rem_atomquot;>
http://foo.edu/oai2</request>
<ListRecords>
<record>
<header> MUST NOT
<identifier>oai:foo.edu:object1</identifier> equal ReM /entry/id
<datestamp>2007-01-06</datestamp>
</header>
<metadata>
<!-- Insert ReM here --> MUST be equal to ReM
</metadata> modification time ( /entry/updated in Atom)
</record>
. . .
</ListRecords>
</OAI-PMH>
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
137. OAI-PMH GetRecord points at ReM … almost
http://www.foo.edu/oai?verb=GetRecord&identifier=oai:foo.edu:object1&
metadataPrefix=oai_rem_atom
<?xml version=quot;1.0quot; encoding=quot;UTF-8quot;?>
<OAI-PMH xmlns=quot;http://www.openarchives.org/OAI/2.0/quot;
xmlns:xsi=quot;http://www.w3.org/2001/XMLSchema-instancequot;
xsi:schemaLocation=quot;http://www.openarchives.org/OAI/2.0/
http://www.openarchives.org/OAI/2.0/OAI-PMH.xsdquot;>
<responseDate>2007-02-08T08:55:46Z</responseDate>
<request verb=quot;GetRecordquot; identifier=quot;oai:foo.edu:object1quot;
metadataPrefix=quot;oai_rem_atomquot;>http://foo.edu/oai2</request>
<GetRecord>
<record>
<header>
<identifier>oai:foo.edu:object1</identifier>
<datestamp>2007-01-06</datestamp>
</header> need a gateway to:
<metadata> 1. strip off OAI-PMH wrappers
<!-- Insert ReM here --> 2. return just what is inside <metadata>
</metadata> 3. reset the MIME type (e.g., from
</record> application/xml to application/atom+xml )
</GetRecord>
</OAI-PMH>
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
138. SiteMaps
http://www.foo.edu/sitemap-rem.xml
<?xml version=quot;1.0quot; encoding=quot;UTF-8quot;?>
<urlset xmlns=quot;http://www.sitemaps.org/schemas/sitemap/0.9quot;>
<url>
<loc>http://www.foo.edu/objects/object1.atom</loc>
<lastmod>2007-01-06</lastmod>
</url>
<url>
<loc>http://www.foo.edu/objects/object2.atom</loc>
<lastmod>2007-08-11</lastmod>
MUST equal URI-R
<changefreq>weekly</changefreq>
</url> ( /entry/link[@rel=quot;selfquot;]/@href
<url> in Atom)
<loc>http://www.foo.edu/objects/object3.atom</loc>
<lastmod>2007-03-15T18:30:02Z</lastmod>
<priority>0.3</priority>
</url>
... MUST be equal to ReM
</urlset> modification time ( /entry/updated in Atom)
remember SiteMap path limitation: http://www.foo.edu/a/b/sitemap-rem.xml can list
http://www.foo.edu/a/b/bar2.atom but not http://www.foo.edu/bar1.atom
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
139. Embedding Discovery Links
• Starting with a Web resource (say a splash page), how to find the
associated Aggregations(s)?
o HTML <link> element
o HTTP Response Headers
o Display it …
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
140. HTML <link>: one ReM
<html xmlns=quot;http://www.w3.org/1999/xhtmlquot; lang=quot;enquot;>
<head>
<title>[astro-ph/0601007] Parametrization of K-essence and Its Kinetic Term</
title>
<link rel=quot;shortcut iconquot; href=quot;/favicon.icoquot; type=quot;image/x-iconquot; />
<link rel=quot;stylesheetquot; type=quot;text/cssquot; media=quot;screenquot; href=quot;/css/arXiv.cssquot; />
<link rel=”resourcemapquot; type=”application/atom+xmlquot;
href=“http://arxiv.org/rem/atom/astro-ph/0601007quot; />
</head>
<body>
<div id=quot;headerquot;>
<h1><a href=quot;/quot;>arXiv.org</a> > <a href=quot;/list/astro-ph/recentquot;>astro-ph</a>
> arXiv:astro-ph/0601007</h1>
…
</body>
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
141. HTML <link>: two ReMs
<html xmlns=quot;http://www.w3.org/1999/xhtmlquot; lang=quot;enquot;>
<head>
<title>[astro-ph/0601007] Parametrization of K-essence and Its Kinetic Term</
title>
<link rel=quot;shortcut iconquot; href=quot;/favicon.icoquot; type=quot;image/x-iconquot; />
<link rel=quot;stylesheetquot; type=quot;text/cssquot; media=quot;screenquot; href=quot;/css/arXiv.cssquot; />
<link rel=”resourcemapquot; type=”application/atom+xmlquot;
href=“http://arxiv.org/rem/atom/astro-ph/0601007quot; />
<link rel=”resourcemapquot; type=”application/rdf+xmlquot;
href=“http://arxiv.org/rem/rdf/astro-ph/0601007quot; />
</head>
<body>
<div id=quot;headerquot;>
<h1><a href=quot;/quot;>arXiv.org</a> > <a href=quot;/list/astro-ph/recentquot;>astro-ph</a>
> arXiv:astro-ph/0601007</h1>
…
</body>
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
142. HTML <link>: a ReM and a Feed
<html xmlns=quot;http://www.w3.org/1999/xhtmlquot; lang=quot;enquot;>
<head>
<title>[astro-ph/0601007] Parametrization of K-essence and Its Kinetic Term</
title>
<link rel=quot;shortcut iconquot; href=quot;/favicon.icoquot; type=quot;image/x-iconquot; />
<link rel=quot;stylesheetquot; type=quot;text/cssquot; media=quot;screenquot; href=quot;/css/arXiv.cssquot; />
<link rel=”resourcemapquot; type=”application/atom+xmlquot;
href=“http://arxiv.org/rem/atom/astro-ph/0601007quot; />
<link rel=”alternatequot; type=”application/atom+xmlquot;
href=“http://arxiv.org/feed/astro-phquot; />
</head>
<body>
<div id=quot;headerquot;>
<h1><a href=quot;/quot;>arXiv.org</a> > <a href=quot;/list/astro-ph/recentquot;>astro-ph</a>
> arXiv:astro-ph/0601007</h1>
…
</body>
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
143. HTML <link>: an RDFa ReM
<html xmlns=quot;http://www.w3.org/1999/xhtmlquot; lang=quot;enquot;>
<head>
<title>[astro-ph/0601007] Parametrization of K-essence and Its Kinetic Term</
title>
<link rel=quot;shortcut iconquot; href=quot;/favicon.icoquot; type=quot;image/x-iconquot; />
<link rel=quot;stylesheetquot; type=quot;text/cssquot; media=quot;screenquot; href=quot;/css/arXiv.cssquot; />
<link rel=”resourcemap selfquot; type=”application/xhtml+xmlquot;
href=“http://arxiv.org/abs/astro-ph/0601007#remquot; />
</head>
<body>
<div id=quot;headerquot;>
<h1><a href=quot;/quot;>arXiv.org</a> > <a href=quot;/list/astro-ph/recentquot;>astro-ph</a>
> arXiv:astro-ph/0601007</h1>
…
</body>
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
144. HTTP Link Header
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
145. Display the URI
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
146. Display URI-A
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
147. OAI Object Reuse and Exchange
So what is going to happen with this all?
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
148. Several interesting experiments based on ORE
• Digital preservation of aggregations:
o http://www.ctwatch.org/quarterly/multimedia/11/ORE_prototype-demo/
• Social curation of aggregations:
o http://african.lanl.gov/preserve/
• Exchange of compound objects between heterogeneous repository
architectures:
o http://journal.code4lib.org/articles/1062
o http://blip.tv/file/866653
• Desktop-based creation of rich aggregations:
o http://www.itee.uq.edu.au/~eresearch/papers/2007/IDCC07.pdf
o http://maenad.itee.uq.edu.au/lore/
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
149. Early signs of adoption (1)
• ORE model is explored/recommended as the core model to deal with multi-
resource scholarly and cultural heritage assets in various high-visibility
projects:
o OREchem
o NSF DataNet
o EU funded DRIVER 2, Europeana, EDLnet
- http://driver2.dans.knaw.nl/demonstrator/html
• Major institutional repositories (Fedora, DSpace, ePrints) implementing
ORE. Oxford Universities’ Fedora:
o HTML splash page:
http://ora.ouls.ox.ac.uk/objects/uuid
%3A12790621-14d6-41f1-8df3-0f944cf333e6
o HTML splash page has <link rel=“resourcemap” …> to Resource Map:
http://ora.ouls.ox.ac.uk/objects/uuid:
12790621-14d6-41f1-8df3-0f944cf333e6/aggregation.xml
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
150. Early signs of adoption (2)
• JSTOR to bring Resource Map for its entire journal collection in production.
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
151. Early signs of adoption (3)
• Microsoft is developing technology that leverages ORE:
o ORE Word plug-in
o Research Output Repository Platform
- http://research.microsoft.com/en-us/projects/zentity/
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
152. Early signs of adoption (4)
• Myexperiment.org uses ORE for the description of Packs and Experiments
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
153. OAI Object Reuse and Exchange
A fun experiment by the LANL Digital Library
Research & Prototyping Team
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
154. Demo: Writing papers (citing) leveraging ORE
Structured bibliographic
references
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
155. Set Up
Resource
Map
Bibtex
EndNote
Typed as bibliographic
Indication of bibliographic format DC
Experiment conducted by LANL Digital Library Research & Prototyping Team
Movie (no vox) at http://public.lanl.gov/herbertv/images/cite_no_manager.mov
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
156. Web-based authoring environment
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
157. Empty References section
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
158. Start editing
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
159. Select area where citation is needed
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
160. Use search engine to find to-be-cited paper
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
161. Got it. Remember Splash Page points at Resource Map
Resource
Map
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
162. Copy URI of Splash Page
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
163. Hyperlink selected area with Splash Page URI
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
164. Repeat for other areas that require a citation
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
165. Save it
The Save process follows
URIs searching for Resource
Maps; structured bibliographic
descriptions
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
166. Links to Splash Pages, References section inserted
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic
167. References section completed
OAI Object Reuse & Exchange
Herbert Van de Sompel
Inforum 2009, May 26 2009, Prague, Czech Republic