Difference between User's attributes and general attributes

Permalink
Hi,

We are developing a job posting package and will be having customisable attributes. For example some clients will want to show salary, location etc. Some might not.

We are reverse engineering the Users' model for this and notice that this method uses some sort of stand-alone attributes model just for users. Why is this?

What makes Users attributes more important than the general attribute api?

Thanks