Composite and multi-valued attributes can be nested to any number of levels. Suppose we want to design an attribute for a STUDENT entity type to keep track of previous college education. Such an attribute will have one entry for each college previously attended, and this entry is composed of: college name, start and end dates, degree entries (degrees awarded at that college, if any), and transcript entries (courses completed at that college, if any). Each degree entry is formed of degree name and the month and year it was awarded, and each transcript entry is formed of a course name, semester, year, and grade. Design an attribute to hold this information. Use the conventions of Figure 7.5.

What will be an ideal response?

```

{ PreviousEducation ( CollegeName, StartDate, EndDate,

{ Degree (DegreeName, Month, Year) },

{ Transcript (CourseName, Semester, Year, Grade) } ) }

```