atom feed16 messages in org.oasis-open.lists.ditaRe: [dita] proposal on "vocabulary" t...
FromSent OnAttachments
Erik HennumSep 26, 2004 9:09 am 
Michael PriestleySep 28, 2004 8:55 am 
Michael PriestleySep 28, 2004 8:55 am 
W. Eliot KimberSep 29, 2004 6:49 am 
Michael PriestleySep 30, 2004 8:14 am 
JoAnn HackosSep 30, 2004 11:24 am 
Michael PriestleySep 30, 2004 12:08 pm 
Erik HennumSep 30, 2004 2:39 pm.gif, .gif, .gif, 8 more
Deborah Aleyne LapeyreSep 30, 2004 5:13 pm 
W. Eliot KimberOct 1, 2004 6:32 am 
Robin CoverOct 1, 2004 8:12 am 
Michael PriestleyOct 1, 2004 8:23 am 
Michael PriestleyOct 1, 2004 9:12 am 
Esrig, Bruce (Bruce)Oct 1, 2004 9:13 am 
Michael PriestleyOct 1, 2004 9:34 am 
Robin CoverOct 1, 2004 11:09 am 
Subject:Re: [dita] proposal on "vocabulary" terminology
From:W. Eliot Kimber (ekim@innodata-isogen.com)
Date:Oct 1, 2004 6:32:41 am
List:org.oasis-open.lists.dita

JoAnn Hackos wrote:

Is there a reason that we cannot use "document type" except for an intrusion into the DTD world? I think information developers and architects are more likely to understand the term "doc type" rather than a more esoteric term like "vocabulary"? I'd like to err on the side of usability and user-centeredness if possible. JoAnn

"document type" is certainly the most accurate if you take it to mean "abstract document type" (that is, a set of types distinct from any implementation expression of them) but I think that most people don't make that distinction, especially people like many of us with deep SGML brain damage, where there was no obvious need to distinquish between the abstract document type and its syntactic expression.

That's one reason I prefer "vocabulary"--it's completely (and in the namespace spec, explicitly) divorced from any particular syntactic or formal definition or expression of the vocabulary.

Cheers,

E.

eli@innodata-isogen.com www.innodata-isogen.com