Different schema results when using empty profiles parameter versus no parameter

[rajkarkar-crestdata]

A discrepancy is observed when querying schemas using an empty profiles parameter compared to querying without the profiles parameter in both the JSON Schema API and the OCSF UI.

Requests made without query parameters and requests made with an explicitly empty profiles parameter return different schema results.

Examples:

• Without parameter: https://schema.ocsf.io/1.5.0/classes/network_activity
• With empty profiles parameter: https://schema.ocsf.io/1.5.0/classes/network_activity?profiles=

API Response Discrepancy

For the Network Activity class:

• Without parameters: https://schema.ocsf.io/schema/1.7.0/classes/network_activity

{
"required": [
    "activity_id",
    "category_uid",
    "class_uid",
    "cloud",
    "metadata",
    "osint",
    "severity_id",
    "time",
    "type_uid"
  ]
}

• With empty profiles parameter: https://schema.ocsf.io/schema/1.7.0/classes/network_activity?profiles=

{
  required": [
    "activity_id",
    "category_uid",
    "class_uid",
    "metadata",
    "severity_id",
    "time",
    "type_uid"
  ]
}

When querying with an empty profiles parameter:

• cloud and osint fields are not included in the root-level required fields.
• The same fields are also absent from the properties section.

UI Discrepancy
Similar behavior is observed in the UI, where certain fields appear only when no parameters are provided in the URL.

Example — Device Inventory Info (5001) class

• Without parameter (device field present): https://schema.ocsf.io/1.7.0/classes/inventory_info

• With empty profiles parameter (device field not present): https://schema.ocsf.io/1.7.0/classes/inventory_info?profiles=