1. IBM Software Group ® WSRP-UDDI Straw Man Richard Jacob WSRP-PFB SC

2. IBM Software Group | WebSphere software Publishing Producers – basic ideas  Publish WSRP Producer as a businessService  Categorize this businessService as being of type WSRP-Producer  Use simple approach to publish the URL of service-WSDL and then use the service’s DescriptionInterface for further discovery  At the beginning use an approach as simple as possible, perhaps with minimum amount of tModels and other structures needed.  Proposal should allow easy extension to the UDDI-WSDL documents

3. IBM Software Group | WebSphere software Publishing Producers – approach 1 Unchecked Categorization KeyValues would be Producer or Portlet, later might be even PortletApplication..tModelKey=… Type: wsdlSpec To indicate it implements the wsrp wsdl tModelKey=… keyName=“WSRP Type” keyValue=“Producer” Producer

4. IBM Software Group | WebSphere software Publishing Portlets – basic ideas  Publish Portlet as a businessService  Categorize this businessService as being of type WSRP Portlet  Need to publish the Portlet handle somehow  Need to reference the Producer the Portlet belongs to  This could be done in two ways: Either pointer to the Producer’s wsdl Or reference within the directory to the Producer entity (seems better to me)  Try to keep it as simple as possible with minimum amount of tModels and other structures needed

5. IBM Software Group | WebSphere software Publishing Portlets – approach 1 Unchecked Categorization KeyValues would be Producer or Portlet, later might be even PortletApplication tModelKey=… keyName=“WSRP Type” keyValue=“Portlet” tModelKey=… keyName=“WSRP Producer Ref” kevValue=“Producer Business Service Key” Portlet Unchecked Categorization KeyValues would be the Producer’s businessService Key Note: same tModel as used for Producer categorization

6. IBM Software Group | WebSphere software Approach 1 – summary/questions/…  3 tModels used in total  No redundant information about wsdl, just stored on the producer entity (seems to be natural), Portlets refer to Producer  WSRP Type tModel  Is it sufficient for searching WSRP Producer/Portlets?  Could it be a checked categorization allowing only distinct values?  Producer’s bindingTemplate  tModelInstanceKey references the wsrp-wsdl tModel to indicate a wsrp impl  Do we need this if we have the categorization WSRP Type tModel?  It could be defined as UDDI-tn-v2, Appendix a (external wsdl documents) Here UDDI defines a WSDL Address tModel to indicate the accessPoint is not an actual access point but the service wsdl URL, do we need that? Contradiction to UDDI-WSDL proposals (v1 and v2) −We would have one tModel for the WSRP wsdl (containing 4 bindings/portTypes) −While UDDI defines that for each binding/porttype there should be one tModel… −Also UDDI says there must be one bindingTemplate for each portType used (don’t see really why in this case)  Producer Reference tModel  How easy is it to find the businessService entity in UDDI the Portlet businessService is pointing to?  Better ways to add such a reference?  This model could be easily extended to the WSDL-UDDI best practices/technical note proposals

7. IBM Software Group ® Approach 2 As discussed in calls/list

8. IBM Software Group | WebSphere software Publishing Producers – Approach 2 This tModel indicates that this businessService is a WSRP Producer tModelKey=… tModelKey=… Type: wsdlSpec To indicate it implements the V1 wsrp wsdl … Producer

9. IBM Software Group | WebSphere software Publishing Portlets (optional) – Approach 2 tModelKey=… tModelKey=… keyName=“WSRP Producer Ref” kevValue=“Producer Business Service Key” Portlet Unchecked Categorization KeyValues would be the Producer’s businessService Key Allows to find Producer in Registry This tModel indicates that this businessService is a WSRP Portlet

10. IBM Software Group | WebSphere software Approach 2 – data structures Producer’s businessService Example Producer Producer description see next page  may contain multiple name values (at least one), each accompanied with a unique xml:lang value (required)  May contain multiple description values, each adorned with a unique xml:lang value (optional)  Contains at a minimum one binding template holding the access point to the service wsdl (required)

11. IBM Software Group | WebSphere software Approach 2 – data structures Producer’s wsdl address bindingTemplate Binding description http://url-to-your-service-wsdl.wsdl tModelKey=“key of wsrp_v1_bindings.wsdl tModel” tModelKey=“key of WSRP Producer tModel”  May contain multiple description values, each adorned with a unique xml:lang value (optional)  accessPoint holds URL of service WSDL (required)  References two tModels  Wsrp_v1_bindings.wsdl to indicate that producer implements V1 of WSRP (required)  WSRP Producer tModel to point out the businessService is a WSRP Producer (required)

12. IBM Software Group | WebSphere software Approach 2 – data structures Portlet’s businessService Example Portlet Portlet description see next page <keyedReferencetModelKey=“WSRP Producer Service Reference tModel’s key” keyName=“WSRP Producer Service Reference” keyValue=“Producer’s businessService key” />  may contain multiple name values (at least one), each accompanied with a unique xml:lang value (required), we may want to define a mapping to PortletDescription.title?  May contain multiple description values, each adorned with a unique xml:lang value (optional), we may want to define a mapping to PortletDescription.Description  Contains at a minimum one binding template where the accessPoint holds the Portlet handle (required)  categoryBag holds reference to the businessService entity of the Producer, thus allowing to find out the wsdl location of the producer

13. IBM Software Group | WebSphere software Approach 2 – data structures Portlet’s wsdl address bindingTemplate Binding description portlet_handle_comes_in_here tModelKey=“key of WSRP Portlet tModel”  May contain multiple description values, each adorned with a unique xml:lang value (optional)  accessPoint holds URL of service WSDL (required)  References one tModel  WSRP Portlet tModel to point out the businessService is a WSRP Portlet (required)

14. IBM Software Group | WebSphere software Approach 2 – data structures WSRP v1 bindings wsdl tModel urn:oasis:names:tc:wsrp:v1:bindings The WSRP V1 WSDL containing the bindings WSDL source document. http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_v1_bindings.wsdl <keyedReference tModelKey="uuid:C1ACF26D-9672-4404-9D70-39B756E62AB4" keyName="uddi-org:types" keyValue="wsdlSpec"/>  Name is a uri to wsrp namespace (required)  May contain multiple description values, each adorned with a unique xml:lang value (optional)  overviewURL points to our V1 bindings wsdl (required)  References one tModel  UDDI types tModel indicating that this technical fingerprint is expressed by WSDL  Published once by the WSRP TC (in public UDDI case)

15. IBM Software Group | WebSphere software Approach 2 – data structures WSRP Producer tModel urn:oasis:names:tc:wsrp:v1:producer The WSRP V1 Producer Description of that tModel. URL to the WSRP-UDDI document we will produce  Name is a uri to wsrp namespace (required)  May contain multiple description values, each adorned with a unique xml:lang value (optional)  overviewURL points to our WSRP-UDDI document (optional)  Published once by the WSRP TC (in public UDDI case)

16. IBM Software Group | WebSphere software Approach 2 – data structures WSRP Portlet tModel urn:oasis:names:tc:wsrp:v1:portlet The WSRP V1 Portlet Description of that tModel. URL to the WSRP-UDDI document we will produce  Name is a uri to wsrp namespace (required)  May contain multiple description values, each adorned with a unique xml:lang value (optional)  overviewURL points to our WSRP-UDDI document (optional)  Published once by the WSRP TC (in public UDDI case)

17. IBM Software Group | WebSphere software Approach 2 – data structures WSRP Producer Reference tModel urn:oasis:names:tc:wsrp:v1:producer reference Reference to the Producer’s businessService key Description of that tModel. URL to the WSRP-UDDI document we will produce <keyedReference tModelKey="uuid:c1acf26d-9672-4404-9d70-39b756e62ab4" keyValue="unchecked"/> <keyedReference tModelKey="uuid:c1acf26d-9672-4404-9d70-39b756e62ab4" keyValue="categorization"/>  Name is a uri to wsrp namespace (required)  May contain multiple description values, each adorned with a unique xml:lang value (optional)  overviewURL points to our WSRP-UDDI document (optional)  References two tModels  UDDI categorization tModel indicating that this tModel is a categorization tModel  UDDI unchecked tModel indicating the that the values are not being checked  Published once by the WSRP TC (in public UDDI case)