Skip to content

regionsAllowed vs. eligibleRegion on MediaObject #4446

@suchajazzyline

Description

@suchajazzyline

Hello. Wanted to bring this to the group for consideration. It appears that the property regionsAllowed only appears on MediaObject, while MediaObject also contains the ineligibleRegion, which appears on multiple schemas, to serve as its inverse. However, I would expect MediaObject to use eligibleRegion instead for consistency. Both properties are expected to use ISO 3166 format and serve similar functions.

Taking a different approach, there was an older issue 974 that auto-closed addressing the lack of a true regionsAllowed inverse like regionsNotAllowed. Issue 1741 also gets at this a bit. Ideally, if regionsAllowed and ineligibleRegion were to remain as-is on MediaObject, perhaps the ineligibleRegion property description can be modified so it does not refer back to its inverse as being eligibleRegion? Thank you!

Metadata

Metadata

Assignees

No one assigned

    Labels

    no-issue-activityDiscuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!).

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions