XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Why does XML call them "attributes" and not name-valuepairs?

Aristotle would have recognised the concept of an attribute, if not its English name, and the term is universally used in data modelling discussions ("entity - relationship - attribute").

Your dictum "don't invent some artificial name" hardly applies, because the term "attribute" is very ancient and well-established. And it doesn't really address the issue: when naming an invented concept, there is always a tension between using a word that means something similar, but not quite the same, in another domain, and inventing a new term. Computing is responsible for many monstrous abuses of terminology, like using the term "real" for numbers that are actually rational, or "function" for something that can have side-effects. Naming of new concepts really depends on whether you want to emphasise the similarities to existing known concepts, or whether you want to emphasise the differences.

Michael Kay
Saxonica

On 15 Jan 2022, at 12:42, Roger L Costello <costello@mitre.org> wrote:

Hi Folks,
 
Someone once told me:
 
               Call it what it is.
               Don’t invent some artificial name.
 
The items in yellow:
 
<Person name="John Doe" employer="Acme Inc." age="30">…</Person>
 
are name-value pairs. 
 
Why does XML call them “attributes”?
 
/Roger



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS