{"id":123,"date":"2005-06-08T01:43:13","date_gmt":"2005-06-08T01:43:13","guid":{"rendered":"\/?p=123"},"modified":"-0001-11-30T00:00:00","modified_gmt":"-0001-11-30T04:00:00","slug":"microstandards-unravelling-ws-policy","status":"publish","type":"post","link":"https:\/\/www.identityblog.com\/?p=123","title":{"rendered":"Microstandards – unravelling WS-Policy"},"content":{"rendered":"

\"AI've been trying to explain my thinking about Microstandards<\/strong>. I see these as being standards objects<\/strong> that can be combined and specialized to define complex distributed systems. I thought I might help others understand what I'm saying by picking an example and discussing it.<\/p>\n

So I rolled the dice and came up with WS-Policy<\/a>. Let's start by getting a feel for the scope of this thing.<\/p>\n

I count the authors. Three from VeriSign, two from Sonic Software, five from IBM, six from Microsoft, one from BEA and one from SAP. Yikes – that makes eighteen.<\/p>\n

But it is twenty-two pages long, of which six are introduction, table of contents, nomenclature, abstract, references, and all the associated formalities. Another nine pages are essentially examples (can there ever be too many examples?) Which leaves seven pages of discursive specification.<\/p>\n

<\/p>\n

The specification defines the following:<\/p>\n