Web: Minimal Metadata for Data Services Through DIALOGUE Neil Chue Hong AHM2007.

Slides:



Advertisements
Similar presentations
Web Services & EAI.
Advertisements

MgmtSecurity QOS Transport Packaging Extensions Wire Inspection Discovery Publication Registry Description Business Level Agreements Service Level Agreements.
Web Service Architecture
Siebel Web Services Siebel Web Services March, From
Web Services Copyright © Liferay, Inc. All Rights Reserved. No material may be reproduced electronically or in print without written permission.
Web Services Nasrullah. Motivation about web service There are number of programms over the internet that need to communicate with other programms over.
UDDI, Discovery and Web Services Registries. Introduction To facilitate e-commerce, companies needed a way to locate one another and exchange information.
SOA and Web Services. SOA Architecture Explaination Transport protocols - communicate between a service and a requester. Messaging layer - enables the.
1 Introduction to XML. XML eXtensible implies that users define tag content Markup implies it is a coded document Language implies it is a metalanguage.
1 Introduction to SOA. 2 The Service-Oriented Enterprise eXtensible Markup Language (XML) Web services XML-based technologies for messaging, service description,
Future Software Architectures Combining the Web 2.0 with the Semantic Web to realize future Web Communities Maarten Visser
Ontology Classifications Acknowledgement Abstract Content from simulation systems is useful in defining domain ontologies. We describe a digital library.
JXTA P2P Platform Denny Chen Dai CMPT 771, Spring 08.
NextGRID & OGSA Data Architectures: Example Scenarios Stephen Davey, NeSC, UK ISSGC06 Summer School, Ischia, Italy 12 th July 2006.
PAWN: A Novel Ingestion Workflow Technology for Digital Preservation
Tools and Services for the Long Term Preservation and Access of Digital Archives Joseph JaJa, Mike Smorul, and Sangchul Song Institute for Advanced Computer.
Interpret Application Specifications
Web Service Architecture Part I- Overview and Models (based on W3C Working Group Note Frank.
Web-based Portal for Discovery, Retrieval and Visualization of Earth Science Datasets in Grid Environment Zhenping (Jane) Liu.
Web Services Michael Smith Alex Feldman. What is a Web Service? A Web service is a message-oriented software system designed to support inter-operable.
Secure Systems Research Group - FAU Web Services Standards Presented by Keiko Hashizume.
Chinese-European Workshop on Digital Preservation, Beijing July 14 – Chinese-European Workshop on Digital Preservation Beijing (China), July.
QCDgrid Technology James Perry, George Beckett, Lorna Smith EPCC, The University Of Edinburgh.
XML at Work John Arnett, MSc Standards Modeller Information and Statistics Division NHSScotland Tel: (x2073)
GridCastUK-Japan N+N October Cambridge Newcastle Edinburgh Oxford Glasgow Manchester Cardiff Soton London Belfast DL RL Hinxton.
Web Services Architecture1 - Deepti Agarwal. Web Services Architecture2 The Definition.. A Web service is a software system identified by a URI, whose.
THE GITB TESTING FRAMEWORK Jacques Durand, Fujitsu America | December 1, 2011 GITB |
Using IESR Ann Apps MIMAS, The University of Manchester, UK.
A Metadata Catalog Service for Data Intensive Applications Presented by Chin-Yi Tsai.
UDDI ebXML(?) and such Essential Web Services Directory and Discovery.
Web Services Description Language (WSDL) Jason Glenn CDA 5937 Process Coordination in Service and Computational Grids September 30, 2002.
The Data Grid: Towards an Architecture for the Distributed Management and Analysis of Large Scientific Dataset Caitlin Minteer & Kelly Clynes.
Metadata and Geographical Information Systems Adrian Moss KINDS project, Manchester Metropolitan University, UK
QCDGrid Progress James Perry, Andrew Jackson, Stephen Booth, Lorna Smith EPCC, The University Of Edinburgh.
1 CS 430 Database Theory Winter 2005 Lecture 17: Objects, XML, and DBMSs.
Presented by Dr Joanne Evans, Centre for Organisational and Social informatics Faculty of IT, Monash University Designing for interoperability Experiences.
1 Schema Registries Steven Hughes, Lou Reich, Dan Crichton NASA 21 October 2015.
MobileMAN Internal meetingHelsinki, June 8 th 2004 NETikos activity in MobileMAN project Veronica Vanni NETikos S.p.A.
Web Services Standards. Introduction A web service is a type of component that is available on the web and can be incorporated in applications or used.
XML Web Services Architecture Siddharth Ruchandani CS 6362 – SW Architecture & Design Summer /11/05.
OGSA-DAI in OMII-Europe Neil Chue Hong EPCC, University of Edinburgh.
1 Metadata –Information about information – Different objects, different forms – e.g. Library catalogue record Property:Value: Author Ian Beardwell Publisher.
OASIS Symposium 4/04 Registry : Reliable Infrastructure Role of Registry : Reliable Infrastructure Carl Mattocks CEO CHECKMi Infrastructure Project Background.
WebService. Outline Overview of Web Services SOAP (messaging) WSDL (service description) UDDI (registry)
Web Services (SOAP) part 1 Eriq Muhammad Adams J |
A Brave NEtWork World Rob Willis, Ross & Associates Node Mentoring Workshop New Orleans, LA February 28, 2005.
Registries, ebXML and Web Services in short. Registry A mechanism for allowing users to announce, or discover, the availability and state of a resource:
1 Service Creation, Advertisement and Discovery Including caCORE SDK and ISO21090 William Stephens Operations Manager caGrid Knowledge Center February.
C# 1 Web services CSC 298. C# 2 Web services  A technology to make libraries available across the internet.  In Visual Studio,  can create a web service.
1 G52IWS: Web Services Chris Greenhalgh. 2 Contents The World Wide Web Web Services example scenario Motivations Basic Operational Model Supporting standards.
DSpace System Architecture 11 July 2002 DSpace System Architecture.
Providing web services to mobile users: The architecture design of an m-service portal Minder Chen - Dongsong Zhang - Lina Zhou Presented by: Juan M. Cubillos.
An approach to Web services Management in OGSA environment By Shobhana Kirtane.
Copyright 2007, Information Builders. Slide 1 iWay Web Services and WebFOCUS Consumption Michael Florkowski Information Builders.
Improvement of Semantic Interoperability based on Metadata Registry(MDR) Doo-Kwon Baik Dept. of CSE Korea University.
Software Architecture Patterns (3) Service Oriented & Web Oriented Architecture source: microsoft.
XML 1. Chapter 8 © 2013 Pearson Education, Inc. Publishing as Prentice Hall SAMPLE XML SCHEMA (XSD) 2 Schema is a record definition, analogous to the.
A Semi-Automated Digital Preservation System based on Semantic Web Services Jane Hunter Sharmin Choudhury DSTC PTY LTD, Brisbane, Australia Slides by Ananta.
Java Web Services Orca Knowledge Center – Web Service key concepts.
Outline Introduction and motivation, The architecture of Tycho,
Sabri Kızanlık Ural Emekçi
WEB SERVICES.
An Overview of Data-PASS Shared Catalog
Web Ontology Language for Service (OWL-S)
Web services, WSDL, SOAP and UDDI
Session 2: Metadata and Catalogues
LOD reference architecture
Introduction to Web Services
Metadata The metadata contains
Presentation transcript:

Web: Minimal Metadata for Data Services Through DIALOGUE Neil Chue Hong AHM2007

Web: It’s Good To Talk Data Integration Applications: Linking Organisations to Gain Understanding and Experience (DIALOGUE) EPSRC supported sister project network grant running from Stimulate discussion between people involved in data access and integration o

Web: Minimum Requirements for Information Exchange Requirements for agreements so that information can be effectively interchanged between DAI technologies. o Identification of data sources o Description of data sources o Identification of data o Description of data representations What’s the least information I need?

Web: Service Types Core Services / Baseline Services o essential to infrastructure o security, registry, index, discovery Data Services / Data Access Services o exposes a queryable data resource Analytical Services / Data Processing Services / Computational Services o provide operations that act on data Data Transfer Services o provide transfer of data between endpoints Data Storage Services o provide management of data, inc replication

Web: Interoperability Points between Components Compatible naming for services Compatible naming for data objects Managed data transfer between any two endpoints Data formats Data discovery

Web: Searching for data Standard way of accessing a metadata catalogue Standard format for describing a data resource o sufficient to access it access protocols supported description of security policies transfer protocols supported available replicas QoS policies o sufficient to understand what’s in it quality of data provenance o sufficient to choose the right source quality of service –productivity, availability, responsiveness, reliability, accessibility

Web: Core Set of Metadata for all our Data Services Service name Service ID? o Does this evolve too quickly? o Is this only useful for resolution? o Should this be described elsewhere? Service version Service owner Service maintainer Service description: human readable summary Service types implemented Minimal set of annotation on operations to allow discovery Minimal set of management information? Link to service policies (including security, QoS)? Should we use WSDL and WS-MetadataExchange

Web: Extra Metadata for Data Access Services Access protocols supported o query languages supported o result representations supported Description of security policies Transfer protocols supported Available replicas QoS policies Is this DAIS? Extensions for each type: SQL Data Access Services, DICOM, XPath, CQL, etc.

Web: Extra Metadata for Data Transfer OGSA-DMI QoS – what terms o e.g. replica selection for transfers?

Web: Extra Metadata for Data Storage Amazon’s S3 (Simple Storage Service) Data Transport RG o storage operations and parameters SRM

Web: Extra Metadata for Data Transformation Services Schema mapping o store schema maps (e.g. A->B) rather than schema o but no current agreed way of representing a schema map o allow schema maps to be discovered o allow optimisation over maps e.g. A->B->C => A->C if present o Quality and trust of third party schema maps

Web: Core set of Metadata for representing a data object / record Identifier Structure / representational format Provenance data Human readable description Extended sets for o relational data o XML data o file collections Feature based processing, content based processing

Web: Core set of information to store in a provenance record for data integration Who created When created Which service created Service configuration parameters (inc inputs) But how do you evolve this information?

Web: What needs to be agreed What does need to be agreed to make different services interoperate? DIALOGUE allowed discussion amongst software engineers involved in data integration o paper to be published But look at Dublin Core… o … and the many formats for addresses