The CatalogSpecificationRelationship entity provides the ability to group specifications much like the Composite/Atomic pattern using the “type” attribute to specify that the relationship is a composite/atomic. For example, a Smart Home CatalogSpecification could be comprised of a Smart Home Security CatalogSpecification and a Smart Home Appliance CatalogSpecification. The “type” attribute can also be used to indicate that one CatalogSpecification supersedes another or is included with another.<br/>The content of associated Catalogs can be dynamically defined using relationship to EntitySpecificationType for simple rules and/or to PolicySet for more complex rules. EntitySpecificationType is a way to create categories of any specification entity to which it or its subclasses are related, such as a ProductSpecificationType which is a subclass of EntitySpecificationType. For example, a Smart Home Security ProductSpecificationType could be related to the Smart Home Security CatalogSpecification. This relationship would enable a Smart Home Security Catalog, in this case a ProductCatalog, to be dynamically created. If there are more complex rules, such as limiting the catalog to only containing ProductOfferings that are in surplus status then a PolicySet could be defined to only include ProductOfferings that have this status.<br/>The Characteristic pattern can be used to define dynamic attributes for any CatalogSpecification along with the attributes values for any Catalog. <br/>Basic entities related to a CatalogSpecification and relationships with the existing entities are shown in the Figure Cat.01 – Catalog Specification.<br/>