[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [tm-pubsubj-comment] Subject-Oriented Applications
[BV] > > -- A subject-oriented application is any document, language, software, technology, system > > ... using abstract representations of subjects (e.g. called topics) as fundamental > > objects. [Murray] > Yikes. Now you need to define "abstract representations of subjects" > as well as "fundamental objects." This trail leads off into a jungle. Agreed. I didn't pretend this definition proposal to be complete, effective and accurate. Just an attempt in this direction. > I understand the desire to extricate "topic maps" from these > definitions, but I don't see that "subject-oriented application" > is really an improvement, since it's too vague. Are topic maps > "subject-oriented"? Is Encarta "subject-oriented"? I would tend > to define these things in terms of what they *are* not how they > might be used, and hence avoid needing to define the application > at all. So - what do you suggest? Bernard
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC