UML14 — Clarify that profiles can contain model libraries

The definition of <<modelLibrary>> says it is:

A package that contains model elements which are intended
to be reused by other packages. A model library differs from
a profile in that a model library does not extend the
metamodel using stereotypes and tagged definitions. A
model library is analogous to a class library in some
programming languages.

However, profiles can contain model libraries. UML 1.x has an explicit
dependency to model this (called <<modelLibrary>> also). It should be
clarified that in 2.0 this is done by including model library pacakages
in profile packages. The above text should be clarified. Suggestion:

A package that contains model elements which are intended to be
reused by other packages. A model library can be contained in a
profile package, but the classes in a model library are not
stereotypes stereotypes and tagged definitions extending the
metamodel. A model library is analogous to a class library in some
programming languages.

see above