:hasFork


Label

has Fork

Description

Relates a protocol variant to a forked version of it. A fork in a protocol variant is a change of the rules for creating valid new blocks (the protocol). It is inverse functional because a forked protocol can have only one protocol variant it forked from. It is transitive because if a protocol C that was forked from protocol B that in turn was forked from protocol A, protocol C was also forked from protocol A. It is asymetric because if protocol A is forked from protocol B, B cannot be also forked from A. It is irreflexive because a protocol cannot be a fork of itself.

Usage

DOMAINPROPERTYRANGE
:ProtocolVariant :hasFork :ProtocolVariant

Implementation

@prefix : <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#> .

:hasFork a owl:AsymmetricProperty,
        owl:InverseFunctionalProperty,
        owl:IrreflexiveProperty,
        owl:ObjectProperty,
        owl:TransitiveProperty ;
    rdfs:label "has Fork"@en ;
    :suggestedStringRepresentation "hasFork" ;
    rdfs:comment """Relates a protocol variant to a forked version of it. A fork in a protocol variant is a change of the rules for creating valid new blocks (the protocol).

It is inverse functional because a forked protocol can have only one protocol variant it forked from. It is transitive because if a protocol C that was forked from protocol B that in turn was forked from protocol A, protocol C was also forked from protocol A. It is asymetric because if protocol A is forked from protocol B, B cannot be also forked from A. It is irreflexive because a protocol cannot be a fork of itself."""@en ;
    rdfs:domain :ProtocolVariant ;
    rdfs:range :ProtocolVariant ;
    rdfs:seeAlso <http://vitalik.ca/general/2017/03/14/forks_and_markets.html> ;
    rdfs:subPropertyOf :NetworkObjectProperty ;
    ns:term_status "unstable" .