Skip to content

Add COLLATE behavior #543

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
edeutsch merged 1 commit into from
Feb 12, 2026
Merged

Add COLLATE behavior #543

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions TranslatorReasonerAPI.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -926,19 +926,24 @@ components:
MANY means that member CURIEs MUST form one or more
sets in the Results, and sets with more members are generally
considered more desirable that sets with fewer members.
If this property is missing or null, the default is BATCH.
Only when there are no ids provided, set_interpretation MAY be
set to COLLATE to indicate that multiple matching nodes MUST be
collated into a single Result, rather than separated into
separate Results. If this property is absent, the default is
BATCH.
enum:
- BATCH
- ALL
- MANY
- COLLATE
member_ids:
type: array
description: >-
A list of CURIE identifiers for members of a queried set. This
field MUST be populated under a set_interpretation of MANY
or ALL, when the 'ids' field holds a UUID representing the set
itself. This field MUST NOT be used under a set_interpretation
of BATCH.
of BATCH or COLLATE or when set_interpretation is absent.
minItems: 1
items:
$ref: '#/components/schemas/CURIE'
Expand Down