migrating xml schema definitions from v2 to v3 ?

[Tom Zeller]

For v3, should the xsd's be distributed across multiple modules or
co-located in one module ?

For example, if distributed, xsd's would live in
idp-attribute-resolver-spring and idp-attribute-filter-spring, etc. If
co-located, all xsd's would be in idp-schema or somesuch.

I am leaning towards co-located, because these files provide a
configuration reference hopefully useful to deployers.

Most of the idpv2 xml schema definitions live in java-shib-common, but
there is one in java-idp.

java-idp/src/main/resources/schema :

shibboleth-2.0-idp-profile-handler.xsd

java-shib-common/src/main/resources/schema :

shibboleth-2.0-afp-mf-basic.xsd
shibboleth-2.0-afp-mf-saml.xsd
shibboleth-2.0-afp.xsd
shibboleth-2.0-attribute-authority.xsd
shibboleth-2.0-attribute-encoder.xsd
shibboleth-2.0-attribute-map.xsd
shibboleth-2.0-attribute-resolver-ad.xsd
shibboleth-2.0-attribute-resolver-dc.xsd
shibboleth-2.0-attribute-resolver-pc.xsd
shibboleth-2.0-attribute-resolver.xsd
shibboleth-2.0-metadata.xsd
shibboleth-2.0-profile-handler.xsd
shibboleth-2.0-relying-party-saml.xsd
shibboleth-2.0-relying-party.xsd
shibboleth-2.0-resource.xsd
shibboleth-2.0-security-policy-saml.xsd
shibboleth-2.0-security.xsd
shibboleth-2.0-services.xsd
shibboleth-metadata-1.0.xsd