Skip to main content

Profiles

Manage OML Profiles​

The OML Profiles section in Admin Settings allows administrators to manage modeling profiles that define the vocabulary for specific concerns or domains. Each profile version is displayed as an individual card with its metadata and lifecycle status.

❗️info

This section provides an overview of existing profiles and enables import/export operations. For detailed information about profile concepts and structure, see Profiles.

Viewing Profiles​

The profiles overview displays all available profile versions as cards, showing:

  • Icon: Visual identifier from the profile specifications
  • Name: Display name of the profile
  • Description: Human-readable description
  • Version number: Semantic version (e.g., 1.0.0)
  • Status: Current lifecycle state (Draft, Published, or Deprecated)
  • Tags: Categorization tags for filtering and organization

Filtering Profiles​

Use status filters to control which profiles are displayed:

  • Draft (default: enabled): Profiles under development
  • Published (default: enabled): Released profiles available for use in baselines
  • Deprecated (default: disabled): Profiles no longer recommended

Adding a New Profile​

To add a new profile:

  1. Click the Add profile button
  2. In the sidebar that opens, upload a YAML file containing the profile definition
  3. Click Add to upload (or Cancel to abort)

Validation​

When adding a profile, the system validates:

  • File format: Must be a valid YAML file
  • Profile structure: The YAML must conform to the OML profile schema
  • Required fields: All mandatory profile attributes must be present

If validation fails, appropriate error messages are displayed.

❗️info

All newly added profiles start in Draft status.

Managing Profile Lifecycle​

Each profile card provides an overflow menu with the following operations:

Upload New File​

Icon: Upload Availability: Only when status is Draft

Allows you to replace the profile file with an updated version. Opens the same upload dialog as adding a new profile. Use this to iterate on a profile before publishing it.

Download File​

Icon: Download Availability: Always available

Downloads the profile YAML file to your local machine. Useful for:

  • Creating backups
  • Sharing profiles with other teams
  • Using as templates for new profiles
  • Version control and collaboration

Set Status to Published​

Icon: Rocket Availability: When status is Draft or Deprecated

Publishes the profile, making it available for use in project baselines.

Once published, a profile becomes immutable and cannot be modified or deleted.

⚠warning

Published profiles cannot be reverted to Draft status.

Set Status to Deprecated​

Icon: Archive Availability: When status is Draft or Published

Marks the profile as deprecated, indicating it's no longer recommended for new baselines. Deprecated profiles:

  • Remain available for existing baselines that reference them
  • Are hidden by default in the profile overview (unless the Deprecated filter is enabled)
  • Can be re-published if needed

Best Practices​

  • Version incrementally: Create new versions with semantic versioning rather than modifying published profiles
  • Document clearly: Use descriptive names, descriptions, and tags
  • Deprecate gracefully: When superseding a profile, deprecate the old version rather than deleting it
  • Coordinate with baselines: Publish profiles before publishing baselines that reference them
  • Backup regularly: Download profile files periodically for disaster recovery
  • Follow naming conventions: Use consistent ID patterns (e.g., domain-profile, c4-profile)

Profile Lifecycle States​

StatusDescriptionCan ModifyCan DeleteAvailable for Baselines
DraftUnder developmentYesYesNo (testing only)
PublishedReleased for useNoNoYes
DeprecatedNo longer recommendedNoNoYes (existing baselines)