//Developing a standard for naming web services within the enterprise

Developing a standard for naming web services within the enterprise

Sometimes, the first person to speak up, and point out a problem, gets to be involved in solving it.  I find that cool.  (Call me crazy).

Last year, I decided to try to get various folks within Microsoft IT to discuss a naming standard for web services that could be used across the enterprise.  My attempt didn’t get a lot of notice, and fell pretty silent.  However, the issue woke up recently now that we have web services that are starting to deploy, in production, across the enterprise.  Folks want their namespaces to be right, because changing the namespace later often means that the client app has to be recompiled (or someone gets to edit the WSDL file).

So, traction is starting to develop.  I am hopeful.  I’ll post progress here…

By |2005-08-03T03:43:00+00:00August 3rd, 2005|Enterprise Architecture|1 Comment

About the Author:

President of Vanguard EA, an Enterprise Architecture consulting firm in Seattle focused on the Pacific coast of the US. Nick has over 30 years of professional experience in management, systems, and technology. He is the co-author of the influential paper "Perspectives on Enterprise Architecture" with Dr. Brian Cameron that effectively defined modern Enterprise Architecture practices, and he is frequent speaker at public gatherings on Enterprise Architecture and related topics. He coauthored a book on Visual Storytelling with Martin Sykes and Mark West titled "Stories That Move Mountains".

One Comment

  1. Sean Chase August 3, 2005 at 12:33 pm - Reply

    I’d also be interested in reading about other people’s experience with this process from an iterative standpoint. Basically learnings from initial design ideas to the actual implementation of naming ASMX files to adopting namespaces. Very cool post!

Leave A Comment

17 − 13 =