RFC 3659:Extensions to FTP
RFC-Ref

semantic


Click on the red underlined text to get to the source

... Notice that with TYPE=A the SIZE command reports an extra 112 octets. Those are the extra octets that need to be inserted, one at the end of each line, to provide correct end-of-line semantics for a transfer using TYPE=A. Other systems might need to make other changes to the transfer format of files when converting between TYPEs and MODEs. ...


... by the server for any purpose that suits it. Clients implementing this specification should not assume any semantics for such names. ...
... + There are no defined "magic" names, like ".", ".." or "C:". Servers may implement such names, with any semantics they choose, but are not required to do so. ...
... + TVFS imposes no particular semantics or properties upon files, guarantees no access control schemes, or any of the other common ...


... Where TVFS is not supported, the only defined semantics associated with a "type=cdir" entry are that, provided the current working directory of the server-PI ...
... that reside in this directory can be renamed. This is a consequence of the UNIX semantics of the directory that contains them being modifiable. ...


... which must conform to the syntax of a token as given in this document, and a specification of the semantics to be associated with the particular fact and its values. Upon receipt of such an application, and if the combination of OS name and OS specific fact ...
... which must conform to the syntax of a token as given in this document, and a specification of the semantics to be associated with the particular fact and its values. Upon receipt of such an application, and if the combination of OS name and OS specific file type ...



Google
Web
RFC-Ref