Many EducationalOccupationalProgram pages provide information for determining how long a program typically takes, when terms typically run, and when applications are accepted. I propose adding the following properties to EducationalOccupationalProgram to allow authors to mark up that sort of data.
The properties include:
numberOfUnits: The number of units or credits required to complete the program, not including prerequisites for enrollment.
typicalUnitsPerTerm: The number of units or credits a full-time student would be expected to take in 1 term however 'term' is defined by the institution.
termDuration: The amount of time in a term as defined by the institution. A term is a length of time where students take one or more classes. Semesters and quarters are common units for term.
termsPerYear: The number of times terms of study are offered per year. Semesters and quarters are common units for term. For example, if the student can only take 2 semesters for the program in one year, then termsPerYear should be 2.
applicationStartDate: The date at which the program begins collecting applications for the next enrollment cycle.
applicationDeadline: The date at which the program stops collecting applications for the next enrollment cycle.
maximumEnrollment: The maximum number of students who may be enrolled in the program.
educationalProgramMode: Similar to courseMode, The medium or means of delivery of the program as a whole. The value may either be a text label (e.g. "online", "onsite" or "blended"; "synchronous" or "asynchronous"; "full-time" or "part-time") or a URL reference to a term from a controlled vocabulary (e.g. https://ceds.ed.gov/element/001311#Asynchronous ).
timeOfDay: The time of day the program normally runs. For example, "evenings".
I also propose extending the domains of the following existing properties to include EducationalOccupationalProgram:
startDate
endDate
dayOfWeek
Many EducationalOccupationalProgram pages provide information for determining how long a program typically takes, when terms typically run, and when applications are accepted. I propose adding the following properties to
EducationalOccupationalProgramto allow authors to mark up that sort of data.The properties include:
numberOfUnits: The number of units or credits required to complete the program, not including prerequisites for enrollment.typicalUnitsPerTerm: The number of units or credits a full-time student would be expected to take in 1 term however 'term' is defined by the institution.termDuration: The amount of time in a term as defined by the institution. A term is a length of time where students take one or more classes. Semesters and quarters are common units for term.termsPerYear: The number of times terms of study are offered per year. Semesters and quarters are common units for term. For example, if the student can only take 2 semesters for the program in one year, then termsPerYear should be 2.applicationStartDate: The date at which the program begins collecting applications for the next enrollment cycle.applicationDeadline: The date at which the program stops collecting applications for the next enrollment cycle.maximumEnrollment: The maximum number of students who may be enrolled in the program.educationalProgramMode: Similar tocourseMode, The medium or means of delivery of the program as a whole. The value may either be a text label (e.g. "online", "onsite" or "blended"; "synchronous" or "asynchronous"; "full-time" or "part-time") or a URL reference to a term from a controlled vocabulary (e.g. https://ceds.ed.gov/element/001311#Asynchronous ).timeOfDay: The time of day the program normally runs. For example, "evenings".I also propose extending the domains of the following existing properties to include
EducationalOccupationalProgram:startDateendDatedayOfWeek