ࡱ> M tcbjbj== )WW@_3lZZZZZZZn8l&<nY.2nN=lX-Z-Z-Z-Z-Z-Z-$/ 1l~-Z9=~-cZZg-2cccZZX-cX-cc)%+ZZ,b Xn ,,,-Y.@,\2c2,cnnZZZZ The XDI FAQ January 20, 2004 This FAQ was created by the organizers of the OASIS XDI TC to provide background on its formation ( HYPERLINK "http://www.oasis-open.org/committees/xdi/" http://www.oasis-open.org/committees/xdi/). Other introductory material on XDI includes: The Dataweb: An Introduction to XDIa white paper that presents several well-known distributed data sharing challenges, explains how Dataweb architecture can be applied to these problems, and discusses how XDI builds on the principles of the Web, Web Services, and the Semantic Web.  HYPERLINK "http://www.oasis-open.org/apps/org/workgroup/xdi/download.php/5115/wd-xdi-intro-white-paper-2004-01-20.pdf" http://www.oasis-open.org/apps/org/workgroup/xdi/download.php/5115/wd-xdi-intro-white-paper-2004-01-20.pdf. The Cover Pages topic on Data Sharing, Mediation, and SynchronizationRobin Covers overview of the context in which XDI is being developed.  HYPERLINK "http://xml.coverpages.org/dataSharing.html" http://xml.coverpages.org/dataSharing.html. Question Index  TOC \o "1-1" \h \z  HYPERLINK \l "_Toc62403308" 1. What is XDI?  PAGEREF _Toc62403308 \h 2  HYPERLINK \l "_Toc62403309" 2. Is XDI a Web service?  PAGEREF _Toc62403309 \h 2  HYPERLINK \l "_Toc62403310" 3. What are the primary problems XDI is intended to solve?  PAGEREF _Toc62403310 \h 2  HYPERLINK \l "_Toc62403311" 4. What is the Dataweb?  PAGEREF _Toc62403311 \h 2  HYPERLINK \l "_Toc62403312" 5. Why is existing URI syntax not sufficient for cross-domain data sharing?  PAGEREF _Toc62403312 \h 3  HYPERLINK \l "_Toc62403313" 6. What features do XRIs have that URIs dont?  PAGEREF _Toc62403313 \h 3  HYPERLINK \l "_Toc62403314" 7. How do XDI documents differ from HTML documents?  PAGEREF _Toc62403314 \h 4  HYPERLINK \l "_Toc62403315" 8. How do XDI documents differ from conventional XML documents?  PAGEREF _Toc62403315 \h 4  HYPERLINK \l "_Toc62403316" 9. Does XDI require that I re-code all my XML documents?  PAGEREF _Toc62403316 \h 5  HYPERLINK \l "_Toc62403317" 10. How does XDI differ from HTTP?  PAGEREF _Toc62403317 \h 5  HYPERLINK \l "_Toc62403318" 11. How does XDI differ from SOAP?  PAGEREF _Toc62403318 \h 5  HYPERLINK \l "_Toc62403319" 12. Is XDI only for enveloping other data?  PAGEREF _Toc62403319 \h 5  HYPERLINK \l "_Toc62403320" 13. What are XDI link contracts?  PAGEREF _Toc62403320 \h 5  HYPERLINK \l "_Toc62403321" 14. How will link contracts reflect the large spectrum of data sharing policies?  PAGEREF _Toc62403321 \h 6  HYPERLINK \l "_Toc62403322" 15. Will there be standardized link contracts?  PAGEREF _Toc62403322 \h 6  HYPERLINK \l "_Toc62403323" 16. What is an XDI form?  PAGEREF _Toc62403323 \h 6  HYPERLINK \l "_Toc62403324" 17. What is an XDI dictionary?  PAGEREF _Toc62403324 \h 6  HYPERLINK \l "_Toc62403325" 18. What is the XDI Service Dictionary?  PAGEREF _Toc62403325 \h 6  HYPERLINK \l "_Toc62403326" 19. Will there be other XDI dictionaries?  PAGEREF _Toc62403326 \h 6  HYPERLINK \l "_Toc62403327" 20. How does XDI address the complex security issues involved with cross-domain data sharing?  PAGEREF _Toc62403327 \h 7  HYPERLINK \l "_Toc62403328" 21. How does XDI address the complex privacy issues involved with cross-domain data sharing?  PAGEREF _Toc62403328 \h 7  HYPERLINK \l "_Toc62403329" 22. How does XDI relate to XNS?  PAGEREF _Toc62403329 \h 7  HYPERLINK \l "_Toc62403330" 23. How does XDI relate to RDF?  PAGEREF _Toc62403330 \h 7  HYPERLINK \l "_Toc62403331" 24. When does the XDI TC intend to deliver its first specifications?  PAGEREF _Toc62403331 \h 8  HYPERLINK \l "_Toc62403332" 25. Who can I contact for more information?  PAGEREF _Toc62403332 \h 8  What is XDI? XDI (XRI Data Interchange) is a new generalized service being developed by the OASIS XDI TC for sharing, linking, and synchronizing data over the Internet (or any other data network) using a common XML representation, called an XDI document. Specifically, XDI consists of three parts: The XDI Meta-Schemaa very simple XML schema that uses XRIs (Extensible Resource Identifiers) developed by the OASIS XRI TC to describe and link data that may be in many other native formats, including other XML schemas. XDI Service: a WSDL-defined protocol for exchanging data and metadata using XDI documents, together with bindings to different transport protocols (HTTP, SOAP, SMTP/MIME, etc.) The XDI Service Dictionary: a set of pre-defined XDI resources for describing other XDI resources and controlling XDI data interchange using XDI link contracts (see below). Is XDI a Web service? XDI over SOAP is a Web service. However XDI can also be bound to HTTP for use in RESTful architectures, as well as to other transport protocols like SMTP/MIME. So strictly speaking XDI is a generalized service based on XML document exchange that can be implemented as a Web service. What are the primary problems XDI is intended to solve? The general problem XDI is designed to address is interoperable, automated data interchange across distributed applications and trust domains. There are many specific examples of this problem: Exchange, linking, and lifetime synchronization of electronic business cards, public keys, and other common identity attributes across distributed directories (commonly known as dynamic address books).* Internet calendar sharing.* Trusted search (searches that need to cross multiple private websites).* Auto-configuration and intelligent data synchronization across multiple user devices (desktop, laptop, PDA, land phone, cell phone, etc.) Automated website registration, form-fill, and e-commerce transactions. Cross-domain security and privacy management. * For detailed discussions of how XDI can be applied to these problems, see the XDI white paper at  HYPERLINK "http://www.oasis-open.org/apps/org/workgroup/xdi/download.php/5115/wd-xdi-intro-white-paper-2004-01-20.pdf" http://www.oasis-open.org/apps/org/workgroup/xdi/download.php/5115/wd-xdi-intro-white-paper-2004-01-20.pdf. What is the Dataweb? The inspiration for XDI was the application of the architectural principles of the Web and XML to the problem of distributed data sharing. The result is called the Dataweb, as summarized in the table below: PrincipleWorld Wide WebDataweb100% addressable resourcesURIsXRIsCommon representation and linking languageHTMLXDI Meta-Schema & XDI Service DictionaryCommon interchange protocolHTTPXDI/HTTP, XDI/SOAPLogical organization and navigation of resourcesWebsiteDataweb site In essence, the XDI meta-schema and protocol is to sharing and linking machine-readable data what HTML and HTTP are to sharing and linking human-readable content. In particular, Dataweb links are can define and control two-ways data sharing pipes between dataweb sites that can actively synchronize shared data when it changes, as illustrated below.  Why is existing URI syntax not sufficient for cross-domain data sharing? While URIs in general, and HTTP URIs (commonly called URLs) in particular, have been spectacularly successful for building the Web, they are missing several features that are vital for cross-domain data sharing: HTTP URIs do not provide absolute addressability of data instances down to any level of containment or nestingthey work only to the page or page fragment level. While XPath provides additional addressing features for XML documents, it operates only relative to XML document roots and is not integrated with HTTP URI syntax. HTTP URIs do not provide support for persistent addresses (the Dataweb equivalent of global foreign keys in databases). Other persistent URI schemes have been created, most notably the URN scheme, however they are not integrated with HTTP URI syntax and have not gained widespread adoption. HTTP URIs do not provide addressability of resources across contexts, i.e., the ability to share identifiers across multiple websites in order to identify the same logical resource in multiple domains or physical locations. This is extremely useful for cross-domain data sharing. What features do XRIs have that URIs dont? XRIs were developed by the OASIS XRI TC ( HYPERLINK "http://www.oasis-open.org/committees/xri/" http://www.oasis-open.org/committees/xri/) to build on the IETF URI specifications in the following ways: XRIs are location-independent the content of an XRI is decoupled from the network location of any data or services associated with the XRI. This means, among other things, that accessing a resource associated with an XRI isnt limited to a particular network location or protocol. (Most URI schemes in wide use today use identifiers that imply a close association to a network location or protocol.) XRIs can assert persistence of all or parts of an identifier. XRIs allow two types of separators (persistent and reassignable) between segments of an XRI, so the XRI can suggest that certain parts of the identifier are intended to be long-lived primary keys (a concept borrowed from database technology) and others are subject to change. Most URI schemes, on the other hand, are all-or-nothing. With URNs, for example, the entire identifier is persistent. With HTTP URIs, the entire identifier is potentially transient. The XRI scheme allows both characteristics to be combined in one federated identifier. XRIs provide the ability to contain other URIs or XRIs in the form of cross-references. Conceptually this is similar to using quote marks in English to talk about someone elses text. Cross references allow a well-defined URI or XRI to identify not only a concept or resource, but also to identify that concept or resource relative to another concept or resource. For example, a URI could identify a book, and an XRI could then identify a particular librarys copies of the book by using that URI in a cross-reference appended to the librarys XRI. So if urn:isbn:0-131-10362-8 represents The C Programming Language by Kernighan and Ritchie, and xri:@SeattlePublicLibrary represents the Seattle Public Library, then xri:@SeattlePublicLibrary/(urn:isbn:0-131-10362-8) represents The C Programming Language in the context of the Seattle Public Library. XRIs also support self-references, a special form of cross-reference that indicates that an XRI is not intended to be resolved on the network but is intended solely as a unique identifier. For example, xri:(@SeattlePublicLibrary/(urn:isbn:0-131-10362-8)) is a self-reference because it is entirely enclosed by parentheses, and as such represents the identifier itself. XRIs allow unlimited delegation of namespaces. While many URI schemes rely on DNS delegation, XRIs also have the ability to use abstract (non-DNS) names or identifiers that can contain a wider set of characters and strings. The XRI specification includes several global context symbols for this purpose (e.g., the @ in xri:@example/foo represents a standard global namespace for organizations). In addition, a cross-reference can also serve as a namespace root, thus creating a private or community-based identifier space whose management is entirely community defined (for example, xri:(http://www.example.com)/foo). XRIs are fully internationalized. XRI syntax builds on the W3C IRI (Internationalized Resource Identifier) specifications that adapt URIs to the Unicode character set. For more information, see the XRI Generic Syntax and Resolution Specification 1.0 ( HYPERLINK "http://www.oasis-open.org/apps/org/workgroup/xri/download.php/5109/xri-syntax-resolution-1.0-cd.pdf" http://www.oasis-open.org/apps/org/workgroup/xri/download.php/5109/xri-syntax-resolution-1.0-cd.pdf). How do XDI documents differ from HTML documents? First, XDI documents are XML documents, so they take advantage of the many features of XML architecture. However XDI documents are similar to HTML documents in that they are the common data representation format used by all XDI Dataweb sites. In other words, a key purpose of XDI is to provide a schema-neutral format for expressing shared data. This is what allows XDI data elements to be easily shared, linked, and synchronized across any number of Dataweb sites the same way HTML or XHTML Web pages can be easily shared and linked across any number of Web sites. How do XDI documents differ from conventional XML documents? While XDI documents are valid XML documents, the key difference is that they use a very simple XML schema (the proposed XDI meta-schema) expresses the metadata normally encoded as XML element tags and attribute names as XRIs. By using this approach: Every data element at any level of the XDI graph of data (including versions) becomes addressable using XRI syntax. Resources can be addressed with multiple XRIs (called XRI synonyms), including both reassignable and persistent identifiers. XRIs used to identify datatypes, taxonomy classifications, or ontology nodes can be shared across any number of applications, domains, and XDI documents (like generic nouns in the English language). Resources can be grouped and linked in any number of combinations. Authority for every resource can be clearly expressed by its XRI path(s). Does XDI require that I re-code all my XML documents? Absolutely not. Like SOAP, XDI documents can be used as envelopes for other XML documents that use any schema or schema definition language. And like XML Digital Signatures, XDI documents can also be: a) completely detached from the XML document they describe, or b) nested as elements within XML documents that are extensible or explicitly support XDI elements. How does XDI differ from HTTP? XDI service will most likely resemble HTTP closelyit will define the same basic GET/PUT/DELETE/POST operations on XRI-addressable resources instead of URI-addressable resources, with XDI documents specified as the default content type. However the OASIS XDI TC will also study the need for addition verbs to support transactional integrity. How does XDI differ from SOAP? XDI might be called SOAP for data sharing. In other words, the same way SOAP provides a standard XML envelope for cross-domain messaging, XDI provides a standard XML envelope for cross-domain data interchange. Of course an XDI envelope can go inside a SOAP envelope, which is exactly what happens in the XDI/SOAP binding. With XDI/SOAP, XDI functions as a standard Web service, and is interoperable with all other Web services standards and infrastructure. Is XDI only for enveloping other data? No. Like XML digital signatures, XDI documents can also be contained within conventional XML documents (enveloped), or they can be used to describe resources from which they are completely independent (detached). Of course these uses of the XDI meta-schema do not involve XDI service, which operates only on XRI-addressable resources, just as HTTP operates only on URI-addressable resources. What are XDI link contracts? If XML is self-describing data, then XDI is self-describing data sharing controlsXML that not only describes the data, but also describe the terms under which that data is shared by the relevant data authorities. These controls are called XDI link contracts. Technically, an XDI link contract is an XDI document that references other XDI documents in order to describes the terms under which they are shared between two or more XDI authorities. They are directly analogous to real-world legal contracts that control the exchange of information between parties, such as a non-disclosure agreement (NDA). Because link contracts are themselves XDI documents, they can be exchanged, negotiated, shared, and linked just like any other XDI data. This is how XDI data sharing communities can quickly evolve standard data sharing agreements that simplify the development and management of trust relationships. How will link contracts reflect the large spectrum of data sharing policies? A XDI link contract can be a blend of: a) XDI-readable policies (such as opt-in or opt-out privacy choices), b) references to other XML-readable policies, such as XACML, and c) references to human-readable policies. To the extent that link contracts are simple and machine-readable, they can become largely transparent to many routine data sharing transactions. To the extent they represent a complex and individualized relationship, they will require human review and negotiation. Will there be standardized link contracts? Undoubtedly. Part of the goal of XDI data sharing is to simplify and automate routing data interchange tasks, so standardized link contracts reflecting best practices in cross-domain data sharing are likely to evolve as quickly as standardized credit cardholder agreements. What is an XDI form? Just as HTML/XHTML forms are used to request data from humans, XDI forms are used to request data and form link contracts between dataweb sites. Unlike HTML forms, which are almost always processed by humans, an XDI form is an XDI document that is processed as a request for data by the receiving Dataweb site. Since all datatypes requested in an XDI form are identified with XRIs, if matching data instances are present on the receiving site, an XDI form can be filled out automatically. A human need be involved only if data is missing, multiple matches are possible, or the link contract requires human authorization. What is an XDI dictionary? Like a real-world dictionary, an XDI dictionary is a Dataweb site that publishes a set of words (XRIs) and definitions (XDI documents) for the purpose of helping establish equivalence across a community of users and applications. The biggest difference is that XDI dictionaries are machine-readable and can also support XDI links to subscribing Dataweb sites that have an interest in new or updated vocabulary. What is the XDI Service Dictionary? The XDI Service Dictionary, which is developed and maintained by the OASIS XDI TC, plays a special role because its purpose is to define the global set of XDI resources used to describe and control XDI data sharing using XDI forms and link contracts. In this respect it might be analogous to a specialized legal dictionary. Will there be other XDI dictionaries? Yes. Like real-world dictionaries, XDI dictionaries can be published by any authority and can cover any fields of interest, from very general to very specialized. Generalized XDI dictionaries will focus on the shared concepts common to almost all vocabularies (in the English language this would be the equivalent of Merriam Websters or the Oxford English Dictionary). Such generalized dictionaries can address a longstanding problem in XML how to establish XML elements that can be broadly shared across many XML schemas (the machine-language equivalent of generic nouns.) More specialized XDI dictionaries or glossaries can also be developed to support data sharing needs of any community, from a global federation to an industry association to a company to a workgroup. How does XDI address the complex security issues involved with cross-domain data sharing? XDI is not a magic bullet for Internet security infrastructure. However it does introduce several potential new building blocks for such infrastructure, including: 1) a common scheme for persistent identification of data and data authorities (XRIs), 2) a common XML representation format for data interchange (the XDI meta-schema), and 3) machine-readable link contracts that can include publish-subscribe synchronization of security attributes, such as public key certificates. In addition, an XRI secure resolution protocol is under development by the OASIS XRI TC. Contributors to this effort believe that a broadly distributed public key infrastructure (PKI) may be an ideal Dataweb application. Certificate authorities and registration authorities could operate as Dataweb sites, and certificates could be shared, revoked, and updated using XDI link contracts. In any case, when XDI is bound to SOAP, the resulting Web service can apply existing and emerging Web services security standards, including SAML and WS-Security, to the problems of cross-domain data sharing. How does XDI address the complex privacy issues involved with cross-domain data sharing? Cross-domain privacy is a complex, multi-dimensional problem. However on this score XDI does promise a key breakthrough: XDI link contracts can provide a standardized way to both: a) persistently identify data and data authorities using XRIs, and b) represent domain-independent data sharing and usage controls. This architecture is a direct outgrowth of the ISTPA Privacy Framework developed by the International Security, Trust, and Privacy Alliance ( HYPERLINK "http://www.istpa.org" www.istpa.org), so it explicitly addresses the requirements for cross-jurisdictional data protection. XDI link contracts can reference or describe privacy policies in different domains, and they can also provide an automated mechanism for negotiating, recording, and updating the permissions specified by these policies (e.g., opt-in or opt-out). For this reason XDI service and the XDI Service Dictionary may offer a new tool for cross-domain privacy management that can supplement W3Cs P3P (Platform for Privacy Preferences Project) and IBMs EPAL (Enterprise Privacy Authorization Language). (Note that XDI link contracts can also incorporate or reference P3P and EPAL privacy statements). How does XDI relate to XNS? You might say that XDI is XNS v2. Much of XDI architecture is based on concepts originally developed in XNS (Extensible Name Service) v1.0 and v1.1 from the XNS Public Trust Organization (XNSORG). XNSORG contributed the XNS v1.0 and v1.1 specifications to the OASIS XRI TC to help develop the XRI identifier scheme, and they will also be contributed to the XDI TC to help develop the XDI specifications. How does XDI relate to RDF? This is a hard question to answer in a FAQ. A summary answer is that the proposed XDI meta-schema and RDF use slightly different models for graphing data relationships. This might be compared to the difference between Cartesian and radian coordinate systems. Either can identify any set of points in a plane, but each is optimized for certain kinds of geometric shapes (e.g., line figures vs. circles). Following this analogy, RDF is a very robust, application-independent solution for describing any property of any URI-addressable resource, while XDI is optimized for a specific application: describing data sharing and linking relationships between XRI-addressable resources in XML. For example, in XDI: All nodes of XDI documents are directly addressable using XRIs. XDI nodes can have multiple XRI addresses, including both persistent and reassignable addresses (very useful for cross-domain data mapping). XDI nodes are nestable to any level, just like XML elements. All XDI nodes can be efficiently linked using XRIs. Any subset of XDI nodes can be copied to another location in the XDI graph without breaking any internal addresses or links. Like Cartesian and radian coordinate systems, RDF and XDI descriptions are interoperable. XRIs are URI-compatible, so XDI documents can contain RDF descriptions and vice-versa. Thus both can be used to describe the same resources, and it should be possible to programmatically convert between the two types of descriptions when necessary. When does the XDI TC intend to deliver its first specifications? The first deliverables, including the XDI meta-schema and XDI WSDL service definition, are planned for the summer of 2004. Early implementations of the proposed XDI meta-schema and XDI/HTTP are already in progress among XDI TC members, and the TCs emphasis will be to publish drafts of proposed specifications early in order to encourage such implementation feedback. Who can I contact for more information? Feel free to contact the XDI TC organizers Drummond Reed, Cordance ( HYPERLINK "mailto:drummond.reed@cordance.net" drummond.reed@cordance.net) and Geoffrey Strongin, AMD ( HYPERLINK "mailto:geoffrey.strongin@amd.com" geoffrey.strongin@amd.com), or visit the XDI TC home page at  HYPERLINK "http://www.oasis-open.org/committees/xdi/" http://www.oasis-open.org/committees/xdi/. The XDI FAQ v3, January 11, 2004 Page  PAGE 8 912>^  3456QRSTVWcde~rjUmHnHumHnHuCJaJmHnHu&j#q>*B*UmHnHphu mHnHu0JmHnHuj0JUmHnHu5CJOJQJ\^JjpUHhF0JjmU HhF6]0JjlU jU,X <   { I ;b $  $ %P@csce~ 7 8 9 R S T U V W X Y Z u ѿѿǿѿѿǿuѿjsUmHnHu&js>*B*UmHnHphujrUmHnHu&jr>*B*UmHnHphu mHnHu0JmHnHuCJaJmHnHuj0JUmHnHujUmHnHujqUmHnHumHnHu.u v w x z {    6 7 8 9 : ; < = > Y Z [ \ ^ _ ĸĪĸĸĂĸn&ju>*B*UmHnHphujvuUmHnHu&jt>*B*UmHnHphu mHnHujtUmHnHujUmHnHumHnHuCJaJmHnHuj0JUmHnHu&jt>*B*UmHnHphu0JmHnHu+        ! < = > ? A B ~  ооƾооƾtjXxUmHnHu&jw>*B*UmHnHphujbwUmHnHu&jv>*B*UmHnHphu mHnHu0JmHnHuCJaJmHnHuj0JUmHnHujlvUmHnHumHnHujUmHnHu-          5 6 7 8 ; < Z [ \ u v w x y z { | } n&jz>*B*UmHnHphujDzUmHnHu&jy>*B*UmHnHphujNyUmHnHujUmHnHumHnHuCJaJmHnHuj0JUmHnHu&jx>*B*UmHnHphu mHnHu0JmHnHu+   ( ) * C D E F G H I J K f g h i l m ȾȾtj&}UmHnHu&j|>*B*UmHnHphuj0|UmHnHu&j{>*B*UmHnHphu mHnHuCJaJmHnHuj0JUmHnHuj:{UmHnHujUmHnHumHnHu0JmHnHu- 56789:;<=XYZ[^_ྲྲn&j>*B*UmHnHphujUmHnHu&j~>*B*UmHnHphuj~UmHnHujUmHnHumHnHu&j}>*B*UmHnHphu mHnHu0JmHnHuj0JUmHnHuCJaJmHnHu+ !"#&'ABC\]^_`abcdپپtjUmHnHu&jy>*B*UmHnHphujUmHnHu&j>*B*UmHnHphu mHnHuj0JUmHnHujUmHnHujUmHnHumHnHuCJaJmHnHu0JmHnHu-./0123456QRSTWXԺԲԐԲjUmHnHu&je>*B*UmHnHphujUmHnHumHnHu&jo>*B*UmHnHphu mHnHu0JmHnHuCJaJmHnHuj0JUmHnHujUmHnHu+4o/ "0N+o12G $ NOPijklmnopqŹūŹץבŹŃŹץoŹ&jG>*B*UmHnHphuj̅UmHnHu&jQ>*B*UmHnHphu mHnHujքUmHnHujUmHnHumHnHuCJaJmHnHu0JmHnHuj0JUmHnHu&j[>*B*UmHnHphu+)*+,-./01LMNORS !ѿѿǿѿѿǿup jUjUmHnHu&j3>*B*UmHnHphujUmHnHu&j=>*B*UmHnHphu mHnHu0JmHnHuCJaJmHnHuj0JUmHnHujUmHnHuj†UmHnHumHnHu,!Na+6g|IJV./184|$$$$$$$&&l)|)u++6,P,,,^1_111152jٯU60JjU jU jJUCJOJQJ^J5CJOJQJ\^J!HhF0JCJOJQJ^Jj)CJOJQJU^JHhFCJOJQJ^JjCJOJQJU^JCJOJQJ^J6]3 /78SX]^xxhx~$$IflFJ.!   06    4 la $$Ifa$ &34 !xxvtrvp~$$IflFJ.!   06    4 la $$Ifa$ !#4$5$a$/%&$),-b0 1 192j2445P6677!8"8X899::;526266dUeUUUUUUab/b0b1bKbLbjbkbbbbbbbbccc>?MAxBBDDEEfHH!JEJKKMNOPuRFSSUAX]X]XYZ[\]]]^^^_"`aa@cqcrcsctc ! $$dN' 0&P1/ =!"#$%lDdP vuX  S &AOAS"bl\Ê=dkDnk\Ê=dPNG  IHDR m84HjgAMA|Q pHYsּk}IDATx.ˑwHj}& 8P:& ciN84 ;Sg m' 6 QG0 h! O@H^o隞}zyL}Ɍ63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63"̈h3#͌63",ȿ_ e ןjp,"}l/鷮ǯ/p?_.!]ҾM\A|Z*_-NNӇQAmjq[}Epo?|hUrkT1⸭^?\)%j'Uvq~qR"y|ZX ;~_+$ ]X)$N} gUz[T7Ji,5:y%]%6[N+R">(>I۝v;U8nB3-"]ըQ$U[dr" HW( ='-6TKb]$1h5 mĢ"Ѯ[QqsaqN.pv $WZw]2iw&"kl Ӷ'Yr|eucʵkfԼIlʽR+b29T¦ʵQd/Œۅu__7b&'4 `"|(+fӮ]tr9tuHa"b=-&9![\؜V]Sn-; >72tFy %Ž/l8ykV:2;Hv|%ywHdrSl-?(9 *0`|_~^eQ|r9Ad-0*w!RÀ-w0לGH]BBn}4zGl沀@n!F^@1"Pd^e,$Hr9$'"r~E,"P䰷rb"мe;F(my 4! "ɝ-XM9D b2O ;DcֱLŦkzֆuZ8cÎ.$ D>9CDZtwL6XfӠXIAD@BtMYZ^`LF3.ciSDnwTȆvZNN|iS'[_5@K}2"p98u2k u$Ҏ$N|iS' {MЅHMR"gl|fjp tiW(ҎOh! 3]"I;vFd;MvK_: WB"x Mze]=}բ_: lׄeD$]"M `Kk"Ѳ.3YQkLKl$5ZrM-r;U"J:-#"lZvEgDDiaou@Q%I.,"E^EUKH8eiX[y'@DdZy"9&S: [6]nH$Uy"IB"(lV$ʊ֑:"' Sen'pKUiYm"0u(W%Тݯ\@D8^WF0m0u(h:"$5:sO-̀D#JXY" '"M[Z@م}&D D: D}&D8mD: DAK4I;~ `@KN8"q0دZ%D}&D_q0["JXk>>nMw&Ђ_WĚȍr5D!b1"ȉD&3[^@b)/$r#uS"5.oEũC`˷"1Ђ:"iC$ۊ$:^H=d^ *4!1Q"CZ@Dg|MddLz{kE$gF%oIe ="2\nW׈p\I$'m3FdSC$"=HN%qDrH" o>R2翌Խ!) dHt[/H$uĺyeݥp?ґ?vh|4mvtH-h3+-9#C;y鏿<,"a:"D`&BS/P"K5Ә?a ;SD&?دi;*.Zz0]tN;"H|-ȖZzw!rnB(2z ѠY;Q^(!񓆘{,D`RDl .Cڴ!B'&$M q*C`t:0=ؾQH6LYDm|;#ۥ@΍(d^V""KWVu^, DHVqWi0-XDLJ.G5@axI$X:+yr%3l$BNX#kVuNi!%$rn~hHD97~*jNY; GdKy݀H ZȎAd;qKMF#I&2K@D-D|gL97l sux"E6C|lAg>/5@B$9WR9I%~RmYy*u^=H:%Ddz5rE 6It @*:7I4my"1DC&Ze#pc&M We"JDഝOg;Nb T@d ݅㡰ɉi;j/ߝlkh9K0IfG[Ha @#3L"Qi'&2%ӂ$B$PR 5tMF$(9p1AFI=ި i '"HirD}iD~Ļ5Cב0LDdӔJ]DlDbc"R=S D'K vm8j29|+WIf̟ C"d$DBt…DND0OTHĥJ~: p*o  L$'tslpDSD ~$ D$i}εڂӕXk誃IM uK-FX"JbAtc[׹ ED%$ndJ tDb n &]-"~w_hRCv"Qe>`"K#QVGh䘣sˉs\EDSk.DDmwwu,# 2V@$^ВtY7""o8`Xt Dc%¥mâ):3aАñYObRĤ͛u؀I@J/H\ā0ˈpi4ޡ` y{ )%Od.m;~Nc\~"@SP#4ONՈZ{Dا0w"O }-$"ߠa}6x7#|U>(>6?Y@}^!4tDq{a&"M&,3YDd_$DهHy&mkI% !Jכ\eI[]CJgӖOdb]gI}qpL#g"DH5"$"icf]ϋln,gJ IuDI/o|i 1}|k/N|""{w-o?›D@,)ײ&!S-^{Z9{G$D$=$FD_۟g`i"ќKep"M@8963:DX7)"qgprȈ%"HyR/D@/,b`+)>2"Hp"` DYêVuJ$DdS"\!FK۱lDY ׈vse"|`ȽSF$:BBzFV$F][*@v aߍHFz{$*C%r"sK"YU͎{HFjf9S4i#׸x"?HF8]2r]9hx"ҕ!N}"ȕ H&g#9Dr5RN$^9%gPB?w*.UK8ݽK.Zٯ*%%.;PpJޥjK!>/בj"=5ҚiI!OvD.Ј򕽜Ȅ%.;9rȄ8M%Pt#ZSQFD&gm@%J^\ߣW-13;'5%@@#@r5rzə% Y$RMDZWD^S#~rfħH#oU!,O^D [(qU3 C#RM+˻FrWeh$4]44V%)yUk"+@ L(qUՠFrVH69D?L#5\Gr^I_uJ\pD5FvF!.)+;]ʮZ5ZH":2Qȧ2PuF7jG"yY DnՐqבTK4@ND87jqͫB\ypբc9044̰kFȩD#Wj#jKm# .!4%]@4FDbXHG伦4$r#>@d{,'r^~Uk?m4ab`;e ջf?<"&2îUj$ȵ+q"_\#42iۑa;,"w$ZhȑHL#Y٤:"꽈@aM4RJdZh'RY#(r`WXGf+54a 5r$b}",u_վ`;e VNBD^YDE̩͔Hi[p.HD/SA#[[GPpreԿ&M F`"Njq@1P}"5OF1JO%=RV %kZCT-=D0 nHWU'nn]bʼn ^B՚B5Ո+$#dDL#FJ"#Jg ʮ#ڈ5{.w㏱6$T#@#VG"NH'V!>L#.+VN$|U"5j1VȽ#NLy(]+{G"]4 3_ NZF|"*M=QI4{ȭ_{AGPu;ILdZy$5"NL$G#1VD.5DDt]> 342FM HwQD6vhdJ qٙ<f'2Fx"Vjqb"[FZT-NdJzתeecޠ~9z "w}HçGJߠNcG(xh{DH4&r$&b'@#C [:H*9D\!i#Ȗ{'uՑ3F"ZNLdZh\G.҈#>Ws'0]nyQpfj"2i[D:j~_5B]ey:b_FOd/NLdP#XY`לFns_1눝GH{s!֑<".(Hz9D&YnA"YG6D}52a"ODAOȖA$&!8~RD4>w՚5|~K;QhrD'k+X5G@#%DD浰u$5"Ȁ=H"aXq"ųILdZhZbDFHc"h#2FZCϻ_]]I[H#j޼C<=ʮN#G׎6_ؒȦ^##\PvfO4}:rDn;Cլ#F4V-ȳ5{-*kjFDW%r8=DG4Eo5R]בq(Gp"Gj4spA=zF#nYGT!#yD񹂕#Ѯ/H|34fiG+NFvfͿ=M]%'jdm0КѯDn!w4=\G* 3_ȽWv׃H֑l^ 'ĆDo{S2u\P:4ȋuaU"V0U '&kĪg #>f.A!#j TBL#+ZvB6y̯p(Ј35"'kDcղ{=fkF|7zD$ogGZ(<4l^ U4bDb! {'rdqeoH4E޿P} ׂ=λ(?V. u bHK"4Ҙȳw_"8~S >ՈDR#0HVJZg ]F^DPHb ֑!>qLצ/fU܌HԞZ`H[hX|$ikqfHl6Hu4{sv4ZfD6Dz:bF?Dnh$2FEQ t{-瑧U-ӈnCT-^FC# 8xtmUuԈU-ҞFĪV="M<#G|nV iODv}6HhUhDT-_#CTv}}RUFvfVH/DjDP}"ֈW!5CG^#v7>mEZG" Z{-*TZ=N"CG!tԈU-Ҟv_׈F"b^ekyFbHdZ嘮R3GD@k JFjmGD]{ui+5r`yFӵi䋉53C(F4jkx QҸ?M#z<Ց="miwUHI[wPMWP#Fgvgu3D=6d OiwQHG(xzsyi$m5BkĈx# ZF6(Јu#i zU-6mOXGk{-jFR!inI+X5:G.43CWÈpEZHio'lfr5[vUH3#x*5bUK59"v!mN"Vm"VHjQ^UF bڮpQjU'qeJ#CT-F@9"6/PMW-FصUQpBԨVvejֈ#>EZǪeҞ֣53CEP+wjD%_#W!53_<#G|>yvUK^˪Vˈ\Yn+F"[bfɳaxҞ< HںkjjL 'Q##עBփUi$ڵU/P#7ZF3UK^i誵3CŦyUK#g4#brDiOӈ~"b,kDeDR;FU-6mi ժkMFWWv*TU4Rnu>9ƪ%ѵ#>o4\Y.(X5yF4V-H #BZGidZ`ݙ+Xه M#F֑qDj6FHiJ#M%+5M#&JZ52|RGdgjiGjyD<6M*\M#=jUYacȪja!zMF(KN"y\#U~#ȯ>^FnEdt?F6j|? yEAժ,"{ESs'"A+{BdAќSqjݯ"h ]#D\qj24'n9D1Y#85!M<3= DfYtcX#xR"wƑo3z3{CK"+5R2kdy9%B䤑IߣDuz9iADRgҠWi)i)wnCdKyD#]xANd=~4WZw4"ߦ%c]!O.ѿxalbk)(I@yp[B" و2" >H2M8A6ݖ֏Y vu(;$v&4HAv DD"#BzI> HD64'ȈFC䇕Ѝh"%ۭ5}b4"Qs4:ɿ[ "s2"@E$=֞NlDwݲVB"W'&&4O%#$I1VM"`D2w+Q"!w'LJɑ惈Hz~d"VD3#s D\&bR("~}1X!T]!:ehDd/1%"dDmeDl?""/YipS"Q+Jdu:=K`=pıHL< Id'7~B~)9 ӈ0 T#RH¢iJf;S]S"5oT$F{sՈ^܂5"%2S6FBلw#"~w<8iZ -NT.ITLDшBW ID6 Dĥ2y`4"+B,y uC5"$4"^et&tx*A%tzV "KjiRMr@Rf'"K~JYΦr"{M̕ sN#|Vn応7k5F6i95y )E%3GD@d2үC6alSDjn#Ir3G}G%"57[#GfKBdv"λbMGL,"f ]q%H;[9~$D*n$IMD\Lۃ^ɝ*tyuDjt x "=iD< ܃+H "=G""{oYt~e:""=%F#ÕKlD* /ӈ85u(y~%\hj\QȊ#U!"ʧHL2T$i*+$ ;uO""=T!"u(y@y ") ;JnJppd}ƎB܄H'bGD!7oͱDqN5HA"_~v?1q a٪CDC!=(X"-2Wp̴b"^9<~ uMJAbC14 WR"@.@e@HdQ7blWH{DdɈDڽr"@+DDŋ̫b"^viDV+$ !p]Nh:~Z* "ZYHCU! ڥD%PUd|("/ltZ+6F,D$q}FD7ٓnËj(%r~1<vGJw_E鯑o:yb"e߈mYDPf9U!Nz 4ȧv +Ӊ1"~nNSy $;@ hND]Ndy# kO [[>aW "W.O;kO:Cb"SNl" KO+qrˉo^D^(!_-1劉``5 Rs-"ɿJӽ_)JDD6W Iu"JHr"Ǭ֩dyw,i^1sg"W~=D>%ƑAd~#V?L'pYLt֪K-m" D|_˫ (34 ]r덈Y5"i uXn˵~q6(9!~o\%"Gd"dI$THZ"^G>[`ҌH`B#+:fD$QC?F9U> ^Hu`2E9DPdH<;aĊe="O|x~Do·q#{EO]q5섃,u5Z!q 4NGEvd#./HZ$E,Pl DLy$sADO)u4ȫ&R$.hV]+)݉`ΫjnY]"H(O$B~!YY+w_G9,%BD6S*GvF\ar[5 &*6 f,i-6кVs"4f3E)&BDiG.#ruDSG@Cħj$ ( ٞ}4.A 5Y 5V`5 hԝ>99ӹE}"06X>}#>[4 hsK jzη< I8}F>[4~pzK twnЀHP* 7!R_#:pڀH Lbu@5:% $F" 4Ӆ6^*ۂYDjo$Fr.Ds5r^e/!:uah$ۂȹT:", \,i-6P_uK tZ}D J oBdFpDy^WnDgs$M4r5[Gg099Y^eU׈?IkD4V&Q@HM4҄/ k"Kg.#Rϫ O!D#tMZ97ZM4r"N_B$lpK8Nq";lM4r"NAVS/=D#8l"UD0=4f߽jamS$gm4^vZ&yk ~w"@hD) vFA^hu iMZ%D.҈46'Q4Ҧj4s"m"Ỡ-V"7u.!2 n+FL#i0DN ~n6ЍFjahDU-_# ]#@jܹ2F|"]4Қi7D^!FJ}'*%5RSnr݄@UZ"71%D,VVu$eۮ#9}j]F%UJ#"PjyDi䒪u yD=̹iD[H""9R#RrIL#yDL# FDKNwkk"7H:ӧ<QX09bU+emXꢑk\W)9"HE˪"P rw  Dp[ZOhH*Z7l=i$eF\䜈LCLO% #֪j)H>meOٝ4Gdd,u$e1rdI*"܆;̹i4ȚEfD}[A}ڨjILȌ&{i$e`v-ogk_̹U-m4Z=poiUJN^~m2U+p۽jahd0{-kXw6PZшUϦi1|6Zw_G0獪V5GRi) 5DDFH>s*NgdJ}ZJUFT%ԯ#@{TFέiĪVflzKV,cZ4bDi䒪5RiCjUJ4AiDFl{tw"نZC26:C#O% 4bUkZ4bU42{kRi`/$K]?`9D#NLScD#,u\Fj^#sDSBĜK$p۝6D&Y2mȪ*%FԿ 4[#Fx3LFoDV.ZNLS_^IL侖Sysnydre)3"Ft `ɪ5w_Yr: LF0F۽WILHh$F0iD  ܚFֈ69ZOD0hRiF$e~yR#RrL#ߚ3KV#KLk AkU %D\2uX ײmjnM#Qk4b+ D]ksjSFȱiqei$eʛ%52{D^Bd.D8Y2mH8zT-FtkĈezF&Y2Mʎ9WZ}s "sYr: l2"V9{L#\G&Y2M: "NL_UV9mQ%ԯ#K4d4kA֣j rW#59ȔLR!H =ܻjM42 >.UKFzT!2ٯp̪g{FW-lhd.L#)SsJVhĪ6[ԈF?jѭ#A%d4+;漇FL#V#VL# D#S2uK>YGji[G.ZS2u)Kjd֑%5T"@/!2Rid4lV#j$p۽jaD#,u6FTZ}Ύ9Q8!fh`Le)Ss{be^k06KLe j9Y242#l7$K]69ZO-5kj[#,ufHUfM}œ+H>ZhRi5 Lei$eϦwewe70 vZ@_Wd˴|gٟ~K,R/?/.ԧuDs9懞uLa\Fx"m5r'rFѢFNn@R52RRW%ZDkDYպ9懮@#tZ 4U-'rl:27H]NDi{B<Ɗ9V  >7hmud+=[j֑D.THD:wQ0@8i(l[Hg4&L# h$L#<{A`+xήejno#bA\GiކԈ#0~1d_ " kDT-Dzwo.RA#a&w5V ,cX·՛E-1V4CDF0dY ǼFnSԈcnz~&2FM2" ֑GiIAV="Xq"ֈƪuoX249D#S!A4@h$/,HDim4=s~ Zڈʞh)(ODF2,cÒ;̹R"5򴧺Dy:@#4f*{ۜG?t[G%r hE+cL#DGya=# uy0Ј⽿cUJ4bDY z_+|U"~J 4ȤHF2`M#ڪ%HF%D4V9?j췃4iHEv]G#:ƊY#i#[GHw՚DқHG(8!fGW%b_L#FF+ AœW17 ,chq#'2Q5b+;LGDқȽ52=e7ȱRaDhĪV-" wQ|a㇉N# #T-%DVo"~>2a=YGL#-llX\5ȐQDd*$<rOkQD}fD9`Εj(,C͛#q5ҘȽב]A#shaZDq\aoCidz` k}FS@'5,i/mj4Bk"Ndi1&2=E# `Dxte>"XxT 2'pmc p"ǩlK$O#͈鲎'rV'%N$C#Xx( +{Yx("]'W\K" XLrx:r^ep|Uj|Dʎks[.,"ZUJD5ZDr4QfeOWIdjrb`+{?T%k:j!W5S*k$jFHw!$5$H#k.!Z#DWA4QJ{I,W#D4"j!ȄxM@Fw>6QLĽQ;&ni[i+V亲jDarW"549f$2CWk QjC$M4 DpWY ǀF|w!k2"s-" 4]ޠjAW-xM)Ȍ!=4L^U {~Id+HXՎȄ!m4bU"BNɉoK d7]Q|H}-DzjHqƈ JEy$<4#r@cN#KMoݻDF>&Bňr,?MڍicDʉܱje99i'vv0!=骑b"&2ɉĈiJd<шIlQuڍ/ANFKiDUD@]\U94&HZy ?F2ʉ89 &MDfsz6DHm DCYޘD4ZzbjOD#ih' W- ["|g|K369ya"ЍDf3oik+=+,kGJd kĈI6D+ȫF>[7l! ŌokdD"e͏򽖜);ޘ㋮rj52g8ܽ&!h"\tou D|D" Ј4sD+2֑.D2WH4rHx=W#9$R"@M\s0DAH$^Yy"*D2DB{E9MDfA#&rJ9WhxehFZiD`0H4qb"5AN#+ȱ/ yAg{ڤyy_K~Ə[݉,gFJ{m2P~Df y޸q cmOL>c藬r,gD#b"`(ңH dȏnh"~׈HFFĿ ȕ;'֑B"D%pDHr-0*hD|Uw" шFL^ҦJ#,Zˉo[ХLVz4Rrh'hDcD }Yv9)$@R["DeYՒ9r/"S;"l⾵W{".+PIL#|N!Nd\C:h^4'on@dSHdb>GވH|gL#gAH#稄ڎ?|=~{,D1oBde]agQ"4joVf_ ~J"%Ž!s "SK"se:#0q #R"D!"Fъ@S紅v.Y'MK$kޜРuv54"$r܊4!m':':"%5@7 %2CD pJ"{xidy>.;9,20OCN~sw!%ڬ^ot ViJB7 xVq "u"B&Dr4|*!L2"@ 'ZYuL{0YK|#]"'gf8 *3#kD$hw9zlCEdjH`tAo8 jygV@Gd<ab>2 6YV.gO }"DB"yq" j<^)= T#2"d\`B"~ UHdMe78wJ)ƹDScDfq8D>!D2H#|!j@d? CLdGyUq)L #:]ӝ:Gk)9_ZXD$bYǁsT#_jGdJuZH[[Hr'ڃyA&2łY}})9DYv | YXDSS^=ɕao|B'43< j|}Om saN#pDb~שVDfq \E"DAD9&Z'6kg{-"!1+"rV[TwT;μRlDI$>׹S:(7n oe>s㥲2+eu"s5"/<8F H@+_]")ŏN@dy#i$^Fg0]gWS7Xt8t겉o2D}nH:XDҩ{A$ 3h"d5,I1aX<D7bFB"3ŚDb #βKl'~ê.2H|>_f#DYވPAcX + +%<" R#PDuJ7`̖+{@:L"1=wԒi˕z$e3Z[b@H4XDoYodӠU9 X}"F`U%2_]UM@"ʏ0x#B& yas#\ \P"TXN#ĉ߿M]Zj 笘+t7s%"%D7b XQfޙC"D1!?#G#H@d݅ސF< LXdKPD2{$Xdqцk>単<^G h4UFiǷPfd/!c&F4!.-זY&?rd(j;qr"%iբ}ZGeg F.ܦ!iȇ?{HEڝGُynql@:0.?|YE"cծU&7eDAYJ""1Pq";=?L_G>v |H2"t^Ȍ9]ވȝg}Xnbn>5i[CsI>Ad~#De9%@I5BjX[_@_Y}j:NBdl`N xp{V; ߃BEbM"@Je%"09,!n,%9pFjL$s;Dn~Ӏ L.b[\Y>V}]@`\Iy,+ܶA$o* #,oD ~2Y'"2g!NM֠5$Ǒp"kN1DܺcgvՎH","1gb"t\Fg-<"d9u3UFd~#=d{J2i5uJIDdy# tvF9SDf6"92M) \ىF H["3Gv3Nd b"9L$eLr۞GrD N$TNDr(#ۼk2g+3de ,*4Nv 19W:"Ө/; &Qgˉ}kMl0 UGr- L|C ĸsD8W`Dh@k.XiJe}-Ho~S*l"r\r[kDL]%թ8Kas o]̧>4bw/"b=uڥONp\Hb)\~u6Kg>pwgvy]0Gjl¾&!6qAdzO˅>눴΢O*->V_K.̩>m 6L0KJ1"g9MDΤGlz%UT&4ŖMFc"3DՎH4ԑIU*kjCE3-.3uc''9UDD&LWDDFa5kT"" P}>5~ZALA)7hAOWkI≈J~uFD*$&ِty5#OKg@DBY+BT]+B"@~W- L#Ad|DS!AYZ$vHt%?@dθ"iv< 4MHG# ;{ j{}}+ B?ɉ?"RspCi 8}.j"]%R"t銉K;'D{+a!#I3fSy;| vM3.F(bXsE"'sD "3rT#NX";' APrJt}AɽB#h@AvfP"-yUR"0Gؼ0bD;U=W%A}r0") ]VRX̒>DvO`D^P_|DD9NVܧ*D"܊_sfPڏVܹgr |ʉHׄF#PI'Yx_MvC y}-KVv0eVJD0OU-d+$GN)s%"@_2rQB*TRY@OiXH$P~5P"//,#⒓AS5"l_i2s''x/(/n|1"3t^ᒓCdc-L l. psMNnDuͽ!Hlt&}/3؎s4LdD}a>''p";̒s`>Y*[ǙfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDfFDmfDf?%+7IENDB`DyK *http://www.oasis-open.org/committees/xdi/yK Thttp://www.oasis-open.org/committees/xdi/!DyK khttp://www.oasis-open.org/apps/org/workgroup/xdi/download.php/5115/wd-xdi-intro-white-paper-2004-01-20.pdfyK http://www.oasis-open.org/apps/org/workgroup/xdi/download.php/5115/wd-xdi-intro-white-paper-2004-01-20.pdf!DyK +http://xml.coverpages.org/dataSharing.htmlyK Vhttp://xml.coverpages.org/dataSharing.html{DyK  _Toc62403308{DyK  _Toc62403308{DyK  _Toc62403309{DyK  _Toc62403309{DyK  _Toc62403310{DyK  _Toc62403310{DyK  _Toc62403311{DyK  _Toc62403311{DyK  _Toc62403312{DyK  _Toc62403312{DyK  _Toc62403313{DyK  _Toc62403313{DyK  _Toc62403314{DyK  _Toc62403314{DyK  _Toc62403315{DyK  _Toc62403315{DyK  _Toc62403316{DyK  _Toc62403316{DyK  _Toc62403317{DyK  _Toc62403317{DyK  _Toc62403318{DyK  _Toc62403318{DyK  _Toc62403319{DyK  _Toc62403319{DyK  _Toc62403320{DyK  _Toc62403320{DyK  _Toc62403321{DyK  _Toc62403321{DyK  _Toc62403322{DyK  _Toc62403322{DyK  _Toc62403323{DyK  _Toc62403323{DyK  _Toc62403324{DyK  _Toc62403324{DyK  _Toc62403325{DyK  _Toc62403325{DyK  _Toc62403326{DyK  _Toc62403326{DyK  _Toc62403327{DyK  _Toc62403327{DyK  _Toc62403328{DyK  _Toc62403328{DyK  _Toc62403329{DyK  _Toc62403329{DyK  _Toc62403330{DyK  _Toc62403330{DyK  _Toc62403331{DyK  _Toc62403331{DyK  _Toc62403332{DyK  _Toc62403332!DyK khttp://www.oasis-open.org/apps/org/workgroup/xdi/download.php/5115/wd-xdi-intro-white-paper-2004-01-20.pdfyK http://www.oasis-open.org/apps/org/workgroup/xdi/download.php/5115/wd-xdi-intro-white-paper-2004-01-20.pdfr#Dd.db>  # A"2"Y 7vU0"`!"Y 7vU0@@x$rp:"xMUǟZs>nHB6L57HͨAF*t!$.!sr!%%򿔢I%c$IZ>k;<{^wܣA @A$jAP@ rA![ጣgΓg(m[[.ş7p܅m#[8W㫼ge+ d"fߨNJȚG(+Dei N"bɳ%C=ab9 bElQ XY,p"bqƬq6d/b6-`FK<(CTRrhODdOh?=֡ED ?-A鲖K{uϻ:vsXd!~H%D+ҜY]iVCkUR;ڒ8jq]]+{Wýőd} baFiU{#Wl76o<`&tl176¾G^IOzM<|NJ#xilU+o{ŶY}c;]CVq k}f͍mDӣ s{TV3:ѽ9ޜ9En͸m}qsԉ0$c{ Vh3 =GsHa1F=8Þ`Ա' k4G"SUY9=D2z2Gvͮ.o]jOgRT!kD0#("Rmc7̟`O4qhXcL(Cd:<;}+֢oוֹjNJjƛ[DE۬wXeݙ*ǡYc["ۆ9[kH/Չ -V}}+"Q{wXy. {UjgVS{%2ƚP[-pkJ{5&QN~%{bTɅGJG[{uc~I??';Qu@"uСx?AI?!z!\$0RGs#HqqsR):?WJ~F񽍖SO? P.D"5g." )P碒A*P˖HPoːrwsHP[$<\ڱ?W$H{.[9Rܡ?|j~\^u^ ZjIHP?LI?s- ൑=|rՖ:HՉ;_G^׭cʖazix' jۧj  uIoTC߱P/B"q"IoT#9H/AIK};ץ~Ry#^.H5]ܹKw&p&~RWx^𫐺u$ Uy*H5;ݹJx3E^IxsG\%R-^\-$%R-~{w VQ}WVջ֒^TaԽt{]ncCVtUcrҼ=$?#տO=" "C QI(2zFɖGcNÏy- !C뉹$|Rj\$qwis=. P_2I!x]@ [\oHJV:Կk$BjʵJFmo7$EjʵV#ޡmϵ^7"ѡ6oϵQAZ?;6KHP}Ij<\HV:ԬYJGH}PӧH#ݡLϵ]?A;?')RZ^{h\JNvZ^{h\;%s>ws}. _ C  I/_?\_JH}my^oys}# gw `7y u2JN=%Z xg:;h)]P" ]P>蟫$ߍ5l%RjH\$R=p3V"jd\ESzJx/z9̙zIxoz;K/- }P# P˗' PW/ `x۽r AH r-[s H 6^K^v\C$|(RCj\C%|Rj^\$|8R /+pIk?k$Djw5R*6^%| Rc W1>Fݾh)oTb6'` Ʊ9$-DKSW6E@н$'J~ROOI f3$i=Ꟗgz6 {VGгyI,c\$^J %H^K$|.RsCs%|RB$e^}WyY"0l$+^%H- }g^" !Z]k^TiG$/GjyrI_Ԋ;&Ro޵) o!V[աw%| RkB|H:DKA߀D&@0C ̤-,kj)RIRLLOS$#|+WsI$H0> rj!3WHڭje}JI5RMӼrD.DΝPI RmL rDnT[߇sDҾ[L/+-Hjg}NI=RMurDҾMϐݹnD3R6:tDT3AIR̰c'I$Hu6>w,.fX缋$vWaHw#u9[IR̰y7I$H0!=d]c乤4EHO2iֽB_Y/I$H݋% ';GIRB~Hz$DԀУ~$ a$#58l,=!W!HCz*= aWaHÑnwH#z!=*#%*}+DԘw1Hcq8i0әp.p~Ҵt&Q]fm+ޭioޤ7 tmL_=ӖREem:[{DzmkzmfBzfR/^LZ~7U^Z^4(JMm>Ii@ߞC,UO]IN]G'Z9x\jJ?II5g_LͦWk5zm9 v.t!YB.A-"r|O"SK4)YAEd lCV:#ȿD>KE5[w4BOuգlg4,6SĘĦ3*Cx7ci YZNtkOgotO5ӺMM}OBfТkF:4>MgХ軩kx?E8@]*SwrޟܫOE]oտ Qd,}0>^?JѦz^Ϣmٴ>D KE:KK/yK}n;|*=.ӕ:4IŘ ;IltCb^:}t'tCÏ, ,vfXVݤb31lvjU$*cjG"ä{ +݀%7؝Az]6A?R5굘EOgu)>e7։FXoJ}K{:yB7I=C36aIR7뛤GY+K <\'Ot?uvyV?5E=AFc:;5w%..t/N͏nd֝|w]Nw)lm.0P*4MNo фfktwyFQ?7hgYڝІEQèB؋t Y< ŨBsԵCmvj!Vmfd|" qH\L&\?"BjH,~#ذ+H#XOsdN&=B-}4GeDFgCge譗zol6Wv:Fo]?Y{ Inս%VXV< H- Z+ r#4$0 ƢnDueeyp:F:]00} ݱ|h4˱.$?F;= SMYA r=]N'NM<;+b:I!Xjp1P{:[6٪t#tnJN!槆HmRo[aԜlT> ;M&KQ-Yg.L<;Vm/mA5eJR#;8'"2rK,}ZgQ\vt)MC^Ĺ3їC>[0MN/8w|[z>?Ictz~{q7&yz̤QCQ9zz4LWچ!hw'd#F6QCs?-}-J_IЗSQs4}zq<_KLFh/~dx馧nKҫyV=^UW{'KzҖ^ud=RU#{骽WDf)xUGv?iY ^z\^ UgV:tՙ쥫s^j^j^j^z /]7tA^ #y骳;KWg:N/=ӱyLG`LǓB{e䥫䥫FU#{陎 u/]u{骑L#g楫Fg:f23+^Q2/]|/㕼U{^z6x=^zKO^sߥ ^zՑи9KW`/'^udV\KϴSKWY^ UgV:t~U9KW9KW9KW9KW䥫F9KW^z /]uv{ꑃLGݩg:6O̾xRUW`/]u ՟3tt^j`/=ӱ`/]5ri̼tLLf^z^z+ʆ.0;^4O~y|KKϭW/^z6 {j/K?^zգ}Uҫ쾇*x骑tҫ~"Uҫ~U3j/TUgV:tՙ쥫ά`/]t~UkUkUk#y骽쥫GU`9KW^z /=Qwx陎͓g:g:Խt"KW]/t /] /]5r9Ktl{骣0KWg93/]5z8/=1i^O3˼}։һm99^zWKE^zM/=jn/=KO^sߥ#y ^j`/]7##LK?սtՙ쥫ά`/]uf{3+KW`/]t՚t՚t՚tA^jo{ꑃt9쥫GUgw9Ktԝ:^zcy陎{陎'u/]uU`/]9#KW9KW쥫F3^( U#{FKWKtdgWl}NjwX/|KnKj/=^]a5qCnW{^ ҫ}W}t^jo{UGv? ^zՑOZi?W{駺:tՙ쥫ά`/]uf{쥫sZsZsZs9KW`/]=r:tA^#y陎SKtl'/y᲼ǣFdNy^}._a5B{;TVq;/ڶ.,r|;ShKPtDyK *http://www.oasis-open.org/committees/xri/yK Thttp://www.oasis-open.org/committees/xri/DyK dhttp://www.oasis-open.org/apps/org/workgroup/xri/download.php/5109/xri-syntax-resolution-1.0-cd.pdfyK http://www.oasis-open.org/apps/org/workgroup/xri/download.php/5109/xri-syntax-resolution-1.0-cd.pdfDyK www.istpa.orgyK ,http://www.istpa.org/DyK drummond.reed@cordance.netyK Dmailto:drummond.reed@cordance.netDyK geoffrey.strongin@amd.comyK Bmailto:geoffrey.strongin@amd.comDyK *http://www.oasis-open.org/committees/xdi/yK Thttp://www.oasis-open.org/committees/xdi/& i4@4 NormalCJ_HmH sH tH Z@Z Heading 1$ & Fx@&5CJKH OJQJ\^JaJ T"T Heading 2$x@& 56CJOJQJ\]^JaJNN Heading 3$<@&5CJOJQJ\^JaJJJ Heading 4$<@&5CJOJQJ\aJ<A@< Default Paragraph Font20@2 List Bullet  & F4"4 Caption xx 5CJ\.U@. Hyperlink >*B*ph*B@"* Body TextxP>`BP Titlex$dNCJ0KHOJQJ^JaJ <J`"< SubtitleCJOJQJ^JaJ21@R2 List Number  & F<O!b< Graphic$xa$ 6OJQJ2!r2 Quote]^6,@, Header  !, , Footer  !&)@& Page Number@ TOC 1&@& TOC 2 ^&@& TOC 3 ^&@& TOC 4 ^&@& TOC 5 p^p&@& TOC 6 L^L&@& TOC 7 !(^(&@& TOC 8 "^&@& TOC 9 #^DOADl Drummond ReedB* CJOJQJ^JphHoRH Legal notice %$PCJOJQJaJt_ X<{I ;  b 4 o / "0N+o12G /78SX]^&344 5 a /!"$%()b, - -9.j.001P2233!4"4X4556:7Y7$9K9::;M=x>>@@AAfDD!FEFGGIJKLuNFOOQAT]TUVWXYYYZZZ["\]]@_q_u_%0000 0 00000000000000000000000000000 00 0 0 0 00> 00q 0q 0q 0q 0q 0q 0q0q0q 000000000000000000000000 00L 0L 0 L 0 L0L 00 0  0  0  0 0 000 00- 00X0 0X0 0X0 0X0 0X0 0X00X0 003 0 0z50z5 0 06 0 08 0 0:0:0: 0 0-> 00\@ 00A 00D 00E 00>G0>G 00nJ0nJ0nJ 00N0N 00S 00U0U 0U 0U 0U 0U 0U0U0U 00[ 00@0 0222225eu !52tc9<=>?@ABCEFGK!:;]Xtc:DHIJLMsc;1 34Sd8SUVXw79:<[>7[vxy{) D F G I h  6 8 9 ; Z   " B ] _ ` b  / 1 2 4 S O j l m o *,-/N I. ^--5.dQQQ]0^K^j^^^^_<_t_XXX X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%̕XXXXXXX&-/5!4?2$ӊ; Ssg#2$Y 7vU0"2$@mBQ]rx&@0(  B S  ?t__top _Toc62403308 _Toc62403309 _Toc62403310 _Toc62403311 _Toc62403312 _Toc62403313 _Toc62403314 _Toc62403315 _Toc62403316 _Toc62403317 _Toc62403318 _Toc62403319 _Toc62403320 _Toc62403321 _Toc62403322 _Toc62403323 _Toc62403324 _Toc62403325 _Toc62403326 _Toc62403327 _Toc62403328 _Toc62403329 _Toc62403330 _Toc62403331 _Toc62403332#25 9.0"45:7$9:x>@AfD!FGJFOATU[]u_ /F` i.0W45X7J9:>@ADDFGKO\TV!\]u_ZZ  9:0^^  !=_?_@_f_p_r_u_ZZ  9:0^^  !=_?_@_f_p_r_u_ Drummond Reed1D:\1-2003-Drummond\4-XDI-TC\FAQ\wd-xdi-faq-01.doc Drummond ReedQC:\WINDOWS\Application Data\Microsoft\Word\AutoRecovery save of wd-xdi-faq-01.asd Drummond Reed1D:\1-2003-Drummond\4-XDI-TC\FAQ\wd-xdi-faq-01.doc Drummond ReedQC:\WINDOWS\Application Data\Microsoft\Word\AutoRecovery save of wd-xdi-faq-01.asd Drummond ReedQC:\WINDOWS\Application Data\Microsoft\Word\AutoRecovery save of wd-xdi-faq-01.asd Drummond Reed1D:\1-2003-Drummond\4-XDI-TC\FAQ\wd-xdi-faq-01.doc Drummond Reed1D:\1-2003-Drummond\4-XDI-TC\FAQ\wd-xdi-faq-01.doc Drummond Reed1D:\1-2003-Drummond\4-XDI-TC\FAQ\wd-xdi-faq-01.doc Drummond Reed1D:\1-2003-Drummond\4-XDI-TC\FAQ\wd-xdi-faq-01.doc Drummond Reed1D:\1-2003-Drummond\4-XDI-TC\FAQ\wd-xdi-faq-01.docʙ8uh+ChjZp)5Xk:i:q^`. 88^8`OJQJo( ^`OJQJo(hh^h`. hh^h`OJQJo(hh^h`o(.^`.pLp^p`L.@ @ ^@ `.^`.L^`L.^`.^`.PLP^P`L.^`OJPJQJ^Jo( ^`OJQJo(o pp^p`OJQJo( @ @ ^@ `OJQJo( ^`OJQJo(o ^`OJQJo( ^`OJQJo( ^`OJQJo(o PP^P`OJQJo()5k:iwD        ,         /78SX]^&34u_@ L t_@Unknown Drummond ReedDrummond Reed20040120T222928735F Drummond ReedG:Times New Roman5Symbol3& :Arial?5 :Courier New;Wingdings"1h2FƥF  N(L$p0ds` 2qXDI FAQ Drummond Reed Drummond Reed Oh+'0|  8 D P\dltXDI FAQDI Drummond Reedorumrum Normal.doteDrummond Reedo16mMicrosoft Word 9.0@;(@X@|' N ՜.+,D՜.+,4 hp|  AS(s` XDI FAQ Title 8@ _PID_HLINKSA^L*http://www.oasis-open.org/committees/xdi/(^!mailto:geoffrey.strongin@amd.comg"mailto:drummond.reed@cordance.net_http://www.istpa.org/75dhttp://www.oasis-open.org/apps/org/workgroup/xri/download.php/5109/xri-syntax-resolution-1.0-cd.pdfHL*http://www.oasis-open.org/committees/xri/.,khttp://www.oasis-open.org/apps/org/workgroup/xdi/download.php/5115/wd-xdi-intro-white-paper-2004-01-20.pdf2 _Toc624033322 _Toc624033312 _Toc624033303 _Toc624033293 _Toc624033283} _Toc624033273w _Toc624033263q _Toc624033253k _Toc624033243e _Toc624033233_ _Toc624033223Y _Toc624033213S _Toc624033200M _Toc624033190G _Toc624033180A _Toc624033170; _Toc6240331605 _Toc624033150/ _Toc624033140) _Toc624033130# _Toc624033120 _Toc624033110 _Toc624033101 _Toc624033091  _Toc62403308%m+http://xml.coverpages.org/dataSharing.html.,khttp://www.oasis-open.org/apps/org/workgroup/xdi/download.php/5115/wd-xdi-intro-white-paper-2004-01-20.pdf^L*http://www.oasis-open.org/committees/xdi/oaOAS  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~Root Entry FData O1Table2WordDocument)SummaryInformation(DocumentSummaryInformation8CompObjjObjectPool  FMicrosoft Word Document MSWordDocWord.Document.89q