@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix mcr: <https://registry.apicrafter.io/vocab#> .
@prefix dt: <https://registry.apicrafter.io/datatype/> .
@prefix cat: <https://registry.apicrafter.io/category/> .
@prefix country: <https://registry.apicrafter.io/country/> .
@prefix tool: <https://registry.apicrafter.io/tool/> .

dt:ftp_reply_code a skos:Concept ;
    skos:inScheme <https://registry.apicrafter.io/> ;
    skos:topConceptOf <https://registry.apicrafter.io/> ;
    skos:notation "ftp_reply_code" ;
    skos:prefLabel "FTP reply code"@en ;
    skos:definition "Three-digit code with which an FTP server answers a command (RFC 959). The first digit, 1 to 5, says whether the reply is preliminary, a completion, intermediate, a transient failure or a permanent failure. The second digit, 0 to 5, gives the group, such as syntax, connections or the file system. HTTP and SMTP codes have the same form, so use the field name or context."@en ;
    skos:prefLabel "Код ответа сервера FTP"@ru ;
    skos:example "220" ;
    skos:example "226" ;
    skos:example "331" ;
    skos:example "550" ;
    mcr:status "draft" ;
    mcr:isPII false ;
    mcr:classification "categorical" ;
    mcr:regexp "^[1-5][0-5]\\d$" ;
    rdfs:seeAlso <https://www.rfc-editor.org/rfc/rfc959> .