Stable schema locations

[Rod Widdowson]

A clarifying question:  You do just mean the Shibboleth project ones?  I'm
guessing that the other will have whatever they have, but that we *will* be
overriding the locations in the classpath so as to close that hole?

> I kind of think we need an explicit place to manage them for online
access.

Me too.  To a degree our schemata do represent documentation (less so in V3
than V2 I'd hope), and certainly they represent a contract with the user to
expecting them to grab them from svn or the jars kinda sucks.

Not to answer the question but to ask another one, which is related:  What
do we want to do about versioning our schema?

ISRT that the schema-schema has a place where one can put version
information, but when we rev a schema, do we want to revise where it lives?

Obviously we will only be introducing forward compatible changes, but does
that of itself mean that we don't have to worry about versioning the
locations?  On one hand it might be nice to easily see what schema V2 (or
v3.4.99) was using, but on the other having the same location through time
makes for an easier life for all and if someone cares about the precise
version that a release ran with they can check SVN or look at the jars.

Rod