βCMS "open" content model is defined by means of XML Schemas which may be categorized as follows:
-Core XML Schemas are located inside the βCMS content engine module (betacms-repository) and define the core modeling elements upon which any other modeling element is defined (User defined content elements inherit their basic properties from core elements)
-Internal or Bootstrap XML Schemas are also located inside the βCMS content engine module and define a basic set of content object types and complex property types for bootstraping an initial content model to start from when a new content repository is created. The provided model is mainly targeted towards web content modeling and also allows a basic management of documents.
-External XML Schemas are user defined and are located in a special directory under the directory of each content repository ($betacms_repositories/myrepository/betacms_definition_schemas/). User defined schemas implement the custom content model of each organization.

The reorganization of schemas mainly concerns the move of most of the default schemas, which are now provided in the installation package as External Schemas, into the repository engine module. So most of the default External Schemas will be relocated to be Internal Schemas. The movement will NOT alter the content model and will not be visible to end users. The main reason for this is to prevent altering of these schemas from developers / info architects. Some functionality provided by the portal-commons module depends on the bootstrap content model. Allowing the users to alter the bootstrap model will render some of the portal-commons functionality problematic or cause errors.
The idea is that the internal schemas together with portal-commons module supply some core functionality to quickly start managing content targeted for web sites and to quickly build a content portal that presents the modeled content. If users wish not to use the bootstrap content model, they may do so by building their own External XML Schemas which better model their content. In such a case the defined types in the bootstrap model will be visible in the βCMS console but may not be utilized for content input. In latter versions of βCMS it will be possible to either hide the bootstrap content types or create types which extended them.

Besides the reorganization refinement of the Schemas will be done. This concerns:
-The removal of the "pageTemplate" property property from the schemas where it is defined. The property will be added in the core element "contentObjectType" which is the parent of all defined content object types. In this manner this core property will be inherited by default to all defined content object types to allow the specification of a symbolic name for a page template to be used when presenting content object instances.
-The addition into the core element "contentObjectType" of a new core property named "pageTemplateObjectReference". This property will be inherited by all defined content object types and will allow to specify a page template that is store inside βCMS.

The above reorganization will result in the following change for all existing repositories that will install newer versions of βCMS:
Check the External XML Schemas locates under $BetaCMS_RepositoriesDir/myRepositoryName/repository//betacms_definition_schemas/ and remove any of the following that may exist in there to avoid dublicate definitions:
accessibilityType-1.0.xsd
administrativeMetadataType-1.0.xsd
betacms-model-types-1.2.xsd
dynamicContentArea-1.0.xsd
embeddedMultimediaResource-1.0.xsd
fileResource-1.0.xsd
genericContentResource-1.0.xsd
geoTag-1.0.xsd
multilingualStringPropertyType-1.0.xsd
organization-1.0.xsd
person-1.0.xsd
portal-1.0.xsd
portalSection-1.0.xsd
query-1.0.xsd
role-1.0.xsd
scheduledContentArea-1.0.xsd
statisticType-1.0.xsd
webPublicationType-1.0.xsd
webResourceLink-1.0.xsd
workflowType-1.0.xsd