On 08/30/2012 11:32 AM, James M Snell wrote:
> Yeah, it could be done that way. In the yaml I have it separated out as
> a different section but it doesn't have to to be way.
The original motivation for the registry was to establish some
namespaces. Since object/activity components share the same namespace as
external vocabulary keys I think it's clearer to keep them together so
that there's a single place to look for "what keys are valid in this
context and what do they mean?"
The other principle under which the registry was designed is that it is
an index of specs rather than a replacement for them. In other words, it
shouldn't aim to capture all of the subtleties of the specs, it should
just provide minimal information to help recognize a particular element
and then link to the normative prose describing that element.