- From: 陳信屹 <tyson@slashlife.ai>
- Date: Tue, 2 Dec 2025 11:19:57 +0800
- To: paoladimaio10@googlemail.com
- Cc: W3C AIKR CG <public-aikr@w3.org>, public-s-agent-comm@w3.org
To further explore this alignment, I’d like to propose using it as the first testbed use case within our CG. a small demo video that showcases how the Unified Ontic Ontology can ground the Agent Ontology in an executable environment. I don’t yet have a concrete idea for what the best showcase would be. perhaps something minimal that demonstrates Intent–Capability–Delegation flow in a verifiable way. I’d be happy to hear thoughts or suggestions from everyone on what kind of example could best illustrate the value of this alignment. 陳信屹 <tyson@slashlife.ai> 於 2025年12月2日週二 上午11:02寫道: > > Hi Paola > > I’ve been reviewing your Unified Ontic Ontology work. the > cross-mapping across BFO, DOLCE, SUMO, GFO, UFO and YAMATO is an > excellent unification of top-level categories. > > To explore its practical impact inside our Semantic Agent > Communication CG, I drafted a minimal alignment block that connects > the Agent Ontology (core modules: Agent, Intent, Capability, > Delegation …) to your Unified Ontic framework. This gives the Agent > Ontology a stable ontic frame. > > From the engineering side, this alignment allows the AgentIDL compiler > to automatically bind each interface (Intent, Capability, Delegation) > to its ontic category in Unified Ontic Ontology. This makes the > generated code semantically interoperable across domains. The same > AgentIDL interface can compile into different ontological environments > (BFO, DOLCE, SUMO) while preserving meaning. > > Concretely, we could use it not by importing the whole thing, but by > referencing key classes. > > Here’s the snippet (for review / discussion): > > ################################################################ > # Ontic Alignment — Unified Ontic Ontology > # (Light-weight mappings to BFO/DOLCE/SUMO/GFO/UFO/YAMATO families) > ################################################################ > > @prefix exu: <http://example.org/unified-ontic#> . > @prefix agent: <https://s-agent-comm.github.io/ontology/ontologies/agent#> . > @prefix intent: <https://s-agent-comm.github.io/ontology/ontologies/intent#> . > @prefix capability: > <https://s-agent-comm.github.io/ontology/ontologies/capability#> . > @prefix contract: > <https://s-agent-comm.github.io/ontology/ontologies/contract#> . > @prefix ledger: <https://s-agent-comm.github.io/ontology/ontologies/ledger#> . > @prefix delegation: > <https://s-agent-comm.github.io/ontology/ontologies/delegation#> . > @prefix security: > <https://s-agent-comm.github.io/ontology/ontologies/security-binding#> > . > @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . > @prefix owl: <http://www.w3.org/2002/07/owl#> . > > ################################################################ > # Core class alignments > ################################################################ > > agent:Agent a owl:Class ; > rdfs:label "Agent" ; > rdfs:comment "An autonomous computational entity with identity and intent, > modeled as a social artifact capable of delegation > and accountability." ; > rdfs:subClassOf exu:ArtifactSocial ; > exu:mapsTo "BFO:MaterialEntity->Artifact; DOLCE:SocialObject; > SUMO:Agent; UFO:SocialAgent" ; > rdfs:seeAlso <https://basic-formal-ontology.org/> , > <https://www.loa-cnr.it/DOLCE.html> . > > intent:Intent a owl:Class ; > rdfs:label "Intent" ; > rdfs:comment "A deliberative mental state or communicative > commitment of an agent." ; > rdfs:subClassOf exu:AbstractEntity ; > exu:mapsTo "BFO:GenericallyDependentContinuant; > DOLCE:Description/Proposition; SUMO:Intent; UFO:Intention" . > > capability:Capability a owl:Class ; > rdfs:label "Capability" ; > rdfs:comment "A realizable disposition or function that an agent > can exercise." ; > rdfs:subClassOf exu:FunctionDisposition ; > exu:mapsTo "BFO:RealizableEntity/Function; DOLCE:Capability; > SUMO:Capability; GFO:Disposition; UFO:Disposition" . > > contract:Contract a owl:Class ; > rdfs:label "Contract" ; > rdfs:comment "A social artifact representing binding obligations > between agents." ; > rdfs:subClassOf exu:ArtifactSocial ; > exu:mapsTo "DOLCE:SocialObject; SUMO:Agreement; UFO:SocialRelator" . > > ledger:Ledger a owl:Class ; > rdfs:label "Ledger" ; > rdfs:comment "A record artifact capturing accountable agent transactions." ; > rdfs:subClassOf exu:ArtifactSocial ; > exu:mapsTo "BFO:InformationArtifact; DOLCE:InformationObject; > SUMO:Document" . > > delegation:Delegation a owl:Class ; > rdfs:label "Delegation" ; > rdfs:comment "A social relation between agents defining authority > transfer or responsibility." ; > rdfs:subClassOf exu:RelationRelator ; > exu:mapsTo "BFO:RelationalRole; DOLCE:Relation; SUMO:Relation; > UFO:Relator" . > > security:ProofBinding a owl:Class ; > rdfs:label "ProofBinding" ; > rdfs:comment "A verifiable binding between identity, proof, and > execution context." ; > rdfs:subClassOf exu:DependentContinuant ; > exu:mapsTo "BFO:Quality; DOLCE:Quality; SUMO:Attribute" . > > ################################################################ > # Optional note > ################################################################ > > <https://s-agent-comm.github.io/ontology/ontologies/core#> > rdfs:comment "This ontology is ontically grounded via Unified > Ontic Ontology alignment, > enabling cross-compatibility with major upper > ontologies (BFO, DOLCE, SUMO, UFO). > The mapping ensures that computational agents are > modeled as social artifacts > with realizable capabilities, intentional states, > and relational accountability." . > > > By the way, do you have an estimated timeline for publishing or > finalizing the Unified Ontic Ontology (TTL version)? > I’d like to align the AgentIDL compiler’s ontic bindings with your > official release once it’s available. > > Paola Di Maio <paola.dimaio@gmail.com> 於 2025年11月28日週五 下午6:49寫道: > > > > Thinking of where would Tyson's agentic execution interface specification would sit in the diagram, *presumably in the KR Language/Formalism bubble? > > I have extracted captured in a table and a list of terms most ontic categories, which is going to be our first deliverable, > > please give feedback, help to improve/expand. > > > > Please request access to view > > https://docs.google.com/document/d/1OyZGVDCMozbAGPaKqYpUnWX75raGoCNpd6KJN3bMoFQ/edit?usp=sharing > > > > > > > > > > > > Please request access if you would like to give feedback
Received on Tuesday, 2 December 2025 03:20:12 UTC