Hallam-Baker, Phillip wrote:
I don't know why that would be the case. I wrote the first draft of what
became the SAML assertion infrastructure before Microsoft wrote the first
draft of SOAP.
WS-* is certainly tied down to the Web Services framework. That is a
different design decision that has advanatges and disadvantages. WS-* is
architected as an active transport layer protocol, SAML is architected as
static data.
The advantage of the static mode is precisely that you are not tied to
transport unless you want to be.
REST is just a protocol architecture style. Fielding has a different
architectural style to Fristyk-Neilsen or Hallam-Baker. I don't see why the
idea of giving his style an acronym makes it more valid than any other or
creates an incompatibility. He sees an adantage to keeping to one consistent
style that he adopted in 1995 or so. Folk who care about these things can
probably see quite a lot of change in my style over the years. There is a
case to be made for both approaches.
so I admit that I am confused and probably out of my depth, and I know
better than to argue with the initial spec author that it can't be done.
but I simply don't understand what it means to use SAML with something
like atompub
http://www.ietf.org/internet-drafts/draft-ietf-atompub-protocol-08.txt
or any of the plethora of so-called REST based web services.
Here is an ATOM post.
POST /myblog/entries HTTP/1.1
Host: example.org
User-Agent: Thingio/1.0
Content-Type: application/atom+xml
Content-Length: nnn
<entry xmlns="http://www.w3.org/2005/Atom";>
<title>Atom-Powered Robots Run Amok</title>
<id>urn:uuid:1225c695-cfb8-4ebb-aaaa-80da344efa6a</id>
<updated>2003-12-13T18:30:02Z</updated>
<content>Some text.</content>
</entry>
Where does the SAML go? I apologize for my lack of understanding here.
Rob
_______________________________________________
dix mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/dix
