Identifier and Classification of QA Actions

[jeannekitchens]

QA Action use cases require addtional properties:

Classification
Identifier

Texas Registry Use Cases in Career and Technical Education for credentials etc.. recognized or approved by a state to be include with a registry. In this case, the Credential Registry is the state's registry.

[siuc-nate]

This sounds good. Just to cover all of the bases, though, do you have an example of the classifications and identifiers they would be looking to use with QA actions?

[philbarker]

@jeannekitchens which are the QA Actions?

Accredit, Approve, Recognize, Registration, Regulate ?

[philbarker]

It might make sense to add classification and identifier to all Actions. It would do no harm that I can see, it would be more consistent and other orgs may well have the same use case for other types of action. So here is a formal proposal which adds them to all, and if some need deleting from the proposal that's fine.

Proposal

Use case: Allow identification and classification of instances of various Actions.

URI: ceterms:identifier

Add domain: ceterms:AccreditAction ceterms:AdvancedStandingAction ceterms:ApproveAction ceterms:CredentialingAction ceterms:OfferAction ceterms:RecognizeAction ceterms:RegistrationAction ceterms:RegulateAction ceterms:RenewAction ceterms:RevokeAction ceterms:RightsAction ceterms:WorkforceDemandAction

URI: ceterms:classification

Add domain: ceterms:AccreditAction ceterms:AdvancedStandingAction ceterms:ApproveAction ceterms:CredentialingAction ceterms:OfferAction ceterms:RecognizeAction ceterms:RegistrationAction ceterms:RegulateAction ceterms:RenewAction ceterms:RevokeAction ceterms:RightsAction ceterms:WorkforceDemandAction

[jeannekitchens]

@philbarker I agree that all of the "Action" domains should be added to ceterms:identifier and ceterms:classification.