Review potential opportunities in restructuring XSD package layout

[jwrage]

[jwrage]

VERY ROUGH concept not at all very well thought out.

[jwrage]

• Allow easy differentiation between Enterprise and xPress
• Allow self-contained deployment of Enterprise vs. xPress and xPress solutions?
• Provide a good way to provider future xPress solutions; may want to consider having a subfolder by solution?
• Platform includes common components for Enterprise and xPress solutions
• "Contrib" would be a spot for community contributed (but non-Association developed) XSDs
• "Site" would be a spot for site-specific XSDs
• May want to have "site" as a peer to "Enterprise" and "xPress"

[ajackl]

I am not sure we want to build in that level of separation. We certainly want to make it possible to navigate easily to Xpress objects and have people NOT have the experience of "wading " through the giant spec to get to it but i think we should be careful we don't create two separate specs which was a big concern of the Tech boards.

Obviously - the interface to this and the actual structure are also two different but related conversations. We can handle them each differently.

[jwrage]

It's worth a conversation at some point. It's also become apparent through the use of Github that the current structure makes it very difficult to work on different pieces of the spec at one time.