This subfield contains the host address. It is repeatable when there are more addresses available for one host.

It can contain the Internet Protocol (IP) numeric address if the item is an Internet resource (see examples 3, 4, 22), or a telephone number if dial-up access is provided through a telephone line (see examples 10, 17). This data may change frequently and may be generated by the system. A telephone number is recorded as follows: [country code]-[area code]-[telephone number], e.g. 49-69-15251140 (a number in Frankfurt, Germany), 1-202-7076237 (a number in the U.S., Washington, D.C.). If an extension is applicable, include it after the telephone number preceded by "x", e.g. 1-703-3589800x515 (a telephone number with extension).

This subfield is used when special software is required for data decompression (see examples 1, 25, 31).

See examples.

The electronic name of a file is entered as it exists in the directory/subdirectory indicated in subfield d on the host identified in subfield a. Subfield Podpolje f may be repeated if a single logical file has been divided into parts and stored under different names (see example 8). In this case, the separate parts should constitute a single bibliographic item. In all other cases, a file that may be retrieved under different filenames contains multiple occurrences of field 856, each with it corresponding electronic name in subfield f. A filename may include wildcard characters (e.g. "*" or "?") if applicable, with a note in subfield z explaining how files are named. Filenames may be case sensitive for some systems.

This subfield may also contain the name of the electronic publication or conference (see example 19).

The Uniform Resource Name (URN) is entered representing the global uniform name not being dependent on the location.

The username or processor of the request is entered in this subfield (see example 16); generally the data which precedes the at sign "@" in the host address.

An instruction or command needed for the remote host to process a request (see example 16).

The lowest and highest number of bits of data that can be transmitted per second when connected to a host. The syntax for recording the number of bits per second should be: [Lowest BPS]-[Highest BPS] (see examples 10, 17). If only lowest given: [Lowest BPS]-. If only highest given: -[Highest BPS].

Used to record general-used passwords, and should not contain passwords requiring security (see example 18).

General-use logon/login strings which do not require special security (see examples 12, 29, 31).

The address or a contact person is entered for access assistance (see examples 3, 4, 9).

See examples 3, 7, 10, 13, 14, 15, 17.

For information, the operating system is entered used by the host specified in subfield a (see examples 10, 13, 17).

The portion of the address that identifies a process or service in the host (see example 14).

This subfield contains an identification of the electronic format type (e.g. text/HTML, ASCII, postscript, computer program – exe or JPEG). The information is designated for the end users to determine how data are transferred through a network and how they can be used or be read (e.g. what software or hardware is required for the file to be displayed). Text files can be transferred as character data which generally restricts the text to characters in the ASCI character set (i.e. the basic Latin script, digits 0-9, a few special characters, and most punctuation marks). Text files with characters outside of the ASCI set, or non-textual data (e.g. computer programs, image data) must be transferred using another file transfer mode, usually binary mode (see example 11). Electronic format type may be taken from lists such as registered Internet Media types (MIME types) (see example 24). Subfield is repeatable if an electronic resource is available in different formats at one electronic address (see example 41).

The settings used for transferring data are entered. Included in settings are:

The syntax of these elements is: [Parity]-[Number of Data Bits]-[Number of Stop Bits] (see examples 10, 17). If only the parity is given, the other elements or settings and their related hyphens are omitted (i.e. [Parity]). If one of the other two elements is given, the hyphen for the missing element is recorded in its proper position, i.e. [Parity]--[Number of Stop Bits] or [Parity]-[Number of Data Bits]-. The values for parity are: O (Odd), E (Even), N (None), S (Space) and M (Mark).

The size of the file is entered as stored under the filename indicated in subfield f. It is generally expressed in terms of 8-bit bytes. It may be repeated in cases where the filename is repeated and directly follows the subfield f to which it applies (see example 8).

See examples 4, 7, 10.

The URL is entered which provides data in standard syntax needed for the electronic access. With URL address the electronic item should be located using existing Internet protocols.

Field 856 is structured to allow for the creation of a URL from the concatenation of other separate 856 subfields. Within the COBISS system subfield u is used for generating a note on the access mode in the ISBD description; that is why this subfield is always entered when such a note is required.

The hours are entered that access to an electronic resource is available at the location indicated in this field (see examples 3, 4).

A control number of the record is entered in this subfield.

The information by cataloguers that is not suitable for library users (see example 1).

The access method when the first indicator position contains value "7". This subfield may include access methods other than the main TCP/IP protocols specified in the first indicator. The data in this subfield corresponds to the access schemes specified in Resource Locators (URL) (RFC 1738), a product of the Uniform Resource Identifiers Working Group of the IETF. The Internet Assigned Numbers Authority (IANA) maintains a registry of URL schemes and defines the syntax and use of new schemes.

Notes are entered that are suitable to be displayed for the library users (see examples 10, 26). Together with the date of the public note entry, the note about an URL address failure is also entered, namely in the following form: "E-resource at http:// … is not accessible (a date of the note entry)" (see example 40).

The more detailed information is entered concerning the part or aspect of the item that data in field 856 refers to (see examples 27, 37, 38, 39).