RESTFful/Resource Oriented Design

I think you should avoid thinking of classes as a sub-resource or attribute of a student. An academic class is more than just a time slot on a student's schedule; it has an instructor, a syllabus, etc., all of which may need to be encoded at some point.

As I see it, the following relations hold:

• schools have zero or more students
• schools have zero or more classes
• students have zero or more classes
• classes have zero or more students

(You could also trivially extend these with teachers/instructors, if your requirements included such information.)

In addition, each of the above resource types will have any number of attributes beyond the simple links between them.

Given that, I would think you'd want a URL structure something like the following:

• http://example.com/lms/schools => list of schools
• http://example.com/lms/schools/{school} => info about one school
• http://example.com/lms/schools/{school}/students => list of students
• http://example.com/lms/schools/{school}/students/{student} => info on one student
• http://example.com/lms/schools/{school}/students/{student}/courses => list of courses (as links, not full resources) student is enrolled in
• http://example.com/lms/schools/{school}/courses => list of courses
• http://example.com/lms/schools/{school}/courses/{course} => info on one course
• http://example.com/lms/schools/{school}/courses/{course}/students => list of students (as links, not full resources) enrolled in course