- From: Paola Di Maio <paoladimaio10@gmail.com>
- Date: Tue, 2 Dec 2025 16:02:31 +0800
- To: 陳信屹 <tyson@slashlife.ai>, internal-aikr@w3.org
- Cc: W3C AIKR CG <public-aikr@w3.org>, public-s-agent-comm@w3.org
- Message-ID: <CAMXe=SrQy+PLv8F7kwFDKb+UuMXLpKVypMMvbuMpJ+3fjF5-+A@mail.gmail.com>
We must conduct due diligence and check out the literature/state of the art to make sure we do not overlook and plagiarize, even unintentionally, other people's work in this space A genuine contribution, worthy of funding, is novel and advances the state of the art and ackowledgeges prior art Much of research unfortunately is bluntly the opposite Unfortunately, funding institutions lack the capacity to evaluate the state of the art because..... entire ecosystems are built on malpractice. Evaluators who object to large consortia getting massive funds for fake projects are simply ejected from the evaluation system Below two pointers, and note that Peter PS is in this list, There is a vid from him in the link More due diligence follows Paola Patel-Schneider has contributed to discussions on semantic web standards and usability that are crucial for reliable knowledge interfaces supporting intelligent agents (Patel-Schneider, 2024). If including foundational theory and semantic web research is desired, Patel-Schneider’s work on OWL and semantics bridges KR theory and agent-oriented applications. Patel-Schneider, P.F. (2024). "Does the Knowledge Graph community care about semantics?" COST DKG Talk Series. https://research.cs.umbc.edu/kqml/papers/desiderata-acl/section3.3.html INTERNATIONAL JOURNAL OF COMPUTERS COMMUNICATIONS & CONTROL ISSN 1841-9836, 13(1), 117-128, February 2018. *Modern Interfaces for Knowledge Representationand Processing Systems Based on Markup Technologies* A. A. Mohammed Saeed, D. Dănciulescu https://scispace.com/pdf/modern-interfaces-for-knowledge-representation-and-3i2ld58n1u.pdf On Tue, Dec 2, 2025 at 2:43 PM Paola Di Maio <paoladimaio10@gmail.com> wrote: > Tyson, thank you for looking at the artefacts in development > It is great that you are finding it useful > > I am working on a bunch of artefacts and experimenting with ways this can > be built into agents!! > I am a bit wary of sharing because I would like to look for funding for > the deserving portions of this work > > You ask when am I going to publish - asap, as soon as I can free my hands, > but publishing does not > mean that it will not get plagiarized, pardon the sour rant. > > SOUR RANT BEGINS > *many academics regularly scour mailing lists to plagiarise other people's > work, including when it is already published, acknowledged and in use > There are a lot of academics who get funding for their own project and do > not even give credit > > Sad, and very frequent. My own original work in ontology, engineering and > emergency management has been plagiarized and submitted for funding *with > public funding agencies Including my PhD thesis. There are scores of > funded projects and published papers as deliverables of such funded that > cite other plagiarised papers that are copied straight out from other > published works. There are enemies among us. Nobody can afford to pursue > expensive legal battle to demonstrate that the academics so and so, in the > public unversities so and so that receive public funding from all > major public councils world wide are actually criminal organisations > END OF SOUR RANT > > I suppose posting to the internal mailing list is a good idea when sharing > novel artefacts. See internal mailing list address in cc > But all list members, including serial plagiarisers may also be on the > internal list. > I ll keep the roadmap reserved for the moment > > In the meantime, I have given it a preliminary DOI > 10.6084/m9.figshare.30760739 > > It would be great to continue to bounce in this direction > what I got from this exchange so far is > > 1. We need a new category *bubble in our concept map for KR interfaces *I > have already done some literature review and apparently Pater Patel S on > this mailing list did some work on this some 25 years ago, I have not had > time to summarize the state of the art. There are KR interfaces out there > to be gathered > > 2. In this CG we are creating some KR artefacts that can be used by > agents/models to establish ontological commitment *to refine and improve > the quality of the queries and possibly improve overall performance? *I > think so > > Do let us know how your test bed works but please explain it in plan > words?! > > I do have a couple more demos myself I can share..... er... > > PDM > > On Tue, Dec 2, 2025 at 11:20 AM 陳信屹 <tyson@slashlife.ai> wrote: > >> 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 08:03:15 UTC