Hi Ely, On Tue, Dec 21, 2021 at 8:04 PM Ely Matos <[email protected]> wrote: > > Hi! > > Still learning (and testing) about sheaf theory. I’m wondering if it is > possible to have a “unidirectional” connections or if this is against the > theory.
Yes, one can have a non-directional connection rule. The connection rules can also be arbitrarily complicated. There's an example in https://github.com/opencog/generate/blob/master/examples/trisexual.scm > For example, if I have an “ontology” with one type “Entity” and many types > that are children (is-a) of Entity. Is it possible to specify that each > children has a connector What are you trying to do? In basic conventional opencog, there's none of this sheaf stuff, and instead one has assorted relations for very conventional types of knowledge representations. Usually people do is-a relations with InheritanceLink (Inheritance (Concept "animal") (Concept "thing")) and so on. See e.g. https://github.com/opencog/atomspace/blob/master/examples/pattern-matcher/recursive.scm and more generally (Evaluation (Predicate "some relation") (List (Concept "a")(Concept "b"))) > (Connector (Concept "Entity") (ConnectorDir "*")) > > But do NOT specify a connector in Entity? So, if I have many instances of > Entities each one can connect just with one child. If I specific a connector > for each child in Entity, the same instance could be used by many different > instances of children and I don’t want this. I can't answer your question because I don't know what you are trying to do. The Connectors are meant for breaking things up into pieces, and reassembling them. Most people, when they work with ontologies, are not interested in breaking them nor reassembling them. At any rate, Merry Christmas! --linas -- You received this message because you are subscribed to the Google Groups "opencog" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/opencog/CAHrUA34akZ8arG%2Bjd3xtxg8sfs8ynk7ULUiik1Qcay-x-Z1k_w%40mail.gmail.com.
