> I think a user expects to see a "Experience" field, and an "Academic" field.
We can make 3 different lists with different domains in the view and have the same table in the db.
> Same for a resume report: you expect them to be in separate sections.
They are in separate section in the report.
> Also, the fields needed to describe "Academic" and "Experience" are quite
> different, so there's also no rationale there for having them on the same
> table.
Well, in fact, they are not so different. They share a lot of common fields.
You can see this solution as the same used for Partner, Contact and Address...
> I think a user expects to see a "Experience" field, and an "Academic" field.
We can make 3 different lists with different domains in the view and have the same table in the db.
> Same for a resume report: you expect them to be in separate sections.
They are in separate section in the report.
> Also, the fields needed to describe "Academic" and "Experience" are quite
> different, so there's also no rationale there for having them on the same
> table.
Well, in fact, they are not so different. They share a lot of common fields.
You can see this solution as the same used for Partner, Contact and Address...