Page History

...

In the CMA, the Fedora digital object remains the model for all digital objects just as it was in prior versions of Fedora. However, for the CMA we define four specialized variations of the Fedora digital object (see Table 1).

{table:border=1}
  {tr:align=center|bgcolor=#c0c0c0}
    {td}*Object Type*{td}
    {td}*Code*{td}
    {td}*Description*{td}
  {tr}
  {tr:bgcolor=#ffffff}
    {td}Data{td}
    {td}Data{td}
    {td}A container for content{td}
  {tr}
  {tr:bgcolor=#ffffff}
    {td}Service Definition{td}
    {td}SDef{td}
    {td}A container for the service definitions, an element of a content model{td}
  {tr}
  {tr:bgcolor=#ffffff}
    {td}Service Deployment{td}
    {td}SDep{td}
    {td}A container for service deployment bindings{td}
  {tr}
  {tr:bgcolor=#ffffff}
    {td}Content Model{td}
    {td}CModel{td}
    {td}A container for content models{td}
  {tr}
{table}

Table 1 - Fundamental Table 1 - Fundamental Fedora Object Types

Each of these specialized digital objects will be described in much greater detail below. The BDef and BMech have long been recognized as having reserved functions in Fedora and we often called them "control" objects because they contain data used to control object-specific functionality. CMA adds a new control object, the CModel. However, some of the data needed for object-specific functionality was located in the Data object (often just labeled generically as the digital object) in prior Fedora versions. In particular, Disseminators were defined in the Data object. The CMA eliminates the Disseminator and redistributes control data in a more logical and reusable fashion among the "control" objects.

...

Table 2 lists the supported relationships between fundamental object types in the CMA.

Table 2 - Relationships Between the Fedora Object Types

...