Application Class

Revision as of 12:29, 14 June 2017 by Chau (talk | contribs) (→‎Element structure (Application Class))
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

For the description how to request a new application class, please see: Application_Class_(Create_Change_Request).

Property lists are compilations of individual features to describe individual commodities. In eCl@ss, each subgroup (classification class at the fourth level) is described with the help of properties. The properties are not directly assigned to a subgroup but to a so-called application class which is connected to a subgroup. In the versions before eCl@ss 6.0, eCl@ss has used sets of properties that were directly assigned to a classification class - as it is still shown in the BASIC version. Application classes are only visible in the ADVANCED version.

Interrelation of Application Classes

The application class is part of the ADVANCED dictionary and not visible in the BASIC dictionary. For every Classification Class a BASIC Application Class - AC(BASIC) - is automatically created and assigned in the background. This is not visible to the BASIC user, as currently CC:AC(BASIC) is a 1:1-relation. An ADVANCED Application Class - AC(ADVANCED) - does not necessarily exist for the same Classification Class as it might not have been required yet.


NOTE: A CC always has a mandatory AC(BASIC) and can have an optional AC(ADVANCED). Therefore the creation of an AC in the eCl@ss ContentDevelopmentPlatform is only relevant and visible for ADVANCED users.

Element structure (Application Class)

The following part will describe how the structural element "application class" is structured and what attributes it consists of. All attributes are named in CamelCase writing. Attributes can be mandatory or optional, can be created automatically or manually be the user and underly certain rules. All of them are limited to a certain amount of characters.

Identifier (Application Class)

The official and internationally unique eCl@ss identifier, i.e. primary key, is the IRDI (International Registration Data Identifier), a globally unambiguous identifier that comprises Supplier+TypeOfSE+Identifier+VersionNumber. The separate export of Supplier, ID, VersionNumber and the Identifier (ID+ VersionNumber) is therefore redundant. Starting with eCl@ss Release 8.0 this redundant information will no longer be additionally exported, because it is already contained in the IRDI which is the only valid primary key in eCl@ss.

The identifier for classification classes is the IrdiAC. It is mandatory, automatically created and limited to 20 characters. TheTypeOfSE of a class is 01.

Preferred Name (Application Class)

The text attribute named PreferredName is the official name of the product class and is a mandatory text field. The PreferredName is identical with the PreferredName of the corresponding classification class. The rules are the same as for classification class names

Definition (Application Class)

Today, the class definition is a mandatory text field. The definition is identical with the definition of the corresponding classification class. The rules are the same as for classification class definitions

Change Request

How to request a change on an application class in the eCl@ss ContentDevelopmentPortal?

Please see here: Application Class (Create Change Request)

Rules for the creation of a change request are described here: General rules for Change Requests

Related Information