Indie UI Repository structure

Below is a proposed structure for the Indie UI repository:

events
  + 1.0
    + spec
      + indie-ui-events.html
      + {supporting files if any}
    + tests
context
  + 1.0
    + spec
      + indie-ui-context.html
      + {supporting files if any}
    + tests

It has been proposed that the version identifier be dropped as a
containing folder. I don't yet have the knowledge of Mercurial to
understand if we can maintain a clear relationship between branches and
W3C versions.

There would be other ways we could organize, e.g., have spec and tests
be top-level folders and the specific deliverables inside them, rather
than the other way around. This was just a starter proposal.

Michael
-- 

Michael Cooper
Web Accessibility Specialist
World Wide Web Consortium, Web Accessibility Initiative
E-mail cooper@w3.org <mailto:cooper@w3.org>
Information Page <http://www.w3.org/People/cooper/>