*Attendees*
Grace Agnew, Rutgers
Keith Hazelton, U. Wisconsin
Tom Barton, U. Chicago
Jeanette Fielden, Internet2
Renee Frost, Internet2
Steve Olshansky, Internet2

*Discussion*
CourseID Model
Grace emailed to the list a definition of course and where it fits in the academic environment. There was general agreement the UML format is preferred. Roles will be left in the model to connect in later. Examples will be added to the course instantiation section.

Is it possible to stretch people’s minds without suggesting example attributes? If the description can be kept narrative then language stating how things will be represented can be avoided and the problem of accounting for all the different descriptions of term could be avoided.

The offering can be thought of as a range, a function with three inputs: course, section, and session. This would be functional in the sense that the course offering is specified uniquely by a given triplet.

Several things come together at the offering level. The session, the requirements for sections, which schools package different labs, recitations etc. Session might be related to the members and the roles. For an asynchronous course, each student enrolling could be a section. An enrollee might be the determiner only where the section is activated when someone enrolls in it.

How are different course sites represented? How is a web site identified from session to session. What are identifiers for strictly? Identifiers will have different functional purposes and will not always refer to the same kind of object. The need is to be careful that the offering object is consistent with the session object. The focal point of the structure should be the course offering. Meetings can be non-traditional and need to be accommodated. The purpose of a meeting is to enable contact with the sections.

A Birds of a Feather discussion is scheduled for CourseID for the Internet2 Spring Member Meeting. The details of the session will be mailed to the list when they are available.