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

The Beginning of CVOYA

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

3 weeks 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…

4 months ago

GraphModel: A .NET Abstraction for Graphs

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

5 months ago

Playing with graphs and neo4j

After my initial implementation of some BrainExpanded-related ideas on top of dgraph using its GraphQL…

6 months ago

A Graph Model DSL

Say hello to the Graph Model Domain Specific Language (GMDSL), created with the help of…

6 months ago

BrainExpanded – Web app and Data Sources

As I wrote in previous posts, the manual recording of memories for BrainExpanded is just…

7 months ago