WS-RF is having problems with the resource identity issue as well

There has been a lot of buzz lately about WS-Addressing ERPs, the reference parameters, and how resources should be identified. Jim wrote about it a couple of days ago. I agree with Jim. I too was against reference properties/parameters but in favour of WS-Addressing (btw… this was and is my personal view and not my current or previous employer’s!!!).

Since the discussions in the WebArch TAG mention WSRF, I think it’s appropriate to remind everyone that WS-Resource specification is at its second public review stage. If you have any issues with WSRF, now it’s time to speak 🙂

Thanks to Mark McKeown for the link to the public review spec

Recent Posts

CVOYA Graph v1.0 is out

Last week, I wrote about the evolution of the CVOYA Graph. After a lot of…

3 weeks ago

CVOYA Graph – Evolution

Last year, I released the "Graph Model" library for .NET as an open source project. It…

3 weeks ago

The boat is in the water: Spring Voyage is open source

Today I'm pushing Spring Voyage out of the harbor. You can track its journey on…

2 months ago

My Coding Agent Needed Its Own GitHub Identity

In my last post, I wrote that "the typing of code was parallelized and delegated.…

4 months ago

Rebuilding My AI Team in Twelve Days — And Why

In February, I wrote about the small team I'd stood up instead of hiring humans:…

4 months ago

How I Built My Own Team of AI Developers

Assembling a dream team without a single hire I've been making great progress on CVOYA's…

6 months ago