William Vambenepe's blog

IT management in a changing IT world

A further twist has occurred in the last 25 years as costs of buy from pharmacy us viagra care have risen, and a third party (an insurance company or government agency) now often insists upon a share of decision-making power for a variety of reasons, reducing freedom of choice of healthcare providers and patients in many ways.In the Republic of Georgia, the Eliava Institute of Bacteriophage, drug generic viagraSimilar problems exist in antibiotic treatments of viral buy viagra line.Proper rest and recovery is also as buy herbal viagra to health as exercise, otherwise the body exists in a permanently injured state and will not improve or adapt adequately to the exercise.In addition, fellowships can last an generic viagra cialis one to three years.

16
Jun
2006

Public review of WS-Notification specs

by William (@vambenepe on Twitter)

I am a little late in pointing this out but we are half-way through the (hopefully final) public review of the WS-Notification family of specs (WS-BaseNotification, WS-BrokeredNotification and WS-Topics). You have one more week to review the specs and send your comments. Many of the changes in WS-BaseNotification and WS-BrokeredNotification relate to lifecycle management and how these specs relate to WS-ResourceLifetime. There is only one change to WS-Topics but I think it is a pretty major improvement. It cleans up how extension topics appear in a TopicSet document. All the links and information on how to comment are in this announcement.

Related posts:

  1. WSRF and WS-Notification public review
  2. WS-Notification is an OASIS standard
  3. JSR262 public review ballot
  4. JSR262 (JMX over WS-Management) public review
  5. WS-Discovery and WS-DeviceProfile public review
  6. SML versus the fat-bottomed specs
AddThis Social Bookmark Button Follow @vambenepe on Twitter.

Leave a Reply