Terminology

The source of images from this section are screen captures from an Apple Keynote file that @Jim Wilson and @Fohn, Steffen (CORP) have maintained. See

Principles

We should avoid exposing domain experts to the various Core Component views (view, create, edit, etc.).

Core Component Term	OAGi Term	Comments
Aggregate Core Component (ACC)	Component Type	Component class or definition.
Association Core Component Property (ASCCP)	Component	A Component instantiates a Component Type and is used for assembly.
Association Core Component (ASCC)	Component Property	Component Property that exists in an association (i.e., assembly).
Data Type	Data Type	Business Data Type or Core Data Type.
Business Data Type (BDT)	Business Data Type	Restricted Core Data Type.
Core Data Type (CDT)	Core Data Type
Basic Core Component Property (BCCP)	Field	A Field instantiates a Field Type and is used for assembly.
Basic Core Component (BCC)	Field Property	Field Property that exists in an association (i.e., assembly).
Data Type Supplementary Component (DTSC)

BIE
- Profile
- [ Profiled | Contextualized | Qualified | something else ] + [ Message | Component | something else ]
  - e.g., Profiled Message, Contextualized Component
BIE-creation process
- Create a profile
- [ Profile | Contextualize | Qualify | something else ] + “a” + [ Message | Component | something else ]
  - e.g., Profile a Message, Contextualize a Component

Context: A connectCenter instance that includes connectSpec, ADAPT Standard, and HR Open Standards.

Key consideration: Terminology being used or developed in the Flexible Supply Chain WG group for mapping.

Questions

How should we generally refer to connectSpec, ADAPT Standard, and HR Open Standards?
1. Models?
2. Namespaces?
3. Libraries?
4. It depends on context of use?
How would this look as top-level connectCenter menu items? Jim envisions something like:
1. Model | Context | Profile
2. Library | Context | Profile
3. …whatever…