1. Requirements for Standardization on the Service Registries ISO/IEC JTC1 SC32 2015/10/161 A comment to WSSG, JTC1 SC32WG2 N1209 2008.11.10

2. SC32 perspectives to the registry Standardization SC32 recognize that there are so many different registry or metadata standard activities in both ISO or outside of ISO. To clarify requirements to the Service Registry standards, A taxonomy of registry type should be investigated in the discussion of the those standardizations. 2015/10/162

3. OAGIS Registry or Metadata related Standard Activities UN/CEFACT OMG ISO TC 37 ISO TC 204 Metadata or Registry Standards OASIS Intelligent Transportation Systems ISO/IEC 11179 MDR ISO/IEC19763 MFI UDDI.org W3C TC154 E-Commerce metadata XML, WSA,WSDL, SOAP Terminology UDDI SQL Catalog ISO TC 215 Health Informatics ISO TC127 Earth Moving machine ebXML RIM, RS SAML UBL Dublin Core ISO TC 46 Library metadata ISO TC211 Geographical data HL7 ISO/IEC JTC1 SC36 Topic map ebXML MOF, CWM, ODM ISO TC184 PLIB, CDD GS1 CCTS, UMM, UCM SIL, Products Catalog NATO ECCMA ISO8000 Learning Metadata ISO/IEC JTC1 SC32 ISO/IEC JTC1 SC34 EPC-G Rosseta Net 2015/10/163

4. An Idea for Taxonomy of Registry Types 4 Domain Specialty Diversity of Stakeholder Type-1 ProcessContents Type-3 Among Experts High (Narrow) Type-2 Cross Industries (BtoB) Metadata Dependent (Non Structural) Model Dependent (Structural) Low (Generic) High Target of the Standardizations System of Systems Registry Of Registries Cross Individuals 10 2 10 8 Service registry 2015/10/16

5. Type-1 Registry Dedicated Registries for specialized closed domains such as Space & Air, Defense, Automobile or Medical industries to support high skilled engineer/experts like SOSE (System of Systems Engineering) Sharing models and process by domain experts. Registry User: limited experts. Example: – TC184: ISO13584 (IEC 60130 ) : Parts Library – TC184: ISO 22745 OTD ( Open Technical Dictionary ) – TC184: ISO29002: Concept dictionaries — Resolution services 2015/10/165

6. Registries to support cross industries B to B business information sharing in the e-business such as the Supply Chain or Traceability. ebXML RIM & RS is a typical standard in this type. But, different registry standards or non standardized registries were implemented in each industry domains (Heterogeneous Registries) Registry User: various different business domain experts ROR (Registry of Registries) standard might be needed Type-2 Registry 2015/10/166

7. ROR(Registry Of Registries) concept Heterogeneous RegistriesRegistry Interoperation Registry ROR ManufacturingLogisticRetails Registry ROR: Registry of Registry SC32 Seoul 020506 4 PDES/STEP Registry Manufacturing ebXML Registry UDDI Component Registry GCI Registry EAN Registry CPFR Registry RosettaNet Registry Business Negotiation Vender Catalog Shipper Catalog Business Category Shipping Customer Support Consumer Profile CALS Production Planning & Procurement System Development 11179 Registry The UDDI 3.0 specification is addressing this ROR concept as Multi-Registries Environment featuring Root & Affiliate registries. ISO/IEC 19763 (MFI: Metamodel Framework for Interoperability) in SC32 is also addressing the ROR concept. 2015/10/167

8. Registry for discovery of services and orchestration of services. the UDDI is typical registry in this type. Registry User: Unlimited Problems: – Who should be responsible in the contents maintenance – How to segregate from Google or Yahoo Type-3 Registry 2015/10/168

9. Comparison of Registry Types Registry TypeType-1Type-2Type-3 Typical Example PLIB Registry ebXML RIM & RS UDDI Purpose of Registry Integration of products in a specific industry Cross Industries information interchange (BtoB) Discovery of Service Major Contents Models & Products Specification Process & Regulations Metadata Business Information (MSG) Metadata Definitions of Service URL/IRI Access Protocols Maintenance Responsibility Covered by Integrator Agencies Covered by Agency in each industries ?? Diversity of Stakeholder 10 2 10 3~4 10 8~9 Problems to be Considered MDA/SOC capability Complexity of contents Inharmonic registries ROR needed Justification of registering 2015/10/169

10. Risk at Type-2 & Type-3 Concentration of Maintenance efforts Concentration of RA(Registration Authority ） Difficulty on the tracking changes or versions Difficulty on assurance of ID or URI persistency Small returns on the registration efforts at users How to differentiate from Google or Yahoo Summary of comparison 2015/10/1610 Needs for standards of registry content definitions that enable Automatic Syndication without any central maintenances.

11. 11 An Image for Automatic Syndication of Service Definitions Web service Saas Web Service Saas SD 2015/10/16 RaaS SD Saas SD Saas SD SD: Service Definition RaaS RaaS: Registry as a Service

12. SC32 Perspective SOAP/REST WSDL UDDI-X Automatic Syndication Service Definition Registration Metadata /model Registration Ontology Registration Service Registries Scope of SC32 2015/10/1612 ROR

13. Recommendations for WSSG The Service Registry should be considered as a type of the registries It should be investigated that Registry Standards for type-2 still needed to ensure the integrity and the security in Business domains (BtoB) or not. To promote standardization by the PAS procedure at this area, it is needed to organize and coordinate SDOs in both ISO & Industrial consortia more widely. SC32 initiated study projects on ROR and Metamodel for Service Definition, then,SC32 appreciates to share study results with the WSSG. 2015/10/1613