Re: [opencog-dev] Re: Best texbook (most relevant to Opencog Node and Link Types) in Knowledge representation

Hi Linas, How do you propose to learn an ontology from the data -- also, what purpose would, in your opinion, the learned ontology serve. Or stated differently, in what way are you thinking to engender higher-level cognitive capabilities via machine learned bundled neuron (and implicit

Re: [opencog-dev] Re: Best texbook (most relevant to Opencog Node and Link Types) in Knowledge representation

On Tue, Apr 18, 2017 at 3:22 PM, Alex wrote: > Maybe we can solve the problem about modelling classes (and using OO and > UML notions for knowledge representation) with the following (pseudo)code > > - We can define ConceptNode "Object", that consists from the set or >

Re: [opencog-dev] Re: Best texbook (most relevant to Opencog Node and Link Types) in Knowledge representation

Hmmm... Instead of *** - We can require that any instance is inherited from the concrete class: ExtensionalInheritanceLinks invoice_no_2314 VATInvoice *** I would think to say MemberLink invoice_no_2314 VATInvoice DefiniteLink invoice_no_2314 (where the latter indicates

[opencog-dev] Re: Best texbook (most relevant to Opencog Node and Link Types) in Knowledge representation

Maybe we can solve the problem about modelling classes (and using OO and UML notions for knowledge representation) with the following (pseudo)code - We can define ConceptNode "Object", that consists from the set or properties and functions - We can require that any class e.g. Invoice is the