OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

soa-tel message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: UDDI: Service Location with SLA or Latency Parameters


Title: RE: UDDI: Service Location with SLA or Latency Parameters

Hi all,

I did some investigation with some internal UDDI folks and it looks as if it might be advantageous to look at the "accessPoint" in section 3.5.2.1 of the current UDDI specification, http://uddi.org/pubs/uddi_v3.htm#_Ref8977716 as this is part of the tModel, section 1.6.4, structure it might be an advantageous place to define new types related to real time performance, latency and other communications related selection criteria, and Appendix B of the specification outlines how to add a new type. The accessPoint is also part of the "bindingTemplate" which is used to describe various technical aspects of a service offered to the user communities.

<<UDDI_tModel.gif>> <<UDDI_bindingTemplate.gif>>
So, we could define a communications related tModel/bindingTemplate that can be then used to reference these specific communications related behaviours.

Let me know if this makes sense as this does appear on the SOA-Tel charter.

Regards John
_____________________________________________
From:   Storrie, John (MOP:MS024) 
Sent:   17 June 2009 07:09
To:     soa-tel@lists.oasis-open.org
Subject:        UDDI: Service Location with SLA or Latency Parameters

Hi all,

I was looking at the charter and one area that I thought would be of interest for a use case would be the ability for a query to include communications related attributes such as latency, service level agreements or real time performance.

Not being a huge UDDI expert I was wondering if there is some one in the team who would be able to quickly scan the UDDI query API to see if in the Tmodel or other area there is some attribute that would be related to a communication service behaviour?

My first scan seems to indicate that this is not there explicitly.

Any assistance most welcome.

Regards John

UDDI_tModel.gif

UDDI_bindingTemplate.gif



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]