ext Andrew Newton wrote:
> Beyond the discussion of super and subclasses, how does this actually
> affect code? Is there some processing decision you will make about a
> presence-auth-policy vs geopriv-auth-policy based on the MIME type?
> And if so, why can't you make the decision based on the XML namespace?
IFF that identification is always straight forward with namespaces, then
that will work just as well, in code.
> In my opinion, application/auth-policy+xml is already going too far so
> I don't see a need for applicaton/presence-auth-policy+xml or
> applicaton/geopriv-auth-policy+xml.
I was thinking more of use cases where advertising of specific using
protocol policy document support using something like Accept in HTTP/SIP
is needed. In those cases, having a MIME type per using protocol is
beneficial.
Cheers,
Aki
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www1.ietf.org/mailman/listinfo/geopriv
Received on Tue, 21 Feb 2006 13:51:43 +0200
This archive was generated by hypermail 2.1.8 : Tue Feb 21 2006 - 09:55:40 EST