top of page


The top-level “Party” class comprises “Person” and “Organization” subclasses, enabling a single class to assume one or more roles (e.g. customer/vendor) and legal ownership of physical (e.g., device) and informational (e.g., order) objects. The “Organization” class can comprise a hierarchy of subclasses (e.g., Business Unit, Team) and supports containment of one organization within another. An instance of the “Party” class is assigned as the owner of an object (via the “Owning Party” attribute of the root Object class). With this approach, every object is owned by a party and is assigned to an Owning Party when it is created. An Owning Party can be the person who creates the object using a device or an organization associated with the person or device. The Owning Party is given all the authorities to the object.  An instance of the “Party” class itself is owned by a party.   

Figure 34.png
Commerce Classes: Image


The top-level “Location” class represents any place or geographic position with subclasses supporting geolocation containment, as well as space subdivisions within a home or building (e.g., a Zone, Floor, Suite, or Room). The “Site” subclass includes unique attributes supporting a postal address.   A location can be assigned to a party, asset, and transaction (via a Relation attribute within those classes).

Figure 33.png
Commerce Classes: Image


The top-level “Offering” class and subclasses can classify products and services based on their essential attributes and their relationships to related offerings. This hierarchy enables trading partners to group offering instances in the same manner for comparisons across multiple e-commerce sites.
In addition to the “Identifier” attribute of the root Object class, an Offering instance can be identified by alternate Identifier attributes within the Offering class or subclass (e.g., “Model”, “GTIN”).

Figure 37.png
Commerce Classes: Image


The top-level “Asset” class and subclasses (“Inventory”, “Equipment”) represent resources or supplies that can be traded, transformed, used, or consumed to produce benefit. A production unit, based on a Product instance, usually begins as an inventory asset of the manufacturer (an “Inventory” instance) and transitions to an equipment asset of a customer (an “Equipment” instance).  The “Product” Relation attribute within the “Asset” class enables an asset to inherit the attributes of a Product subclass, in addition to the attributes of the Asset class (multiple inheritance).  

Figure 39.png
Commerce Classes: Image


The top-level “Agreement” class represents any negotiated and typically legally binding arrangement between parties as to a course of action.  Its “Party” Relation attribute identifies one party (e.g., [Brand]), while the “Owning Party” Relation attribute of the root object identifies another party (e.g., Heathrow Ltd.) in the agreement.

Figure 40.png
Commerce Classes: Image
bottom of page