DOCSLIB.ORG

TAS3 Deliverable D1.1: State of the Art Accompanying Letter to The

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

TAS 3 Deliverable D1.1: State of the Art Accompanying Letter to the Reviewers At the TAS 3 review on February 26 th , 2009, the project reviewers indicated that deliverable D1.1 State of the Art was provisionally accepted. The TAS 3 Consortium has addressed the reviewers’ comments as follows. In addition to the recommended updates, more content has been provided. A new specific chapter (5) has been created concerning Threat Analysis, additional information on Trust KPI as well as large update in Identity Management. a) Ch. 4: Include at least the Common some SAP product only, so this comment Criteria (ISO/IEC 15408) as a real as been removed because it’s not relevant methodology for security requirements. in this context. CA services and scoring (Microsoft SDLM is another one.) model have been added. Several threat methodologies have been included within a new dedicated chapter f) Ch. 10: Add definitions of key terms used (Chap 5). here. Justify why the focus is laid on IFG. Add Kim Camerons laws of identity. b) Ch.6 Include CardSpace, Information Whereas KC's 7 laws are fully expounded Card Forum. in Ch 11, WP7, additional information Information exists in Identity have been added in Legal chapter (chap Management (chap 11). 10). Updated accordingly. g) Ch. 11: (minor remarks: Change c) Ch. 7: Are there any industry specific 1,024bits to 2,048bits. Consider spending blueprints of enterprise architecture one sentence about modern cryptography models relevant for TAS3? like certificateless PKI, identitybased Updated accordingly. cryptography and groupbased cryptography. Mention the possibility of a d) Ch. 8: Reconsider the claims made smart card being an IdP.) about BestCrypt. Add reference for Updated accordingly. Trustbuilder and Protune. Add European Citizen Card (ECC). h) Ch.12: Check the end of the chapter Updated accordingly. (ends abrupt). Updated accordingly. e) Ch. 9: Explain the link of SAP SSO capabilities to trust policies. Add web of i) Ch.13: Add the EU government project trust models (like PGP), certification STORK and IDABC. authority services, scoring models (as used Added accordingly. by eBay) and their (ir) relevance to TAS3 For SAP SSO/Trust: in fact the real j) Ch.14: Complete 13.3.4 Standards and relation is that a user is going to logon add some elaboration. Justify the using SSO to use the reputation system for exclusion of health insurances. a ranking of providers. This is true for Updated accordingly. The WP01 Team SEVENTH FRAMEWORK PROGRAMME Challenge 1 Information and Communication Technologies Trusted Architecture for Securely Shared Services D1.1 State Of The Art 2/140 Table of Contents Table of Contents _____________________________________________________ 2 1 Contributors _____________________________________________________ 6 2 TAS3 Overall Presentation __________________________________________ 6 2.1 Issue _____________________________________________________________ 6 2.2 Solution __________________________________________________________ 7 2.3 Application Domains _______________________________________________ 7 2.4 Project Organization________________________________________________ 8 2.5 The TAS3 Consortium ______________________________________________ 8 2.6 Architecture _______________________________________________________ 8 2.7 Application in the Domains __________________________________________ 9 2.8 Validation_________________________________________________________ 9 3 State of the Art structure __________________________________________ 10 4 Methods for Requirements _________________________________________ 11 4.1 Introduction ______________________________________________________ 11 4.2 Problem statement ________________________________________________ 11 4.3 Overview of existing solutions _______________________________________ 11 4.3.1 Standards and extensions _________________________________________________ 11 4.3.2 Research solutions ______________________________________________________ 12 4.3.3 Commercial solutions ____________________________________________________ 15 4.4 In-situ perspective _________________________________________________ 15 4.5 Trends & Future development_______________________________________ 16 4.6 Project based Gap Analysis with potential enhancement _________________ 16 4.7 Stakeholders _____________________________________________________ 16 5 Methods for Threat Analysis _______________________________________ 17 5.1 Introduction ______________________________________________________ 17 1.1 Problem statement ________________________________________________ 17 5.2 Overview of existing solutions _______________________________________ 17 1.1 In-situ perspective _________________________________________________ 20 6 Framework, Architecture and Semantics ______________________________ 21 6.1 Introduction ______________________________________________________ 21 6.2 Problem statement ________________________________________________ 21 6.3 Overview of existing solutions _______________________________________ 21 6.3.1 Standards and extensions _________________________________________________ 21 6.3.2 Research solutions ______________________________________________________ 23 6.4 Trends & Future development_______________________________________ 25 6.5 Project based Gap Analysis with potential enhancement _________________ 25 FP7-ICT_2007-1 May 27, 2009 - TAS³ IP 3/140 6.6 Stakeholders _____________________________________________________ 27 7 Adaptable Secure Business Processes ________________________________ 28 7.1 Introduction ______________________________________________________ 28 7.2 Problem statement ________________________________________________ 28 7.3 Overview of existing solutions _______________________________________ 28 7.3.1 Standards and extensions _________________________________________________ 28 7.3.2 Research solutions ______________________________________________________ 30 7.3.3 Commercial solutions ____________________________________________________ 31 7.4 In-situ perspective _________________________________________________ 31 7.5 Policies __________________________________________________________ 32 7.6 Trends & Future development_______________________________________ 32 7.7 Project based Gap Analysis with potential enhancement _________________ 32 7.8 Stakeholders _____________________________________________________ 32 8 Information Protection ____________________________________________ 34 8.1 Introduction ______________________________________________________ 34 8.2 Problem statement ________________________________________________ 34 8.3 Overview of existing solutions _______________________________________ 34 8.3.1 Standards and extensions _________________________________________________ 35 8.4 Trends & Future development_______________________________________ 39 8.5 Project based Gap Analysis with potential enhancement _________________ 39 8.6 Stakeholders _____________________________________________________ 39 9 Trust Policy Management __________________________________________ 40 9.1 Introduction ______________________________________________________ 40 9.2 Problem statement ________________________________________________ 40 9.3 Overview of existing solutions _______________________________________ 41 9.3.1 Research solutions ______________________________________________________ 41 9.3.2 Commercial solutions ____________________________________________________ 42 9.4 Trends & Future development_______________________________________ 42 9.5 Project based Gap Analysis with potential enhancement _________________ 43 10 Legal, Privacy and Ethics _________________________________________ 44 10.1 Introduction ______________________________________________________ 44 10.2 Problem statement ________________________________________________ 44 10.3 Overview of existing solutions _______________________________________ 44 10.3.1 Standards and extensions _________________________________________________ 44 10.3.2 Research solutions ______________________________________________________ 51 10.3.3 Commercial solutions ____________________________________________________ 51 10.4 In-situ perspective _________________________________________________ 51 10.5 Policies __________________________________________________________ 52 10.6 Trends & Future development_______________________________________ 52 10.7 Project based Gap Analysis with potential enhancement _________________ 52 FP7-ICT_2007-1 May 27, 2009 - TAS³ IP 4/140 10.8 Stakeholders _____________________________________________________ 53 11 Identity Management ___________________________________________ 54 11.1 Introduction ______________________________________________________ 54 11.2 Problem statement ________________________________________________ 54 11.3 Overview of existing solutions _______________________________________ 54 11.3.1 Identity Management Principals and Definitions ______________________________ 54 11.3.2 User Centric Identity Management _________________________________________ 63 11.3.3 Existing Technologies and protocols for Federated Access to Resources ___________ 66 11.3.4 Attribute Aggregation ____________________________________________________ 72 11.3.5 Research solutions ______________________________________________________ 85 11.3.6 Commercial solutions ____________________________________________________ 85 11.4 Policies __________________________________________________________ 86 11.5 Trends & Future development_______________________________________
Recommended publications
  • TIBCO Businessconnect™ Ebxml Protocol User’S Guide — Ebms3/AS4 Standard

    TIBCO Businessconnect™ Ebxml Protocol User’S Guide — Ebms3/AS4 Standard

    TIBCO BusinessConnect™ ebXML Protocol User’s Guide — ebMS3/AS4 Standard Software Release 6.1 August 2015 Two-Second Advantage® Important Information SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE. USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME. This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc. TIBCO, Two-Second Advantage, TIBCO ActiveMatrix BusinessWorks, TIBCO ActiveMatrix BusinessWorks Plug-in for BusinessConnect, TIBCO Administrator, TIBCO BusinessConnect, TIBCO BusinessConnect Palette, TIBCO Designer, TIBCO Enterprise Message Service, TIBCO Hawk, TIBCO Rendezvous, TIBCO Runtime Agent are either registered trademarks or trademarks of TIBCO Software Inc.
  • A SOAP-Based Model for Secure Messaging in a Global Context

    A SOAP-Based Model for Secure Messaging in a Global Context

    A SOAP-Based Model for Secure Messaging in a Global Context by Johannes Jurie van Eeden A SOAP-based Model for Secure Messaging in a Global Context by Johannes Jurie van Eeden Dissertation submitted in fulfillment of the requirements for the degree Magister Technologiae in Information Technology in the School of Information and Communication Technology at the Nelson Mandela Metropolitan University Promoter: Dr Maree Pather December 2005 Table of Contents Declaration ............................................................................................................. v Abstract.................................................................................................................. vi Acknowledgements................................................................................................ vii Acronyms and Abbreviations used.......................................................................viii Part I ...................................................................................................................... 1 Introduction............................................................................................................. 1 Chapter 1 ............................................................................................................... 2 Introduction............................................................................................................. 2 1.1 Problem Statement........................................................................................ 3 1.2 Objectives ....................................................................................................
  • Content Assembly Mechanism (CAM) Business Transaction Information Management

    Content Assembly Mechanism (CAM) Business Transaction Information Management

    Content Assembly Mechanism (CAM) business transaction information management What CAM Is The CAM approach provides these three The CAM specification provides an open critical abilities: – XML based system for using business rules to • documentation of business interchange define, validate and compose specific business transactions, documents from generalized schema elements • design-time assembly support with and structures. verification, and A CAM rule set and document assembly • runtime checking of information content. template defines the specific business context, content requirement, and transactional function Next we consider the limitations of current of a document. A CAM template must be approaches and technologies and how the capable of consistently reproducing documents capabilities that CAM provides can address that can successfully carry out the specific these shortcomings. transactional function that they were designed for. CAM also provides the foundation for The Present Tools and Their Limitations for creating industry libraries and dictionaries Addressing the Problem of schema elements and business document structures to support business process needs. The advent of XML has also meant that other new tools are available to advance the technology of automatic transaction content Solving the Inherent Problem of Automated handling. These include formal structure Information Integration definitions using XML schema (XSD) with Automated information integration has content control at the element level using been the Holy Grail of e-Business systems datatyping; then XSLT rules and XPath since before XML was conceived. Early expressions and semantic tools such as RDF attempts centered on the use of industry and OWL to provide machine understanding of standard transaction formats typified by EDI the role and usage of the XML based messages1.
  • Innovations in Resource Management and Mutual Aid Technology

    Innovations in Resource Management and Mutual Aid Technology

    Innovations in Resource Management and Mutual Aid Technology July 22, 2021 National Alliance for Public Safety GIS (NAPSG) Foundation napsgfoundation.org | @napsgfoundation napsgfoundation.org | @napsgfoundation 1 Webinar Prep​ • Due to the large attendance, all participants are muted for the duration of the session to prevent background noise.​ • Please use the Q&A functionality within Zoom for questions that are relevant to the whole group.​ • We will address these Q&A at the end of the webinar!​ napsgfoundation.org | @napsgfoundation Today’s Objectives • Learn about FEMA’s National Resource Hub and how to gain access and start using the suite of resource management tools. • Gain insight into how the National Resource Hub can connect and share data with your other incident management systems, situational awareness apps, and other 3rd party systems today and in the future. • Learn what is in development to improve existing and innovate with new resource management and mutual aid technology tools and systems. • Find out what’s new in version 3.0 of the Implementation Guide on Information Sharing Standards and how you can use the guide in informing your agency’s technology selection and acquisition process to ensure interoperability and seamless information sharing. • Gain basic technical knowledge on the latest with the Emergency Data Exchange Language (EDXL) and how it supports building a National – and Global – network of interoperable incident management systems. napsgfoundation.org | @napsgfoundation 3 Agenda 2:00pm Introductions and Overview 2:10pm National Resource Hub - What It’s About - What It Can Do For You and Your Agency 2:25pm What’s Coming in the Job Aid and Technical Guidance for Incident Management Technology 2:35pm Know the Basics on EDXL and Why it Matters 2:55pm Actions & Next Steps 3:00pm Adjourned napsgfoundation.org | @napsgfoundation 4 Hosts and Panelists • Charlotte Abel, Strategic Manager, NAPSG Foundation • Harmon Rowland, Section Chief, FEMA National Integration Center • Rebecca Harned, Vice President, 4 Arrows Consulting, Inc.
  • T-Mobile International Ebxml B2B Gateway Solution

    T-Mobile International Ebxml B2B Gateway Solution

    An OASIS White Paper T-Mobile International ebXML B2B Gateway Solution Adoption of the ebXML Messaging Service and ebXML Collaboration Protocol Profiles and Agreements OASIS Standards By Pim van der Eijk For OASIS OASIS (Organization for the Advancement of Structured Information Standards) is a not-for-profit, international consortium that drives the development, convergence, and adoption of e-business standards. Members themselves set the OASIS technical agenda, using a lightweight, open process expressly designed to promote industry consensus and unite disparate efforts. The consortium produces open standards for Web services, security, e-business, and standardization efforts in the public sector and for specific industries. OASIS was founded in 1993. More information can be found on the OASIS web site at http://www.oasis-open.org/. OASIS also hosts the ebXML XML.org web site, http://ebxml.xml.org/, which serves as the official international community gathering place and information resource for the suite of ebXML standards. The ebXML Messaging Service (ebMS) OASIS Standard enables the transport, routing and packaging of e-business transactions. The ebXML Collaboration Protocol Profiles and Agreements (CPPA) OASIS Standard describes how trading partners engage in electronic business collaborations through the exchange of electronic messages. Both technical specifications are part of the ebXML modular suite of specifications. The OASIS Technical Committees working on ebMS and CPPA were originally formed in 2001. The ebXML Messaging Service specification, version 2.0 and the ebXML Collaboration Protocol Profiles and Agreements specification, version 2.0, became OASIS Standards in 2002. Along with two other specifications of the ebXML framework, both documents were approved by the International Standards Organisation as ISO/TS 15000-2 and ISO/TS 15000-1 in March 2004.
  • Emergency Management Standards

    Emergency Management Standards

    Emergency Management Standards HL7 WGM International Council May 2019 Elysa Jones, Chair OASIS Emergency Management Technical Committee Emergency Interoperability Member Section [email protected] Agenda ▪ What is OASIS ▪ Joint work with HL7 - Tracking emergency patients - Hospital availability 2 Internationally recognized ▪ EU classifies OASIS as “one of the top three ICT consortia”. ▪ EU Regulation 1025/2012 allows OASIS specs to be referenced in public procurement ▪ OASIS is permanent member of EC’s European Multi-Stakeholder Platform on ICT Standardization ▪ OASIS TC Process is ANSI-accredited. 3 Established presence, Current agenda ▪ Nonprofit consortium ▪ Founded 1993 ▪ Global 5,000+ participants 600+ orgs & individuals in 100+ countries ▪ Home of 70+ Technical Committees ▪ Broad portfolio of standards: security, privacy, Cloud, M2M, IoT, content technologies, energy, eGov, legal, emergency management, finance, Big Data, healthcare, + other areas identified by members 4 OASIS → de jure OASIS Standard Also Approved As: Advanced Message Queuing Protocol (AMQP) ISO/IEC 19464 ebXML Collaborative Partner Profile Agreement ISO 15000-1 ebXML Messaging Service Specification ISO 15000-2 ebXML Registry Information Model ISO 15000-3 ebXML Registry Services Specification ISO 15000-4 Security Assertion Markup Language (SAML) ITU-T Rec. X.1141 Extensible Access Control Markup Language (XACML) ITU-T Rec. X.1142 OpenDocument Format (ODF) ISO/IEC 26300 Common Alerting Protocol (CAP) ITU-T Rec. X.1303 Computer Graphics Metafile (WebCGM) W3C WebCGM
  • Global Namespace Discovery Using a XRI Root-Of-Roots Assumed by ITU-T

    Global Namespace Discovery Using a XRI Root-Of-Roots Assumed by ITU-T

    Geneva, 21 September 2007 Global Namespace Discovery using a XRI root-of-roots assumed by ITU-T Tony Rutkowski Chair, ITU-T IdM FG Requirements WG [email protected] XRI detail slides courtesy of Reed Drummond OASIS Extensible Resource Identifier (XRI) TC International http://xri.net/=drummond.reed Telecommunication Union Identity Discovery Requirements 5.3 Discovery of authoritative Identify Provider resources, services, and federations. A critical IdM challenge in the very dynamic and diverse world of network services and applications is discovering current authoritative sources for the four core IdM categories described above or the federations that are associated with enabling discovery and access of the relevant IdM resources. It is not enough for the IdM capabilities to exist, if a relying party has no means for knowing who and how to reach and interoperate with the authoritative resources for asserted identities treated in the sub-section below. Identity Discovery Provider(s) Query(ies) to discover Identity Resources Response(s) Fig. 9. Identity Management Discovery Services A very significant number of contributions and use-cases during the entire activity period of the Focus Group dealt with Discovery capabilities and associated requirements. Discovery capabilities seem to be widely recognized as one of the most significant needs and gaps – including a consensus that the challenge of providing effective Discovery capabilities are therefore an essential part of trusted Identity Management. Some federations and communities surrounding Open Identity protocols have developed partial solutions to meet discovery needs within the boundaries of their user communities. However, there are no current means for global or inter-federation discovery.
  • Ebxml Web Services &

    Ebxml Web Services &

    ebXML Web Services & EDI XML Europe 2003 London 7 May 2003 Dale Waldt President, aXtive Minds, Inc. Program Development, OASIS Who Am I? Currently Director, aXtive Minds XML Training & Consulting [email protected] Program Development Consultant, OASIS XML Standards Consortium [email protected] Previously VP Technology, RIA Tax Publishing Group The Thomson Corporation XML Enables Robust e-Business Platforms Enables industry data interchange standards platform-independent data exchange electronic commerce user agents for automatic processing after receipt Enables software to handle specialized information distributed over the Web Enables use of metadata data about information help people & systems find information help information producers & consumers find each other The Complete XML Picture V V V V V V E E E E E E R R R R R R T T T T T T I I I I I I C C C C C C A A A A A A L L L L L L HORIZONTAL & WEB SERVICES PROCESS/CORE COMPONENTS MESSAGING (e.g. SOAP, ebXML TRP) FOUNDATION (e.g. XML, Schema, XSLT) CORE (e.g. TCP/IP, HTTP) The eBusiness Tidal Wave Business-to-Business Processes Sales and Distribution Consumer Services Internet Based Delivery The eBusiness Technologies Sales and Distribution B2B iMarketPlaces / Hubs XMLXML B2B iMarketPlaces / Hubs ASP’s (App’ Srvc Provider) B2C Integration Information Mining Web Services Directory Services First There Was EDI Electronic data Interchange (EDI) Fortune 1000 Facilitates global electronic trade ANSI X12 standards used in North America UN EDIFACT (EDI for Administration, Commerce & Transport) used in Europe and 95% elsewhere outside North America Purchase orders, invoices, wire transfers, Small to Medium receipts, etc.
  • 16Th ICCRTS “Collective C2 in Multinational Civil-Military Operations”

    16Th ICCRTS “Collective C2 in Multinational Civil-Military Operations”

    16th ICCRTS “Collective C2 in Multinational Civil-Military Operations” Title of Paper Adapting WS-Discovery for use in tactical networks Topic(s) Primary: Topic 9: Networks and Networking Alternatives: Topic 8: Architectures, Technologies, and Tools, Topic 6: Experimentation, Metrics, and Analysis Name of Author(s) Frank T. Johnsen and Trude Hafsøe Norwegian Defence Research Establishment (FFI) P.O. Box 25 2027 Kjeller, Norway Point of Contact Frank T. Johnsen Norwegian Defence Research Establishment (FFI) P.O. Box 25 2027 Kjeller, Norway [email protected] Abstract The NATO Network Enabled Capabilities (NNEC) feasibility study has identified Web services as a key enabling technology for NNEC. The technology is founded on a number of civil standards, ensuring interoperability across different operating systems and programming languages. This also makes the technology a natural choice for interoperability also in multinational civil-military operations, where a large number of heterogeneous systems need to exchange information. Web services provide loose coupling and late binding, which are desirable properties in such a setting. Discovering available services in an operation is essential, and the discovery process must leverage standards to ensure interoperable information exchange. WS-Discovery is a standard for Web services discovery suited for dynamic environments and civil networks, but has high overhead and is not so suitable for tactical networks. Like the other Web services standards, it uses XML for encoding messages. In civil networks bandwidth is abundant, but in tactical networks XML may incur unacceptable overhead. However, the W3C has created a specification for efficient XML interchange (EXI), which reduces XML overhead by defining a binary interchange format.
  • Service Discovery in Hybrid Environments

    Service Discovery in Hybrid Environments

    Service Discovery in Hybrid Environments Sabrina Alam Chowdhury Department of Informatics Faculty of mathematics and natural sciences UNIVERSITETET OF OSLO 01/08/2017 1 2 Service Discovery in Hybrid Environments 3 © 2017 Sabrina Alam Chowdhury Service Discovery in Hybrid Environments http://www.duo.uio.no/ Printed: Reprosentralen, University of Oslo 4 Abstract The thesis topic is based on Service discovery of heterogeneous Web services across hybrid environments. Here it also describes a clear definition of SOA and Web service with different standards to implement those services in different environments. Furthermore an analysis and survey of Web services standards also given in this thesis. An overview also discussed here that how different Web service discovery mechanism solution is currently available to discover services in different environments which include from cloud to non-cloud , non- cloud to cloud and other platforms with some research challenges on service discovery for SOAP and RESTful Web services. A prototype has been implemented as a proof of concept for enabling common service discovery for hybrid environments for different Web services. 5 6 Preface The thesis represents the final product of my master degree in Informatics at the University of Oslo. The work described herein is conducted under the supervision of Dr. Frank Trethan Johnsen and Cand. Scient. Trude Hafsøe Bloebaum. The thesis has been a long journey, and I would not have been able to complete it without the precious help and support given by various people. The learning curve of my career becomes so high, and I got to understand lots of interesting things while working on this thesis.
  • Gs Ins 006 V1.1.1 (2011-11)

    Gs Ins 006 V1.1.1 (2011-11)

    ETSI GS INS 006 V1.1.1 (2011-11) Group Specification Identity and access management for Networks and Services; Study to Identify the need for a Global, Distributed Discovery Mechanism Disclaimer This document has been produced and approved by the Identity and access management for Networks and Services (INS) ETSI Industry Specification Group (ISG) and represents the views of those members who participated in this ISG. It does not necessarily represent the views of the entire ETSI membership. 2 ETSI GS INS 006 V1.1.1 (2011-11) Reference DGS/INS-006 Keywords access, control, ID, management, network, service ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http://portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission.
  • Extensible Resource Identifier (XRI) Resolution Version 2.0 Committee Draft 02 25 November 2007

    Extensible Resource Identifier (XRI) Resolution Version 2.0 Committee Draft 02 25 November 2007

    Extensible Resource Identifier (XRI) Resolution Version 2.0 Committee Draft 02 25 November 2007 Specification URIs: This Version: http://docs.oasis-open.org/xri/2.0/specs/cd02/xri-resolution-V2.0-cd-02.html http://docs.oasis-open.org/xri/2.0/specs/cd02/xri-resolution-V2.0-cd-02.pdf http://docs.oasis-open.org/xri/2.0/specs/cd02/xri-resolution-V2.0-cd-02.doc Previous Version: N/A Latest Version: http://docs.oasis-open.org/xri/2.0/specs/xri-resolution-V2.0.html http://docs.oasis-open.org/xri/2.0/specs/xri-resolution-V2.0.pdf http://docs.oasis-open.org/xri/2.0/specs/xri-resolution-V2.0.doc Technical Committee: OASIS eXtensible Resource Identifier (XRI) TC Chairs: Gabe Wachob, AmSoft <[email protected]> Drummond Reed, Cordance <[email protected]> Editors: Gabe Wachob, AmSoft <[email protected]> Drummond Reed, Cordance <[email protected]> Les Chasen, NeuStar <[email protected]> William Tan, NeuStar <[email protected]> Steve Churchill, XDI.org <[email protected]> Related Work: This specification replaces or supercedes: • Extensible Resource Identifier (XRI) Resolution Version 2.0, Committee Draft 01, March 2005 • Extensible Resource Identifier (XRI) Version 1.0, Committee Draft 01, January 2004 This specification is related to: • Extensible Resource Identifier (XRI) Syntax Version 2.0, Committee Specification, December 2005 • Extensible Resource Identifier (XRI) Metadata Version 2.0, Committee Draft 01, March 2005 Declared XML Namespace(s) xri://$res xri://$xrds xri://$xrd XRI Resolution 2.0 Committee Draft 02 25 November 2007 Copyright © OASIS® 1993–2007.