[Date Prev] [Date Next] [Thread Prev] [Thread Next] Indexes: Main | Date | Thread | Author

RE: [Gzz] RE: [ba-ohs-talk] Fenfire, RDF (re "Towards a StandardGraph-Based...")

Title: Re: [Gzz]  RE: [ba-ohs-talk] Fenfire, RDF (re "Towards a Standard Graph-Based...")
Hi Sandy et al,
I'm just waiting for the download, it is rather large...
 Sandy said: 
First, from our perspective, we believe that a converged structural and behavioral model is required to bring context and coherence to the systems world. A context incorporates conventional software object-oriented semantics, however its model deals more precisely with knowledge through higher order cognitive constructs. These semantics are layered on top of a software object, one that employs inheritance, encapsulation and polymorphic language mechanisms. Approaching system development from a context information modeling perspective is particularly valuable for aligning complex and variable requirements, even across a multitude of organizations with different processes.
Couldn't most of this be said about *any* knowledge representation system written in an OO language? If I write a Java class called 'Concept', it incorporates OO semantics, (inheritance, encapsulation and polymorphic language mechanisms). If I give it an attribute 'name' with accessor methods, I've added a higher order cognitive construct...
So I'm not really getting an idea of what a 'context' (in this context ;-) actually is.
Would I be right in thinking the aims are something like those of Network Inference:
Now at 36%...
Topic maps is just one corner for such a converged world. At this time, let me introduce you to CoreSystem. Please download a comprehensive CoreSystem animated illustration from the following FTP site:

Or for the Mac:

You will probably be most interested in reviewing the Knowledge Space element of CoreSystem for a discussion of Topic Maps (frame 13).



> At 01:55 PM 3/8/2003, Sandy Klausner wrote:
>> A resource is context, whereas a topic is content.
> I would think that, technically speaking, resources are not topics, but
> they can be the subjects of topics, and, thus, treated as if they are topics.
> Now, a resource as context? And a topic as content?
> Please explain.
> ---------------------------------------------------------------------------
> XML Topic Maps: Creating and Using Topic Maps for the Web.
> Addison-Wesley. Jack Park, Editor. Sam Hunting, Technical Editor
> Build smarter kids globally to reduce the need for smarter bombs.