Shibboleth Developers

["Cantor, Scott E." <>]

On 4/13/11 6:46 PM, "Tom Scavo" 
<>
 wrote:
>The <md:ServiceDescription> element in metadata gives a *short*
>description (say, a paragraph) of the service. If the service provider
>needs to elaborate on that description, the optional
><mdui:InformationURL> extension element may be used to point to a web
>page with more detailed information.

Sure. But there are some axioms that I'm pretty strongly a believer of:

- most users won't read anything
- most users definitely won't read more than a simple short paragraph
- most users definitely won't read external documents

So I remain of the belief that the best way to explain what you need the
data for is in a short elevator speech in ServiceDescription, and anything
longer will go over heads anyway.

That's just my outlook.

>On the other hand, the
><mdui:PrivacyStatementURL> element contains a pointer to the SP
>Privacy Policy document. Content creators will appreciate the ability
>to create separate documents for these purposes. (Think about how the
>Privacy Policy is exposed on a typical web site.)

Think about how much they get read too. I have no doubt content creators
will appreciate the separation, but I think users won't.

But syntactically I just want to make sure people know what's reasonable
to put where and acknowledge the areas that aren't extensible right now
and the implications of fixing that.

-- Scott