RE: Semantic Event Systems

Mark,

Thank you for indicating the Gist ontology, e.g., "gist:Event".
As interesting, my current sketches of semantics-enhanced software event sources and listeners are available in the Nifty project (https://github.com/AdamSobieski/Nifty).
Here is a hyperlink to a relevant section of source code: https://github.com/AdamSobieski/Nifty/blob/19037dca00ff74a75b8d53abc47fc8498963f906/Nifty/Nifty.cs#L200 . Note: on line 209, a triple is constructed by passing arguments to a factory method using a predicate-subject-object sequence instead of a subject-predicate-object sequence.
Semantics-based approaches to software events (and messages) are flexible and extensible. Benefits of semantics-based approaches to software events (and messages) include that listeners could, beyond subscribing to events (or messages) based on their types, utilize semantic queries to further describe those events (or messages) of interest. This could be performed between software components on the same computing device or between software components across computing devices.


Best regards,
Adam

From: Mark Wallace <mark.wallace@semanticarts.com>
Sent: Tuesday, May 10, 2022 8:34 AM
To: Adam Sobieski <adamsobieski@hotmail.com>; semantic-web@w3.org
Subject: RE: Semantic Event Systems

"Gist" is a small but general ontology that includes gist:Event as a top-level concept.
See
https://www.semanticarts.com/gist/
and
https://ontologies.semanticarts.com/o/gistCore.ttl
Very respectfully,
-Mark Wallace

From: Adam Sobieski <adamsobieski@hotmail.com<mailto:adamsobieski@hotmail.com>>
Sent: Thursday, May 5, 2022 4:28 AM
To: semantic-web@w3.org<mailto:semantic-web@w3.org>
Subject: Semantic Event Systems

Semantic Web Interest Group,

Hello. I write, today, about ontologies describing events in the sense of computer software, where software objects can produce, or raise, events and other software objects can subscribe to consume, to receive, or to listen to, these events.
Here is a C# example of a semantic event system:


public interface IHasUri

{

    public Uri Uri { get; }

}



public interface IHasReadOnlyMetadataGraph : IHasUri

{

    public IReadOnlyMetadataGraph Metadata { get; }

}



public interface IEventSource : IHasReadOnlyMetadataGraph

{

    public Task Raise(Uri instance, IReadOnlyMetadataGraph data);



    public bool Subscribe(Uri category, IEventHandler listener);

    public bool Unsubscribe(Uri category, IEventHandler listener);

}



public interface IEventHandler

{

    public Task Handle(IEventSource source, Uri instance, IReadOnlyMetadataGraph data);

}

As one can see, event handlers can subscribe to and unsubscribe from event sources and can do so by specifying entire categories of, or types of, events which they are interested in.
As envisioned, there would be an ontology for these scenarios which would include a top-level type for events, various kinds of events, and relations between things and the events which they produce and consume.
I wonder, have others previously considered these ideas about semantic event systems? Are there any existing ontologies describing software events? Thank you.

Best regards,
Adam Sobieski