Keys maintain the relationship between textbook codes and the text readings, as well as teachers and class lecturers. The root element of the schema is course, since we realized that the syllabus information is really a child element of a greater set of information about the course. Basic information like course title, description, and units are grouped in a GeneralInformation wrapper, followed by the syllabus elements themselves. This is the wrapper class for all the basic course information that we capture in addition to the actual syllabus. If a course has variable unit options, editors can use this element to list the possible unit values. Since there can be many types of course websites, any number can be included in the xml instance, and an enumerated attribute allows for differentiation. Current website types incude a main site (assumed when there is no attribute), wiki, and blog. The enumeration can be expanded to include any new web trend that comes along. See explanation of CourseWebsiteType, above. Basic information about each department in which a course is listed - a course might have any number of department listings. Department codes are maintained in the BABL codelist. Based on babl BerkeleyAcademicDepartmentCodeContentType - these are the departments for which SIMS classes might be cross listed (i.e. those in which SIMS professors have cross-appointments). Any wider adoption of Sylvia will require additions to this codelist. Computer Science City and Regional Planning Economics Electrical Engineering and Computer Science Engineering Information Management and Systems Industrial Engineering and Operations Research Boalt School of Law Mechanical Engineering Haas School of Business Schedule type indicates year, semester, and start and end dates for a class. This allows for a syllabus to be reused year-to-year with the same class numbering, as the application automatically adjusts for the schedule dates. Based on babl BerkeleyTermCodeContentType. Fall Spring Summer Winter Since some classes setup an email that is directed to all teachers and TA's, the teaching team has its own contact child element. Contact information is pretty self-explanatory. An enumerated codelist allows for an attribute indicating the type of phone. See annotation for PhoneType, above. This element includes all necessary information about teachers for the class. The enumerated typeCode corresponds to Berkeley's official categorization. teacherCode is an xsd key which is referenced in the lecture element which is a child of class, below. Normally teacherCode would be a teacher's initials. See documentation for TeacherType, above. Our name element give the editor a choice between one full name string (intended mostly for use with institutional names) and personal name group which includes given name, middle name(s), and family name. See documentation for NameType, above. This element holds information on teacher office hours - it includes the dayPattern element, which indicates a series of days and times and is reused in the actual syllabus element. DayPattern is composed of one or more sets of days and times within that day. For instance, a teacher might have office hours on Wednesday from 2-3 and Thursday from 10-11. A particular day and time - see documentation for DayPatternType, above. Based on BABL DayOfWeekType, code list for days of the week. Sunday Monday Tuesday Wednesday Thursday Friday Saturday A simple time span type includes a start time and end time. Based on babl BerkeleyGradingOptionCodeContentType - these are all the valid UC Berkeley grading options. Letter Grade only Pass/No Pass only Satisfactory/Unsatisfactory only Letter Grade or Pass/NoPass or Satisfactory/Unsatisfactory In Progress Based on expert feedback, we decided that having an optionally empty text wrapper class would be better for processing than having text and reader elements which might or might not be present. So here is that wrapper class. The textbook element includes all the basic bibliographic information. The textbookCode is an xsd key referenced in the textReading element, below. The volume information is captured as a group so it can be reused in some of the reading types, below. Also, the requirement enumeration allows teachers to indicate to students which books are really necessary. Basic bibliographic information used in TextbookType, AnthologyReadingType, and ChapterReadingType. See documentation for TextbookType, above. Information about the course reader includes copy store and optional comments. GradingCriteria allows a teacher to indicate the percentages by which the final grade will be determined (i.e. Exams 50%, Project 50%). A grading criterion is composed of one area of class requirements and the percentage at which it will enter into the final grade. See gradingCriterion, above. Based on the more general ResourceType, below, but we include an optional group attribute in case professors want to group their course resources under some more specific headings. Resources, which can be applied to the course, a class, a reading, or an assignment, are a bit of a catch-all element for professors to include any extra content they feel will be helpful for the syllabus. The syllabus element is the heart of the schema. A course will have one syllabus for every type of meeting conducted - for instance, a course with both lecture and lab will have one syllabus for each. These meeting types are based on official Berkeley designations and are contained in a BABL codelist. In general, each syllabus indicates the time and place to meet, as well as information about classes, assignments, and exams. Based on babl BerkeleyInstructionFormatCodeContentType - these are all the valid UC Berkeley grading options. Lecture Discussion Laboratory Seminar Studio Workshop Field Study Colloquium Clinic Tutorial Individual classes can optionally be grouped into components if the course is organized around larger themes. If components are chosen, then each class must be the child of components - mixing and matching component classes and stand-alone classes is not allowed. So the children of the ClassesType will either be a series of components with classes as their children, or just a series of classes. If the syllabus groups classes into components (see ClassesType, above), then each component has a title, optional description, and child class elements. The class element is slightly complicated. Title is required, along with either a class number or class date. If a number is used, the application automatically maps this to the appropriate calendar date based on the ScheduleType, above. For makeup classes or others falling out of the general pattern of class meetings, users can indicate a specific class date instead. Optional elements include class description and an element indicating that there is a holiday. A choice is given between lecturer, keyed to the TeacherType teacherCodes above, or guest lecturer. Also optional are discussion leader and readings and resources for the class. Guest lecturers' names must be included, along with optional affiliation and contact information. Based on expert feedback, we decided that having an optionally empty reading wrapper class would be better for processing than having reading elements which might or might not be present. So here is that wrapper class. Readings are modeled as a substitution group with four elements common to all reading types. Those four elements are included here, and this element forms the basis for all the more specific reading types in the substitution group. Medium indicates where a student can find the reading. It is used for all reading types except website reading, which is obviously online. Anthology reading is used to assign a chapter or article from a book that is a collection of pieces by difference authors. Since the anthology might be a textbook or a chapter from a non-required text, editors can choose between using just the code for a textbook or the full volume group (see documentation for TextbookType, above). Used for encoding a legal bill or law as a reading. Used for encoding a legal brief as a reading. Used for encoding a court case as a reading. Chapter reading is used to assign a chapter from a book by a single author or authors (as opposed to AnthologyReadingType, above). Since the book might be a textbook or a chapter from a non-required text, editors can choose between using just the code for a textbook or the full volume group (see documentation for TextbookType, above). Used for assigning an article from a journal, either online or in paper form. Website reading is intended for when students should be perusing a website generally or a piece available online, though articles from online journals might be better modeled using JournalReadingType, above. Based on expert feedback, we decided that having an optionally empty resource wrapper class would be better for processing than having resource elements which might or might not be present. So here is that wrapper class. A wrapper element for the syllabus assignments. All assignments have a title and either an assigned day of class, corresponding to one of the class numbers, or an assigned date, if it is assigned outside of the normal class schedule. When an assignedDayOfClass is used, the application automatically maps it to the appropriate calendar date based on the course ScheduleType, above. Similar handling is used for dueDayOfClass or dueDate. Optionall, teachers can include a dueTime. Assignment descriptions can be included in the syllabus or, if the assignment is long and/or complicated, teachers can create a seperate web page for the description and include just the link here. Similar handling is used for answers. Percentage indicates how much this assignment will count towards the final grade. Resources can optionally be included, and a required status enumeration tells the student if the assignment is graded, ungraded, or optional. An enumeration indicates the status of an assignment - see AssignmentType, above. Wrapper class for the exams in the syllabus. Though we had originally assumed that take home exams would be modeled as assignments, our users expressed desire for a dedicated take home exam element. So we decided to use a substituion group. Both sorts of exams have a code (indicating type of exam), percentage of final grade, and comments. These general elements form the basis for the more specific exam types, below. See ExamType, above. Like assignments, a take home exam has a start and end date and can use day of class, corresponding to one of the class numbers, or an date, if it is happening outside of the normal class schedule. When a DayOfClass is used, the application automatically maps it to the appropriate calendar date based on the course ScheduleType, above. Much like assignments, an in class exam can have an exam day of class, corresponding to one of the class numbers, or an exam date, if it is happening outside of the normal class schedule. When an examDayOfClass is used, the application automatically maps it to the appropriate calendar date based on the course ScheduleType, above. Time span shows when the exam is (generally needed only with examDate, since examDayOfClass would presume the usual class meeting time). Location of the exam must be included. Some elements used to keep track of when the syllabus was last updated. We hope to maintain this information programmatically in the finished app. Users often want to include basic HTML tags in description, comment, and similar elements. Substitution groups are used so the HTML tags can be nested arbitrarily. This htmlContent element contains any number of abstract htmlTag elements, which are substituted by the various HTMLType elements below. The abstract element which is the basis for our HTML substitution group, see htmlContent, above. To accommodate alternate transforms using proprietary CSS, some HTML tags allow for a class attribute. These HTML tags can be combined and nested arbitrarily based on our HTML substitution group. See htmlContent, above. The list elements (ul,ol,dl) can contain the li tags. The HTML anchor tag is allowed its href attribute.