Skip to content

Introduce instance-level requirements into the schemas #560

@Raphael-Gazzotti

Description

@Raphael-Gazzotti

This issue is linked to #513.

We may want to add requirements at the instance-level of our schemas.

e. g., a ResearchProduct requires to have a contribution/contributor with specific ContributorType/ContributionType. It makes sense to enforce that a Software product always includes at least one contribution/contributor whose contribution type is development/developer. Currently, our schema formalism does not allow specifying that if _type is Software then at least one contribution must have ContributionType="development"/ContributorType="developer". In other words, we can require the presence of a contribution/contributor field, but not enforce the kind of contribution/contributor.

A major point to address is that schemas would no longer be entirely independent from the instances.

Metadata

Metadata

Assignees

No one assigned

    Labels

    major updatelarge workload or major update needed to completequestionfurther information is requestedrequestany request or update for schemas

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions