General problem statements
Some content connectCenter presents can be overwhelming to non-technical people.
Some content connectCenter presents can be overwhelming to technical people new to connectCenter leading to a first impression of "overly complicated".
Some content connectCenter presents can be more than is necessary in various use cases.
Users and observers
connectCenter users sharing their screen
connectCenter users not sharing their screen
Non-technical people watching someone else sharing their connectCenter screen
Technical people new to connectCenter watching someone else sharing their connectCenter screen
Technical people familiar with connectCenter watching someone else sharing their connectCenter screen
High-level use cases
connectCenter / connectSpec demo
Various conversations with domain experts while screen sharing
connectCenter / connectSpec training
Developing promotional and education content
Browsing connectSpec or ADAPT Standard
CC model development
BIE development
Enhancement 1: Component browser view
See Add model browser view · Issue #1637 · OAGi/Score (github.com).
Enhancement 2: Sibling sort order
Enhancement 3: Support updated 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.).
Use case - modeling experts sharing screen showing BIE UI while talking with domain experts, API designers, and API developers (i.e., implementers)
Use case - modeling experts sharing screen showing CC UI while talking with CCS experts, API designers, API developers (i.e., implementers), and data architects
Mapping: core component terms and OAGi terms
Core Component Term | OAGi Term | Comments |
Aggregate Core Component | Component Type | Component class or definition. |
Association Core Component Property | Component | A Component instantiates a Component Type and is used for assembly. |
Association Core Component | 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 | Business Data Type | Restricted Core Data Type. |
Core Data Type | Core Data Type | |
Basic Core Component Property | Field | A Field instantiates a Field Type and is used for assembly. |
Basic Core Component | Field Property | Field Property that exists in an association (i.e., assembly). |
Alternative terms for speaking about and writing about “BIE” Concepts
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
For discussion: Big-picture terms
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?
Models?
Namespaces?
Libraries?
It depends on context of use?
How would this look as top-level connectCenter menu items? Jim envisions something like:
Model | Context | Profile
Library | Context | Profile
…whatever…
Enhancement 4: Show/hide rarely used components
Upon further consideration, Jim Wilson holds the view that this would be unnecessary if #2 were supported.
Enhancement 5: Reorganize search
Change search as follows:
Filter by ASCCP by default
Enhancement 6: Add simplified search-results view
Keep the existing view as an option
Add a simplified view that looks something like this:
