:Event leaf node


Label

Event

Description

Events are structures implemented in smart contracts in order to create a LogEntry. Once created they cannot be accessed from the contract but can be used from the outside, e.g. by a web application that reacts to Events in a smart contract.

Usage

Instances of :Event can have the following properties:

PROPERTYTYPEDESCRIPTIONRANGE
From class :Event
:isAnonymous owl:DatatypeProperty Specifies if an Event is anonymous. Anonymous Events will not store the Event signature as the LogTopic of a LogEntry. xsd:boolean
:topic owl:DatatypeProperty An Event can be identified by its topic. It is generated from an abbreviated version of its signature. For example the Event Foo(uint32 x, bool y) has the abbreviated signature Foo(uint32,bool). The Keccac 256 hash of this forms the event topic. xsd:hexBinary
From class owl:Thing
:EthOnContractsDataProperty owl:DatatypeProperty Groups all EthOn Contracts extension Data Properties. owl:Thing
:EthOnContractsObjectProperty owl:ObjectProperty Groups all EthOn Contracts extension Object Properties owl:Thing
dc:contributor owl:AnnotationProperty -- owl:Thing
dc:creator owl:AnnotationProperty -- owl:Thing
dc:title owl:AnnotationProperty -- owl:Thing
ethon:suggestedStringRepresentation owl:AnnotationProperty -- owl:Thing
http://purl.org/dc/terms/isRequiredBy owl:ObjectProperty -- owl:Thing
ns:term_status owl:AnnotationProperty -- owl:Thing
vann:preferredNamespacePrefix owl:AnnotationProperty -- owl:Thing
vann:preferredNamespaceUri owl:AnnotationProperty -- owl:Thing

Implementation

@prefix : <http://ethon.consensys.net/Contracts/> .
@prefix ethon: <http://ethon.consensys.net/> .
@prefix ns: <http://www.w3.org/2003/06/sw-vocab-status/ns#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .

:Event a owl:Class ;
    rdfs:label "Event"@en ;
    ethon:suggestedStringRepresentation "Event" ;
    rdfs:comment "Events are structures implemented in smart contracts in order to create a LogEntry. Once created they cannot be accessed from the contract but can be used from the outside, e.g. by a web application that reacts to Events in a smart contract."@en ;
    ns:term_status "unstable" .