(Sorry for the repost, if this is one. I sent to the old Shib users list email by mistake.)<div><br></div><div><div>It may be that we are the only ones using our SP in this way (described below). I some questions about the <mdui:DisplayName>. I hope the questions are broadly relevant.</div>
<div><br></div><div>We use ApplicationOverrides to have the SP treat different Apache VirtualHosts differently. We don't use multiple SP's. We sell hosting services to different customers using the same SP and the ApplicationOverride takes care of making each customer's service look like their own service, and no one else's.</div>
<div><br></div><div>My concern is that newly required MDUI element "DisplayName" does not make sense in the above described context. Examples of what I mean:</div><div><br></div><div> - Customer "Bigstate University" has our service hosted on "<a href="http://moodle.bigstate.edu">moodle.bigstate.edu</a>". Their app override reflects this, and reflects their IdP. But in-house, to their students, they call our service "Bigschool Online" and make no mention of Moodle or of our branded product, and any student who saw either term mentioned would probably not know what it was.</div>
<div> - Customer, "Littleschool Elementary" uses our service hosted on "<a href="http://littleschool.mrooms.net">littleschool.mrooms.net</a>". Our service is known by its branded name to their students (which is "joule(TM)"), and any student that saw that brand mentioned would know what it was.</div>
<div> - Customer, "Townsville School System" uses our service on "<a href="http://moodle.townsville.edu">moodle.townsville.edu</a>". They, however, just use the generic name "Moodle", and their students don't know what our branded product is at all.</div>
<div><br></div><div>(These are made-up examples that very closely describe real world data.)</div><div><br></div><div>Questions:</div><div> - Since the InCommon SP metadata now requires this field (<mdui:DisplayName>), is there a way to override it on a per-app basis?</div>
<div> - Or should I just fill it in as generically as possible?</div><div> - Or should I not even worry about it at all, since the app is never going to use this data anyway?</div><div> - Or should I not even worry about it at all, since end users will never see this data anyway?</div>
<div> - etc./other questions along these lines.</div><div><br></div><div>(btw, my solution for now is to use as generic a name as possible)</div><div><br></div><div>Thanks!</div><div><br></div><div><br></div>-- <br>Jeffrey D. Silverman • Moodlerooms, Inc.<br>
(410) 779-3425 • <a href="mailto:jeff@moodlerooms.com" target="_blank">jeff@moodlerooms.com</a><br><br>The CHANGE You Want E-Learning To Be<br>
</div>