RECOMMENDATION: Use 'labeled fields' rather than records when talking about labeled fields

[Evan Laforge]

On Wed, Feb 24, 2010 at 11:03 AM, John Meacham <john at repetae.net> wrote:
> This isn't so much a proposal as a recommendation for terminology we use
> when talking about things on the list and proposals in general. Calling
> haskell's labeled field mechanism 'records' leads to all sorts of
> confusion for people that come from other languages where 'records'
> means something else, this is compounded by the fact there are several
> actual record proposals out there that are orthogonal to labeled fields,
> but calling fields 'records' confuses this issue.

Just out of curiosity, what are the attributes associated with
"labeled fields" and what are the ones associated with "records"?