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:Michael Priestley (mpri@ca.ibm.com)
Date:Oct 1, 2004 9:12:01 am
List:org.oasis-open.lists.dita

Eliot wrote:

"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.

I don't understand. Does "document type" imply a particular syntactic expression? Its use in the XHTML specification certainly implies that it can be used for either schemas or DTDs, in exactly the manner we want.

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.

I'm not convinced that "document type" is any more wedded to syntactic expression, and it has the advantage of already meaning exactly what we want it to mean.