Instances of :FunctionSelector can have the following properties:
| PROPERTY | TYPE | DESCRIPTION | RANGE |
|---|---|---|---|
| From class :FunctionSelector | |||
| :byteSignature | owl:DatatypeProperty | A function can be identified by its byte signature. It is generated from the canonical signature. For example the Function `bar(uint32 x, bool y)` returns `(bool r)` has the canonical signature `bar(uint32,bool)`. The first 4 bytes of the Keccac 256 hash of this forms the byte signature of the function, in the example that would be `0xcdcd77c0`. | xsd:hexBinary |
| :canonicalSignature | owl:DatatypeProperty | The signature of the function in the canonical form which is used to create the functionSelector. Example: `bar(uint32,bool)` | xsd:string |
| 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 |
@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#> .
:FunctionSelector a owl:Class ;
rdfs:label "function selector"@en ;
ethon:suggestedStringRepresentation "FunctionSelector" ;
rdfs:comment "A function selector can be represented either by a canonical text form of the function signature (e.g. `exampleFunction(bytes32)`) or by its bytes form (e.g. `0xfc13a76a`). The latter is used by the EVM to call a certain function in a contract. It is created by taking the first 4 bytes of the keccac hash of the canonical text form of the signature."@en ;
ns:term_status "unstable" .