Ambiguity in $sourceDescription.* runtime expressions

[char0n]

Problem

Current format $sourceDescriptions.<name>.<reference> is ambiguous - <reference> could be:

• A field from SourceDescription object (like url)
• An operationId from OpenAPI source
• A workflowId from Arazzo source

If we have operationId="url" in source OpenAPI Document, or workflowId="url" in Arazzo Document, it becomes ambiguous.

Proposed Format (Unambiguous)

$sourceDescriptions.<sourceName>.<fieldName> # field access
$sourceDescriptions.<sourceName>.operation.<operationId> # operationId reference
$sourceDescriptions.<sourceName>.workflow.<workflowId> # workflowId reference (allows us to validate workflowId format)

Examples:

• $sourceDescriptions.petStore.url → field access
• $sourceDescriptions.petStore.operation.getPets → operationId
• $sourceDescriptions.petStore.workflow.loginFlow → workflowId

[char0n]

Maybe introducing a described order of resolution priority might limit the ambiguity as the proposed fix is technically backward incompatible