Massive kudos to the
for agreeing to
drop reference properties
This addresses the most
I had with the specification, and leaves EPRs as a means for bundling a URI
with some state; cookies meet XML, as it were.
This decision means that a by-the-book EPR will contain only a single resource-identifying
data element; a URI. In other words, the WG is adopting the
constraint of a
single resource-identifying data element.
More concretely, it means that Web services will actually be encouraging
the use of URIs for identifying things, rather than the old practice of
using them as
behind which countless resources were hidden. This is HUGE,
because in my experience, once you’ve adopted URIs, the use of http URIs and therefore HTTP
(buh bye protocol independence) just naturally follow due to the massive
network effects of the Web. The use of
“hypermedia as the engine of application state”
is the next obvious constraint for adoption after that.
It’s possible that with this decision, Web services might have just stepped inside the Web’s
“So any signs that “tag spam” has started yet?” Yup, I spotted one last October, IIRC – a single posting with a bazillion tags. Reported it, and it was removed. Haven’t seen it since.
Egads, I didn’t think I was that nerdy;
It probably has a lot to do with my uncanny ability to recall
the periodic table.
That’s my story, and I’m sticking to it.
Update; I may be a nerd, but at least I’m not (too) weird;
Of all the weird test takers:
91% are more weird,
5% are just as weird, and
4% are more normal than you!
Since when was layer 6 the application layer? Sarvega/DataPower (and Web services infrastructure general) are one layer too low. Cisco should be looking at KnowNow
I forgot to send a pointer to a presentation I gave at last weeks
face-to-face. It’s titled
Media Types and Compound Documents.
“As a language of contracts, SOA involves complex shapes. But as a Lego system, it’s about simple shapes. Where’s the sweet spot?” Erm, simple shapes? 8-)
“Greasemonkey is a Firefox extension which lets you to add bits of DHTML to any webpage to change it’s behavior” – Wow.
Problems using email addresses with a “.name” TLD. An interesting aspect of email architecture that I wasn’t familiar with.