1 / 31

Issue: Standardized Categorization, Partitioning, Collections,and Unique Identification

Issue: Standardized Categorization, Partitioning, Collections,and Unique Identification to support Discovery and Use through a Registry or Namespace or Namespace URI + filepath conventions. Names, IDs, Categorization, Classification.

kelsey-long
Download Presentation

Issue: Standardized Categorization, Partitioning, Collections,and Unique Identification

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. Issue: Standardized Categorization, Partitioning, Collections,and Unique Identification to support Discovery and Use through a Registry or Namespace or Namespace URI + filepath conventions

  2. Names, IDs, Categorization, Classification What goes here to support registry?? And web services??

  3. application service How does REA, UDEF, Catalog of BPC, and Catalog of CC support attaching metadata that provides business context, application context, hierarchy of collections, associations? Global Registry of Thangs Process Agreements UDDI Reg Agreements Service Collaboration ebxml Models Namespaces ebXML Reg Agreements Actors Resources Documentation Events Translation Dependencies Subscriptions

  4. Standardization of partitioning decisions by a Enterprise, Consortium, Standards Body, Community of Practice, or Domain

  5. Responsibility, Accountability, and Authority (RAA) Established to Govern Functioning of Business, Process, Data, and System Areas Business Business Business Business Area Area Area Area Owner Owner Owner Owner Process Process Process Data Data Process Data Data Owner Owner Owner Owner Owner Owner Owner Owner System System System Service Service Service System Service Owner Owner Owner Owner Owner Owner Owner Owner Partitioning of Business Supported by Taxonomies: ? Partitioning of Types of Ownership Supported by: ? Business - Transport Business Area Business Area Business Area Business Area Customer Supprt Supplier Mgmt Engineering Manufacturing

  6. DataOwner ServiceOwner ProcessOwner SystemOwner BusinessAreaOwner Domain Domain Content Owners Community of Practice Domain Registry DomainStewards Registrars Domain Repository Governing Artifacts (GAs) Established Which Provide Parameters toBusiness, Process, Data, and Systems Domain Domain Domain Content Owners Community of Practice Domain Content Owners Community of Practice Domain Registry Domain Registry DomainStewards Registrars DomainStewards Registrars Domain Repository Domain Repository Partitioning of Domains Supported by: ? The GAs have applicability to 1 or More Communities of Practitioners who have different focuses and who apply these in ways applicable to their focus.

  7. The Domain organizational mechanism allows the Community of Practitioners to establish Configuration Control over the Artifacts they create (their GAs). The Domain Stewardship mechanism also provides the dispute resolution processes to drive down interoperability into sub-domains and ensure interoperability across domains. Metamodel Methodology Methodology Business Process & Collaboration Modeling Interchange InformationModeling Libraries Libraries Patterns Patterns Rules Rules Models, Rules, Policies, Procedures Domain Sole AuthorityDesign Artifacts Domain Content Owners Community of Practice Domain Registry DomainStewards Registrars Domain Repository The Domain organizational mechanism is set up to give a Community of Practitioners the RAA to establish the Models, Rules, Policies, Procedures, and Sole AuthorityDesign Artifacts which will support Data Sharing and Interoperability as we move towards a eBusiness internet connectivity and websevices business applications model. Partitioning of Views Supported by: ?

  8. Registry Mirrors these Partitioning decisions via Collections & Associations

  9. Namespace Object Specific Metadata Business Consortia Stds Body domain Registry Specific Metadata Subscription Dependency SubmittingOrganization ExtrinsicObject Key to RegObj isOpaque mimeType Resource Package Collection of RegistryObjectids RegistryPackage Collection of RegistryObjectids Role RegistryUser Identity RegistryRecord RegistryEntry Metadata Expiration majorVersion minorVersion Stability = Dynamic, DynamicCompatible, Static Status = Submitted, Approved, Deprecated, Withdrawn userVersion Id RegistryObject MetadataobjectType = (see slide 5 for collections) Name Description accessControlPolicy Priviledge ExternalIdentifier Key to RegObj IdentificationScheme registryObject value • IntramuralAssociation • Key to RegObj • associationType = • RelatedTo • HasMember • ExternallyLInks • Contains • EquivalentTo • Extends • Implements • InstanceOf • Supersedes • Uses • Replaces • SubmitterOf • ResponsibleFor • sourceObject • TargetObject Ownership Slot Key to RegObj Name slotType Configuration Mgmt Registry Information Model (RIM) Collections Classification Association Information Asset serviceBinding Key to RegObj accessURI targetBinding Values Key to Slot Repository/External Link specificationLink specificationObject useageDescription usageParameters ExternalLink Key to RegObj Key to Organization externalURI 1..* 1..* 1..* 1..* 1..* Namespace Collection of RegistryObjectids domain Collection of RegistryObjectids nodeType UniqueCode EmbeddedPath NonUniqueCode 1..* 1..1 1..1 1..1 1..* ClassificationScheme TaxonomyID isInternal = T,F 0..* 1..* 0..* • Classification • classifiedObject = • Reg Obj ID • external • Classifcation Scheme id • nodeRepresentation • internal • classificationNode id 1..* ClassificationNode TaxonomyID code 1..* 0..* 0..* 0..* 0.* 1..1 1..* 0.* 1..1

  10. Service RegistryGuest Appl User Project Subscription Dependency Domain Namespace Namespace Classification UDEFREA CBPC Boeing Taxonomy Boeing Thesaurus AIA Taxonomy ATA Taxonomy Domain Taxonomy Translation domain Display Resources Conversion Resources Data Resources Events Resource Package RIDDL Input file address Output files Address XSLT XSL-FO Tables FOP Schema • How do I show this collection in the registry as an addressable thing so subscriptions, dependencies, and other association types can be tied to it? The Resource Package could map to RegistryPackage in RIM map • How do I register the pieces that make up this collection & associate them to a collection? How can I reuse pieces to make other similar collections? Collection members may be submitted together or independently and may be members of different packages • Is Translation a registryPackage? How is this accomplished in the Reg/Rep? What is Translation? It could mapto ExtrinsicObject • Are each one of the pieces of a Resource Package their own separate Registry Record? Do they have to be registered if the package is registered? Yes. Each is a RegistryObject/repository item and must be registered. • How do I identify this collection as being used by a domain or a namespace which did not create it? Use Content Cataloging • Does Slot have any purpose beyond support Service Parameter passing? Yes Slots are used for dynamic extensibility via arbitrary user-defined attribute

  11. Service ExtrinsicObject Slot 0.* Values specificationLink serviceBinding 1..* 1..1 ExternalLink RegistryGuest Appl User Project Subscription Dependency Domain Namespace Namespace Classification UDEFREA CBPC Boeing Taxonomy Boeing Thesaurus AIA Taxonomy ATA Taxonomy Domain Taxonomy Service domain Event Binding Port Address Resource Package WSDL Server Path Port Parameters Binding Server Address Path Documentation • How do I show that this service has been identified as being used domain which did not create it? Use ad hoc SQL or XML filter query • How do I show that this service is part of Registry Package including a WDSL, service agreements, & documentation? Add the WDSL etc. to the RegistryPackage. • Is the serviceBinding a separate Registry object into itself with its own RegistryRecord? Yes. • How do I show this as belonging to a Namespace Use Content cataloging and add namespaces as Slots • When are external object and extrinsic link used? • How are slot and Service Binding used with this type of collection? Slots may be added to any object in the package or the package itself. ServiceBinding may be included in the RegistryPackage as a member.

  12. Collaboration Service Transaction ExtrinsicObject XML Schemas Core Components Attribute Element ExternalLink RegistryGuest Appl User Project Subscription Dependency Domain Namespace Namespace Classification UDEFREA CBPC Boeing Taxonomy Boeing Thesaurus AIA Taxonomy ATA Taxonomy Domain Taxonomy domain Resource Package Info Model Event Event Specification Schemas Event Event BTP Worksheets CCP/A BCP BPSS TPA • How do I show this collection in the registry as an addressable thing so subscriptions, dependencies, and other association types can be tied to it? • How do I register the pieces that make up this collection & associate them to a collection? How do I put collections in collections? • Are each one of the pieces their own separate Registry Record? • How do I identify this collection as being used by a domain or a namespace which did not create it? • How do I reflect that the various pieces that make up the collaboration may have come from different Namespaces or been extended by my company? Namespaces may be a Slot or Classification. Can define “Extends” Assoc to what you extended from. • If someone want to search down to the element and attribute level can they find this information out? Use content cataloging and SQL and/or XML filter query. • When are external Link and Extrinsic Object used? • Does Slot have any purpose beyond support Service Parameter passing?

  13. Service ExtrinsicObject ExternalLink RegistryGuest Appl User Project Subscription Dependency Domain Namespace Namespace Classification UDEFREA CBPC Boeing Taxonomy Boeing Thesaurus AIA Taxonomy ATA Taxonomy Domain Taxonomy Domain Submitting Organization Resource Package Specifications Policies Procedures • How do I show this domain collection in the registry as an addressable thing so subscriptions, dependencies, and other association types can be tied to it? • How do I register the pieces that make up this domain & associate them to a domain? How do I put collections in collections? • Are each one of the pieces their own separate Registry Record? • How do I identify this collection or pieces of this collection as being used by a domain or a namespace which did not create it? • How do I reflect that the various pieces that make up the collaboration may have come from different Namespaces or been extended by my company? • Does Slot have any purpose beyond support Service Parameter passing? • When are External Link and Extrinsic Object used? Guidelines Best Practices Papers TechNotes Directions

  14. Service ExtrinsicObject ExternalLink RegistryGuest Appl User Project Subscription Dependency Domain Namespace Domain Classification UDEFREA CBPC Boeing Taxonomy Boeing Thesaurus AIA Taxonomy ATA Taxonomy Domain Taxonomy Namespace Submitting Organization Resource Package Specifications Policies Procedures • How do I show this namespace collection in the registry as an addressable thing so subscriptions, dependencies, and other association types can be tied to it? • How do I register the pieces that make up this namespace & associate them to a domain? How do I put namespaces in namespaces? • Are each one of the pieces belonging to the namespace their own separate Registry Record? • How do I identify this namespace as being used by a domain or a namespace which did not create it? • How do I reflect that the various pieces that make up the Namespaces may have come from different Namespaces or been extended by my company? • Does Slot have any purpose beyond support Service Parameter passing? • When are External Link and Extrinsic Object used? Guidelines Best Practices Papers TechNotes Directions

  15. Collaboration Service Transaction XML Schemas Core Components Attribute Element RegistryGuest Appl User Project Subscription Dependency Domain Namespace Namespace Classification UDEFREA CBPC Boeing Taxonomy Boeing Thesaurus AIA Taxonomy ATA Taxonomy Domain Taxonomy domain Event Resource Package Event Model Event Specification Schemas Event BTP Worksheets CCP/A BCP BPSS TPA • How do I show this collection in the registry as an addressable thing so subscriptions, dependencies, and other association types can be tied to it? • How do I register the pieces that make up this collection & associate them to a collection? How do I put collections in collections? • Are each one of the pieces their own separate Registry Record? • How do I identify this collection as being used by a domain or a namespace which did not create it? • How do I reflect that the various pieces that make up the collaboration may have come from different Namespaces or been extended by my company? • If someone want to search down to the element and attribute level can they find this information out? • Does Slot have any purpose beyond support Service Parameter passing?

  16. Service ExtrinsicObject ExternalIdentifier ExternalLink RegistryGuest Appl User Project Subscription Dependency Information Models ver Business Process Agreements Application Process Agreements UDDI Reg APIs ver ebXML Reg APIs ver Domains Namespaces Events Resource Package IntramuralAssociation sourceObject TargetObject Classification UDEFREA CBPC Boeing Taxonomy Boeing Thesaurus AIA Taxonomy ATA Taxonomy Domain Taxonomy domain Namespace • How do I register a dependency on a record as an addressable thing (domain, namespace, record, collection) in the registry so that I get notice? • How does a service or a conversion/translation or a collaboration register the list of events in registry they cause so that I can register a dependency on event and get notice when it occurs? Use V3 event notification feature. • How will these be categorized to guide selection of which one to subscribe to? • How do I the owner of this registered item find out who has registered a dependency on the things belonging to my domain? Use ad hoc SQL or XML filter query.

  17. Registry Mirrors these Partitioning decisions via Categorization

  18. Categorization- of Collaboration Components to State & Context CBPC? CCC? Collections? Where does Business Context fit? Business Context Collaboration Transaction Business Context Sequence Pattern Collection State Behavior Actors REA? Documents UDEF? Core Components Element Attribute

  19. ????????? PROCESS AREA Business Area - Plan procurement and supply of raw materials or finished product -Identify potential customer/ vendor - Provide catalog - Request pricing - Request availability - Negotiate contract - Provide purchase order -Agree delivery schedule - Acknowledge delivery notice - Query delivery status - Receive goods -Obtain payment Authorization - Make/Receive Payment - Discover delivery discrepancy - Return shipment - Negotiate/Receive allowance or payment from vendor -Plan design service offering and use of design services -Identify Vendor who can supply product design work -Identify potential customer -Request examples of prior design work - Submit Bid - Negotiate Contract -Make counter-offers - Send design contract - Receive designs - Inspect for conformance - Make payment -Receive payment -Discover discrepancy in agreed upon designs - Negotiate / receive allowance or payment from vendor - Identify places in company where new staff of contract labor is needed. -Plan agency offerings. -Plan student Intake -Identify personnel services provider -Identify training provider -Identify students - Request pricing - Request availability -Request/Provide course details - Negotiate Contract for worker recruitment or training. -Agree start dates -Register for course - Provide training materials -Interview candidates - Make / Receivepayment -Discover discrepancy in agreed upon personnel characteristics or training components - Receive allowance or payment from vendor. -Revise training material -Plan provision and use of transport resources. -Identify Vendors (like Fedex or UPS) -Identify potential customers - Request pricing - Request availability - Negotiate contract for logistics service - Receive logistics services -Provide shipping note -Provide dangerous goods note - Make / Receive payment -Discover discrepancy in agreed upon service and performance - Negotiate logistics allowances with carrier - Receive allowance or payment -Plan manufacturing requirements -Research market for outsourced manufacturing -Identify Provider of manufacturing services - Provide catalog - Request pricing - Request availability - Negotiate contract for Manufacturing -Agree production schedule -Agree quality standard -Send outsourced manufacturing inputs -Receive outsourced manufacturing outputs - Make / Receive payment Discover discrepancy in agreed upon quality levels - Negotiate allowance with vendor - Periodic evaluation - Research market needs -Plan the provision of Financial Services (Insurance, Credit, Investments) -Identify possible debt sources (banks, credit unions, etc.) - Identify financial institution with whom to purchase debt or equity financing -Identify Insurance providers -Identify potential investors -Negotiate terms of debt or terms of equity offering with capital provider -Agree Insurance terms - Accept transfer of debt instrument - make transfers of stock certificate - authorize and make payments & loans -Transfer funds -Pay Insurance Claims -Review offerings & compliance -Receive monetary adjustments -Plan and publicize regulatory requirements - Determine authorities to deal with for import/export -Identify relevant regulatory services to enable business to operate. -Identify appropriate Taxation authority and taxpayers -Agree time and place of inspection or other regulatory services -Negotiate payment of tax -Accept notice of inspections, taxing, or other regulatory services performed - Request export license - Clear goods -Pay tariffs -Make adjustments in services or payments based upon later information -Plan Service specialization and provision -Plan admissions -Register patient - Agree admission date - Decide treatment required -Prescribe treatment - Charge / Pay for treatment -Provide health statistics -Claim re-imbursement Planning Identification Negotiation Actualization Post-Actualization CBPC Procurement / Sales (Goods) Design Recruitment -and-Training Logistics Manufacturing Financial Services Regulation Health Care

  20. General Global Taxonomies Enterprise Specific Taxonomies Domain Specific Taxonomies Categorization & Associations of Registry Objects (Processing, Services Resources) to Global, Local, Domain Taxonomies and Ownership Ownership partitioning Focus/ User partitioning Where does UDEF fit on this? Why doesn’t ebXML Have a namespace And domain strategy For its work or for Registry content? Where is ebXML Registry?? Authoring partitioning Does Taxonomy strategy In CBPC support (discovery and comparison) handles to do web services and eBusiness? Domains AIA ATA OAG W3C W3C Application System Services Documentation Product Standards Body Consortium Enterprise Namespace MS IBM Sun W3C UDDIReg Behavior Partitioning ebXML REA UDEF Boeing AIA? ebXML CBPC CCC categorization Information Model ATA CSDD& AIM ebXML UMM

  21. Area of Search – requires categorization handles, collections, and associations Build Time Run Time Type of Search = Hunting Know what the Target is and have path where Target was last found. Type of Search = Harvesting Know the area where Target is generally Found. Bounded Sampling Type of Search = Browsing Don’t know if the target Exist or what Area it would be in But have idea of Characteristics. Unbounded Sampling

  22. Handles to target in on Registry Objects Collection Domain Collection Versioned Namespace Categorization UDEF REA CBPC Business Domain Business Process Category Business Process Area Business Process Collaboration Business Context Business ebXML defined Collections – artifacts and services defined by the BP and CC teams Organization Context Ownership Domain Events Associations

  23. Registry Mirrors these Partitioning decisions via Namespace Naming

  24. Domain Namespace – specialized collection of artifacts supporting Business Domain processing. Namespace ID 1M Doc V3 Agree V1 CT ID 3 Coll ID 1 Coll ID3 EG ID 1 IG 1 IG 2 Namespace ID 1Z Doc V3 Agree V1 WS ID 1 WS ID 2 CT ID 3 Coll ID3 EG ID 1 IG 1 IG 2 WebServices WS ID 1 WS ID 2 WS ID 3 Conversions Translations Documentation CT ID 1 CT ID 2 CT ID 3 Doc ID 1 Doc ID 2 Doc ID 3 Namespace ID 1A Doc V1 Agree V3 WS ID 1 CT ID 1 CT ID 2 CT ID 3 Coll ID1 EG ID 1 IG 1 IG 2 IG 3 Collaborations Agreements Coll ID 1 Coll ID 2 Coll ID 3 Agree ID 1 Agree ID 2 Agree ID 3 Internal Governances External Governances IG ID 1 IG ID 2 IG ID 3 EG ID 1 EG ID 2 EG ID 3 Application or Specification Namespace – specialized collection of artifacts supporting application processing to a specific specification or set of agreements.

  25. Cross Domain Namespace ID XX-1Z Doc yy-V3 Agree 77-V1 WS ID xx-1 WS ID zz-2 CT ID -zz3 Coll Id yy- 3 EG ID xx-1 IG ID xx-1 IG ID ss-2 Namespace - specialized collections Governances supporting application processing And under configuration control. Specifications, Info Models, worksheets, structures, services, Agreements, policies,……

  26. Namespace Naming Convention Proposal • Namespace URI:= BaseURI/SourceName/CMDate/SpecIDName • Namespace URI would be translated by a Namespace Resolver Service to translate • Down to a pointer to a registry interface to find resources or point down to a server. • Base URI:= (tbd)uncefact.org or uncefact.ebxml.org or ebxml.org or uncefact-oasis.org • Source Name:= (uncefact, (“/”,(UNBaseWG), “/”)| (oasis, (“/”, (OasisBaseWG), “/”) • UNBaseWG:= (TWG |ATG | Legal) • OasisBaseWG:= (MHS | RR | CPP) • CMdate:=yyyy-mm • SpecIDName:= (UnSubWGname | OasisSubTCname) • UNSubWGname:= (UMM, BPCMC, BPIMES, BRIM, BET, BCP, UEB, CBPC,…) • OasisSubTCname :=(tbd) • Unique ID:= Namespace URI + FilePath/FileName • A filepath and file name could lead to the location of resources. Or a Registry Object ID could allow discovery of the object from repository or provide URL to resource. • Namespace URI and “filepath and filename” are 2 distinct “thangs” which need XML mechanisms or registry mechanisms to help resolve to support discovery and use.

  27. W3C Example for definingNamespace URIsand File Share URL addressing

  28. Partitioning of the Work *Completed Base Domain W3C Domain Sub-Domains Architecture Domain Document Formats Domain Technology & Society Domain Interaction Domain Sub-Sub-Domains • DOM Activity • DOM WG • XML Activity • XML Query WG • XML Schema WG • XML Linking WG • XML Core WG • URI Activity • WebSrvs Activity • JigSaw Project • Graphics Activity • SVG WG • HTML Activity • XHTML • HTML WG • Xforms WG • I18N Activity • I18N WG • Math Activity • Math WG • Style Activity • CSS WG • XSL WG • Dev Independence Activity • CC/PP WG • Dev Independence WG • Multimdl Intractn Activity • Multimdl Intractn WG • Voice Browser Activity • Voice Browser WG • Synchronized Multimedia • SYMM WG* • Privacy Activity • P3P Specification • Patent Policy Activity • Patent Policy WG • Semantic Web Activity • RDF Core WG • Web Ontology WG • XML Encryption Activity • XML Encryption WG • XML Key Mgmt Activity • XML Key Mgmt WG • XML Signature Activity • XML-Signature WG Web Accessibility Initiative Quality Assurance TAG • WAI Technical Activity • Protocols & Format WG • User Agent Guidelines WG • Authoring Tools Guidelines WG • Web Content Accessibility Guidelines WG • Quality Assurance Activity • QA WG • Technical Architecture Group

  29. Site Map for Access to Domain Work Products W3C Site Index W3C Search W3C Subscription W3C homepage Public Member & Internal W3C Communication pages W3C Administration & Guidelines W3C About pages W3C WG Policies W3C Membership W3C WG Authoring Guideline pages W3C Subscription W3C Search W3C Site Index W3C Membership Guideline pages W3C Namespace Policies & Guidelines Architecture Domain web pages Public WG Webpages WIP WG Webpages Architecture Domain web pages Technology & Society Domain webpage Technology & Society Domain webpage Public WG Webpages WIP WG Webpages Document Formats Domain webpage Document Formats Domain webpage Public WG Webpages WIP WG Webpages TR web pages (REC, PR, CR, WD, Note) W3C Mailing Lists Internal WD Web pages Interaction Domain webpage Interaction Domain webpage Public WG Webpages WIP WG Webpages Web Accessibility Initiative webpage Web Accessibility Initiative webpage Public WG Webpages WIP WG Webpages Quality Assurance TAG webpage Quality Assurance TAG webpage Public WG Webpages WIP WG Webpages

  30. Namespace URI: • baseURI/CM-date/AssignedName Naming Convention for domain, Sub-domain And sub-sub-domain Namespaces • Base URI: • www.w3.org Configuration Management date on creation:yyyywith optional mm with optional dd • Assigned Name: • WG acronym for base specification name • With optional sub-specification name W3C Defined Namespaces http://www.w3.org/1998/Math//MathML http://www.w3.org/2001/SMIL20/ http://www.w3.org/2001/Xinclude/ http://www.w3.org/2001/xml-events/ http://www.w3.org/2001/XMLSchema/ http://www.w3.org/2001/02/xml-fragment/ http://www.w3.org/2001/04//xmlenc#/ http://www.w3.org/2001/10/xml-exc-c14n/ http://www.w3.org/2001/12/xforms/ http://www.w3.org/1999/02/22/rdf-syntax-ns#/ http://www.w3.org/1999/xhtml/ http://www.w3.org/1999/xlink/ http://www.w3.org/1999/XSL/Format http://www.w3.org/1999/XSL/Transform http://www.w3.org/2002/01/rdf-databases/db-ont-1#/ http://www.w3.org/2002/01/rdf-databases/rei-ont-1#/ http://www.w3.org/2002/03/xkms/ http://www.w3.org/2002/06/soap-encoding/ http://www.w3.org/2002/06/soap-envelope/ http://www.w3.org/2002/06/soap-faults/ http://www.w3.org/2002/06/soap-rpc/ http://www.w3.org/2002/06/xhtml2/ http://www.w3.org/2002/06/xmldsig-filter2/ http://www.w3.org/2000/svg/ http://www.w3.org/2000/xmlns/ http://www.w3.org/2000 /09/xmldsig#/ http://www.w3.org/2000 /10/xmldsig-p3p-profile/

  31. Naming Convention & Repository Hierarchy W3C Domain http://www.w3.org http://www.w3.org/Consortium/ The Architecture (sub) Domain http://www.w3.org/Architecture/ DOM http://www.w3.DOM/ http://www.w3.org/DOM/Activity/ http://www.w3.org/DOM/Group/ JIGSAW http://www.w3.org/Jigsaw/ XML: Structured Data Interchange http://www.w3.org/XML/Activity http://www.w3.org/XML/Group/Core http://www.w3.org/XML/Linking http://www.w3.org/XML/Group/Query http://www.w3.org/XML/Group/Schemas URI (Uniform Resource Identifiers) http://www.w3.org/Metadata/ http://www.w3.org/Addressing/ Web Services http://www.w3.org/2002/ws/[Activity*] http://www.w3.org/2002/ws/cg/ http://www.w3.org/2002/ws/desc/ http://www.w3.org/2000/xp/Group/ http://www.w3.org/2002/ws/arch/ Domain Page http://www.w3.org/DomainName Working Documents http://lists.w3.org/Archives/Public/GroupDirName Public Page http://www.w3.org/GroupName/Sub-Group-Name Status-What’s New Page http://www.w3.org/GroupName/Activity Working Group Page http://www.w3.org/GroupName/Group/

More Related