I agree. It seems somewhat inconsistent to specify schemaTypes outside
respective Description types. For instance, event's type can be
referenced via EventDescription.schemaLocation, or the
ServiceDescription.schemaTypes. This makes consumers look into two
different places to decipher types.
We could consolidate these two into ModelDescription, and make
ModelDescription contain schemaLocation and schemaTypes.
BTW, isn't schemaTypes the same as ModelDescription.modelTypes? With the
consoliation, schemaTypes would go away completely.
Rich Thompson wrote:
In starting to add the language requested on the last TC call, it struck
me that it would be cleaner to use the ModelDescription type for
describing session properties rather than having a separate schemaTypes
field in 5.1.16 (PortletDescription). Any objections/comments?
The F2F asked me to locate and add a reference to the actual definition
of locales. I think this is RFC3066 (_http://tools.ietf.org/html/3066_)
and am adding that reference to section 5.1.10 for wd17. If someone has
a better reference, please post it soon.