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
3 responses to “WS-RF is having problems with the resource identity issue as well”
Hello, Savas!
I understand and agree with your resistence to ref properties/parameters (however, it seems you lost that one looking at the candidate WS-Addressing specs) 😉
Wasn’t one of the goals of your White Dwarfs project to build a WSRF-compliant application? When you spoke at eScience you skipped over any evaluation of those specs and their viability (and rightly so: the crowd was getting sleepy).
You haven’t posted much on WSRF since last year; have your thoughts remained the same?
Hey Robert,
Indeed, i did loose that battle at the WS-Addressing WG 🙁
The point of the WhiteDwarfs application was not to build a WSRF-compliant application. Not at all. At the time we wanted to demonstrate that we didn’t need any special or new infrastructure in order build interesting eScience/Grid applications which meant no WSRF, no OGSI, just plain, simple WS specs.
My thoughts on WSRF remain the same. It’s just that I have said what had to be said. WSRF is ready to be standardised now. Time will tell whether it’ll be successful or not.
.savas.
Thanks, Savas – I guess I too was getting sleepy at your talk 😉