1 / 14

ERIS Workshop, CRIS2002 Architecture

ERIS Workshop, CRIS2002 Architecture. Brian Matthews, Business & Information Technology Dept, CLRC b.m.matthews@rl.ac.uk. Introduction. Early stage proposal Objectives Establish key principles behind an architecture Establish key technologies behind an architecture Strawman architecture

quinlan-carver
Download Presentation

ERIS Workshop, CRIS2002 Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ERIS Workshop, CRIS2002Architecture Brian Matthews, Business & Information Technology Dept, CLRC b.m.matthews@rl.ac.uk Brian Matthews, CRIS 2002, 30/08/02

  2. Introduction • Early stage proposal • Objectives • Establish key principles behind an architecture • Establish key technologies behind an architecture • Strawman architecture • Summary and open questions. Brian Matthews, CRIS 2002, 30/08/02

  3. Objective • To design and build an architecture to support an Integrated European RTD Information System (ERIS). • The ERIS needs to support: • Researchers, • exploiters and • decision makers • And needs to be: • Robust • Easy to use • Extensible • “future proof” Brian Matthews, CRIS 2002, 30/08/02

  4. Key Principles • Certain general principles should underpin the architecture. • Institutional Independence • Common exchange formats • Distributed control • Multilinguality • Easy to use tools Brian Matthews, CRIS 2002, 30/08/02

  5. Institution Independence • Institutions should be able to maintain their own research information • Institutions keep ownership and can use the information for their own needs. • Institutions should be able to use their own internal formats and internal information systems (DB and OS independence). • Without these, institutional buy-in will be hard. Brian Matthews, CRIS 2002, 30/08/02

  6. Common Exchange Formats • A common exchange format (ontology) for expressing data (CERIF?) • Common APIs onto the local CRIS’s for query and return of information. • Local formats related to the common format by well-defined mappings. Brian Matthews, CRIS 2002, 30/08/02

  7. Distributed Control • Loose coupling between institutions • No overall administration • Collection of information at node points for efficiency • Periodic update and mirroring • Single point of authentication Brian Matthews, CRIS 2002, 30/08/02

  8. Multilinguality • Vital in a European (and wider) context. • Multilingual thesauri • Multilingual interfaces • Multilingual querying and response. Brian Matthews, CRIS 2002, 30/08/02

  9. Easy to use tools • Don’t demand unfamiliar tools and interfaces upon users • Based around a standard web architecture • Use Browsers as the Front-end. Brian Matthews, CRIS 2002, 30/08/02

  10. Key Technologies • Preference for Web technologies • “open” development • Widely available and supported • Open source implementations • Should also take note of GRID Brian Matthews, CRIS 2002, 30/08/02

  11. Basic Web technologies: http, HTML, CSS Fundamental exchange mechanism: XML, XSLT, XML Schema Component interfaces: Web Services (SOAP, WDSL, UDDI?, XACML?, SAML?) User Preferences P3P, CC/PP Knowledge representation and modelling: RDF, RDF Schema, DAML+OIL (WebOnt) Generic Querying system: XML Query? (XSQL?, RQL?) Programming layer: Java and Java Servlets Key Technologies Brian Matthews, CRIS 2002, 30/08/02

  12. ERIS broker CRIS Service Strawman Architecture Users Directory service ERIS portal Access control service Local data cache Common metadata User service XML Query over http WS wrapper Web Service wrapper WS wrapper WS wrapper WS wrapper Specific metadata Specific metadata Specific metadata Specific metadata Specific metadata Raw data Raw data Raw data Raw data Raw data Brian Matthews, CRIS 2002, 30/08/02

  13. Components • ERIS broker • Directory Service • Metadata Service • Query Service • Results Service • User Service • Access control service • Distributed query across HTTP • Web Service front-end to local CRIS • Xml wrapper to produce the right data. Brian Matthews, CRIS 2002, 30/08/02

  14. From here? • Service architecture proposed • Amalgamate results from different CRIS systems • Common exchange format – and Ontology • Common Thesaurus? • Local Caching of results? • A P2P hierarchy? Brian Matthews, CRIS 2002, 30/08/02

More Related