Techniques for Extending Schema Scope

[This is preliminary documentation and subject to change.]

You can either specify values for the expected content class property in a content class definition itself or by setting it on the applicable folder.

Setting the expected content class value on the folder is the most direct; however, suppose there were several content classes you wanted to be expected on the folder. It can be tedious to maintain the array of expected content classes on every pertinent folder, but by using the expected-content-class setting in the content-class definition, you only have to maintain the array at one location. As long as the application folders have their schema-collection-ref properties using a URL that points to your schema folder, you can propagate the expected content classes from that one setting in the content-class definition.

You can use the extends property in the content-class definition to inherit from other content classes. Then, if you set the content class you are defining in the array of expected content classes in that content-class definition, you have further streamlined your schema scope without having to manipulate the expected-content-class properties on your application folders.