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

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…

4 days ago

Reflecting on 2025: Building CVOYA’s Future with AI Coding Agents

As 2025 is now behind us, I wanted to share a few reflections from my…

2 months ago

DIY smart home accessory – It all started with a question to ChatGPT

Few months ago, we bought a sculpture from a local art fair for our Palm…

2 months ago

The Beginning of CVOYA

There’s a unique energy that comes with starting something new — a blend of excitement,…

4 months ago

Enhancements in Graph Model: Dynamic Entities & Full-Text Search

As I continued work on BrainExpanded and its MCP service, I came to realize that…

8 months ago

GraphModel: A .NET Abstraction for Graphs

Just over a month ago, I published "Playing with graphs and Neo4j". Back then, it…

8 months ago