Skip to content

schema/doc inconsistency: allow identifier strings in cross-reference properties #53

@dgbroeder

Description

@dgbroeder

Several cross-reference properties (references to other entities) are documented (.md spec) as accepting plain identifier strings (e.g.
"org_1", "ven1") but the schema defined them as $ref object types only, causing validators to reject data the docs
explicitly show as valid.

propose modifications skg-if-openapi.yaml:

Changes from bare $ref / oneOf to anyOf: [string | $ref] for:

  • Product: topics[].term, relevant_organisations[], funding[], contributions[].declared_affiliations[],
    contributions[].by, manifestations[].biblio.in, manifestations[].biblio.hosting_data_source
  • Person/Agent: affiliations[].affiliation
  • Grant: beneficiaries[], contributions[].declared_affiliations[], contributions[].by, funding_agency

API responses may still return expanded objects. I have an update, but unable to create a pull request

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions