Skip to content

Negative requirements and exceptions on Conditions #1003

Description

@philbarker

These could be covered by a property such as excludes to be used on ConditionProfiles, defined as the opposite of requires, i.e. something that is not allowed.

This is mostly motivated by what we are seeing in Credit Transfer Agreements, but may have wider applicability. We sometimes see the opposite to a requirement, or an exception to a generally stated requirement. For example lists of courses for which are excluded from transfer agreements. Or statements that "any Math course except MathX" are transferable or meet some entry condition. A more general example is that one requirement for funding to cover fees is that the person must not have a credential at or above the level of the program for which funding is sought.

There can be other ways of expressing these, e.g. list what is required not what isn't! or the context of the ConditonProfile may rule out the exception (e.g. by the use of transferFrom and transferTo), or a ceterms:condition with text that expressed the negative requirement, but it is worth considering whether we could be explicit by adding excludes as a property as this would be more explicit and sometimes listing everything except one thing can be a long list.

More concrete examples would be useful.

Metadata

Metadata

Labels

HandbookPrior Learning RecognitionRelevant to the Prior Learning Recognition Policies & Agreements as Data Global Task Group

Type

No type
No fields configured for issues without a type.

Projects

Status
Completed

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions