Add ceterms:LearningOpportunityProfile and ceterms:Credential to the domain of ceasn:comment

[jared-diener]

Academic catalogs often include important information about courses, programs, and credentials in a note. This is distinct from requirements and advisory notes, which should go in a Condition Profile. Rather than including this information in the general description, it would make sense to use ceasn:comment.

So, this is a proposal to add ceterms:LearningOpportunityProfile and ceterms:Credential, and their subclasses, to the domain of ceasn:comment.

Example of this kind of note:

Course:

System Requirement: Students must have regular access to a computer with C compiler software either on a Windows or MS-DOS computer or on a Macintosh with PC emulation or with SoftPC installed. A C compiler is not supplied by the University and must be acquired by the student prior to or at the start of the course. It is not possible to proceed through the course without a C compiler. The compiler should be a full implementation of the ANSI standard for C. An ANSI C++ compiler may be used because C is a supported subset in a C++ compiler. Complete documentation is required to handle compiler variants and operational problems.

[philbarker]

It might be cleaner to add a new property to ceterms: .

ceasn:comment is equivalent to asn:comment and case:notes, in other words it comes with baggage from Competency Statements. OTOH, we have already used on some terms that are competency-adjacent, and qdata:Observation, so perhaps that bridge has been crossed. But we should consider the implications of both these statements being true:

ceasn:comment owl:equivalentProperty asn:comment .

and

asn:comment rdfs:domain asn:Statement .

i.e. that anything described using ceasn:comment may be inferred to be a Competency Statement.