PAGEOM_ — PAGE-OM package

I understand that the PAGE-OM package was added in response to Issue #13023. However, the role of the contained class "Page" (Section 7.1.1.1) is thoroughly unclear. Please document the purpose of the Page class and the reason that it contains 69 associations, apparently one to every other class in the model. If you can't clearly document the purpose of this class and its associations, you should remove it. Note also that the name of the class "Page" (Section 7.1.1.1) conflicts with the "PAGE" package (Section 7.1.2); this may not generate a syntax error in most tools, but it is certainly confusing for the human reader.

1) PAGE package gone (see the issue 13811). Its contents is
incorporated into the main package PAGE-OM.

2) Therefore, the class Page does not have anymore a confusing
name. Also, its description was updated.

Resolution:

• The changes of package name for classes previously in the package PAGE are in the generated documentation (Chapter 7).
• The PAGE class got a better description (again, it is generated directly from the model into Chapter 7): "This class does not contain any scientific meaning. Its mainpurpose is to be the root element for the situations where this specification is used for data exchange formats (e.g. xml-schema). Therefore, it has optional direct associations to all important classes so that implementations can exchange only relevant data."