Hi Paul, Thanks for the update! On 2014-03-06 14:14, Paul Millar wrote:> Hi all,

Here's an updated version of the proposal:

---

A service that supports HTTP or any extension based on HTTP MAY publish StorageAccessProtocol objects to represent this.

If a StorageAccessProtocol object is published to represent HTTP access then the Type SHOULD|MUST be 'http'.

If a StorageAccessProtocol object is published to represent WebDAV access then the Type SHOULD|MUST be 'webdav'.

I think in the two above I'd prefer MUST, because I don't see why one would publish something else. But you surely have more use cases in mind than me, so SHOULD is fine as well.

When publishing an Endpoint that supports HTTP (or any extension based on HTTP) without encryption then the URL SHOULD start 'http://'.

If an Endpoint the endpoint supports HTTP (or any extension based on HTTP) with SSL or TLS encryption then the URL SHOULD start 'https://'

Also here I don't see why such a precise description ends up asa SHOULD but is fine. Maybe SSL or TLS might change URL scheme, who knows? Doesn't depend on us.

If the endpoint supports WebDAV then an InterfaceExtension of 'http://www.ietf.org/rfc/rfc4918.txt' SHOULD be published.

sounds very good to me.

---

Is this any better?

Yes :) I'll add it to my list of good practices in GLUE2 Cheers, Florido-- ================================================== Florido Paganelli ARC Middleware Developer - NorduGrid Collaboration System Administrator Lund University Department of Physics Division of Particle Physics BOX118 221 00 Lund Office Location: Fysikum, Hus B, Rum B313 Office Tel: 046-2220272 Email: florido.paganelli@REMOVE_THIShep.lu.se Homepage: http://www.hep.lu.se/staff/paganelli ==================================================