The spec is a bit unclear about this, but it appears that hierarchical resource
library names are not supported. It is desirable to support them for two reasons.
1) It allows developers greater flexibility in structuring their resources and
2) It allows for longer package names with backing components for composite
(NB. Mojarra will load hierarchical names such as components/util.)
Two changes are required.
1) In section 220.127.116.11, add a bullet that a libraryName is a /-separated sequence
of libraryDirname. If
adopted, specify that each libraryDirname must not match the regexes for
versions or locales.
let fqcn be library-name + "." + resource-name
let fqcn be library-name.replace("/", ".") + "." + resource-name