topic

Attribute HTTP-EQUIV

META-tagi With attribute HTTP-EQUIV are equivalent to HTTP-headings. Usually they operate actions of browsers and can be used for perfection of the information which are given out by usual headings. Tagi such form can give the same effect, as HTTP-headings, and on some servers HTTP-headings can be automatically translated in the present{true} HTTP-heading.s are described in RFC1945 (HTTP/1.0) and RFC2068 (HTTP/1.1).

HTTP-headings can be generated with the help of CGI-scripts. Apache servers and CERN allow to make it. In other servers other mechanisms of generating of headings can be used. Some fields of headings generated by the server cannot be changed by values from META-tagov (in particular Date), others are substituted only at an abnormal status - code (<> 200). When the heading is not clear, value of HTTP-heading prevails of value META-tagov.

Expires

Sources: HTTP/1.1 (RFC2068)

Date of obsolescence. Management of caching in HTTP/1.0. In Netscape Navigator it looks as follows: if the specified date has passed, the next search of this document causes repeated network search, instead of podgruzku the document from a cache. Date with value "0" is interpreted as "now". Such value forces a browser each time at search to check - whether this document changed. It, by the way concerns and to proxies - agents. Search robots can or not index at all such document, or constantly "sniff" at it{him}.

Date should be set in a format described in RFC850,

That is equivalent to HTTP-heading

Expires: Wed, 26 Feb 1997 08:21:57 GMT

Pragma

The control of caching for HTTP/1.0. Value should be "no-cache." very useful container, I always use it{him} at delivery of results of job of any script.

Content-Type

Sources: HTTP/1.0 (RFC1045)

The instruction{indication} such as the document. Can be expanded with the instruction{indication} of the coding of page (charset). If to specify charset in maintenance{contents} META-taga Netscape Navigator deduces such page already in set charset. However be accurate, if the text of page in coding Windows, and value charset=KOI8-r, any forces the user cannot change encoding to see normal words!

Content-language

Sources: HTTP/1.0

The instruction{indication} of language of the document. It can be used by search machines at indexing pages. The combination of field Accept-Language (sent by a browser) with contents Content-language can be a condition of a choice the server of this or that language.

That is equivalent to HTTP-heading

In recently left specification HTML 4.0 other opportunity of the obvious instruction{indication} of language - <html lang = "en"> has appeared

Content-language: en-GB

Language is described by pair values (language - dialect). In an example: the English - Great Britain

Refresh

Sources: Netscape

Definition of a delay in seconds after which the browser automatically updates the document. An additional opportunity - automatic loading of other document.

That is equivalent to HTTP-heading

Refresh: 3; URL=http: // www.name.com/page.html

In Netscape Navigator it gives the same effect, as pressing button Reload.

Window-target

Sources: Jahn Rentmeister

Defines{Determines} a window of the current page; can be used for the termination{discontinuance} of occurrence of new windows of a browser at application of frame structures. Operates for many (but not for all) browsers.

That is equivalent to HTTP-heading

Window-target: _top

Ext-cache

Sources: Netscape

Defines{Determines} a name of an alternative cache for Netscape Navigator

PICS-Label

Platform-Independant Content rating Scheme. it is usually used for definition of a rating "vzroslosti" (adult) maintenances{contents} (sex, violence...):-)) however it is rather floppy circuit and it can be used for other purposes.

Cache-Control

Sources: HTTP/1.1

Defines{Determines} actions of a cache in relation to the given document. Possible{probable} values:

* Public - the document kehshiruetsja in accessible to all caches

* Private - only in a private{an individual} cache

* no-cache - cannot be kehshirovan

* no-store - can be kehshirovan, but it is not saved

Vary

Sources: HTTP/1.1

Defines{Determines} accessible alternatives for specified in CONTENT fields of HTTP-heading.

That is equivalent to HTTP-heading

Vary: Content-language

Lotus

Lotus-editors generate own fields Bulletin-Date and Bulletin-Text attributes. Bulletin-Text contains the description of the document

Attribute NAME

META-tagi With attribute NAME are used in cases when fields do not correspond with HTTP-headings. Sometimes clearness is lost: some agents can interpret tag "Keywords" described as NAME, others - as HTTP-EQUIV

Robots

Sources: Spidering

Management of indexation of page for search robots.

Possible{Probable} values:

* ALL

* NONE

* INDEX

* NOINDEX

* FOLLOW

* NOFOLLOW

Description

Sources: Spidering, Altavista, Infoseek

The brief summary of the maintenance{contents} of the document. It is used by search engines for the description of the document. This tag is strongly useful in cases when in the document there is not enough text when it is the manager of frames a file (frameset) or in the beginning of the document scripts are used. Length of the text up to 100 symbols.

Keywords

Sources: Altavista, Infoseek

It is used by search engines for indexing the document. Usually here synonyms to words in heading (title) or alternative heading are specified. Length of the list up to 1000 symbols. Use of the same keyword more than 7 times is not supposed, search engines will simply ignore this word.

Document-state

Sources: Spidering

Management of indexation of page for search robots. Defines{determines} frequency of indexation - or once to index, or reindeksirovat` the document on a regular basis.

Possible{Probable} values:

* Static

* Dynamic

URL

Sources: Spidering

Management of indexation of page for search robots. Defines{determines} frequency of indexation - or once to index, or reindeksirovat` the document on a regular basis.

Author

Sources: HTML editors

The name of the author, format any is usual.

Generator

Sources: HTML editors

The name and the version of the editor with which help this page is created is usual. Can be used for definition of a share of the market borrowed{occupied} with that or other product.

Sources: HTML editors

The description of copyrights to the document in an any format is usual

Distribution

Possible{Probable} values

* global

* local

* iu (internal use)

Resource-type

The current status of the given file. It is important for search engines, i.e. if his{its} value document the search engine starts his{its} indexing.

Other

* Classification

* Formatter

* Site-languages

* Version

* Template

* Operator

* Rating

* Creation

* Host

* Document

* Subject

* Build

* Random text (<META NAME = " Joe Smith ">)

Besides listed more or less standard tagov there is still a set of others specialized, for example, for the concrete search machine tagov.

Tag LINK

Tag LINK gives the document a method of definition of the attitude{relation} of the given document independent of Wednesday to other documents and resources of the Network. It is used with arguments REL and REV. With the help taga LINK it is possible:

* To create in the document special navigating buttons or the menu

* To operate process of display of set HTML of files in printed documents

* To adhere such associated resources, as tables of styles and scripts

* To give alternative forms for the given document

Where http://www.name.com/help.html - page of the help under the given document.

Attributes REL and REV can be used also with tagom A. Tagi LINK can be used only in heading of the document (head)

Attribute REL

HTML 3.2 REL-tagi

top, contents, index, glossary, copyright, next, previous, search

Some from recommended types of interrelations:

rel=top

The given communication{connection} specifies top in a certain hierarchical structure, for example on the first, or a home page in a certain set of documents.

rel=contents

The given communication{connection} specifies a certain file where the table of contents is resulted in the given document.

rel=index

The given communication{connection} specifies other document which can be used with a view of index search under the current document.

rel=glossary

The given communication{connection} specifies a certain document where the glossary of the terms concerning to the current document contains.

rel=copyright

The given communication{connection} refers to the text where copyrights to the given document are specified.

rel=next

The given communication{connection} specifies the following document in the certain beforehand predetermined route of viewing. For example, she can be used for anticipatory automatic loading by a browser of the following page.

rel=previous

The given communication{connection} refers to the previous document in the certain predetermined route of viewing.

rel=help

The given communication{connection} specifies the document offering{suggesting} a certain help, for example it can be the text giving more developed{unwrapped} description and offering{suggesting} the links to other documents on this subject. Purpose{appointment} of this communication{connection} - rendering assistance to those readers who has lost the way in Web.

rel=search

The given link conducts to the search page supervising a certain set of pages, connected by the general{common} subject.

Many systems invent the additional values of arguments REL and REV

Tag Schema

This tag contains URL a document - pattern. Action of all metadata from a document - pattern will be distributed on the document with tagom Schema (so works Dublin Core).

ViewCall REL-tagi

home, bookmark, tickertape, vmail, icon, prefetch, keyn, fastxx

AOLpress REL-tagi

AOLpress uses a little additional, in comparison with HTML 3.2, tagov

Home, ToC, Index, Glossary, Copyright, Up, Next, Previous, Help, Bookmark, First, Last

Attribute REV

It is used in design LINK for indication of a return parity{ratio} of documents.

Where the current page is page of the help for the document http://www.name.com/index.html

Use <LINK rev=made href = "mailto:document-owner"> in case of use Lynx will call automatic sending mail to the address document-owner.

Tag BASE

This tag defines{determines} base URL address which then will be used for redefinition of relative addresses for the given document. Tag BASE it is useful, if the document can be copied in other place or is requested on other way with use of the symbolical link, or a redirect with imagemap, etc.

Keywords for beginning{starting}

In this clause{article} it would be desirable to pay attention "keywords". Though this meta-tag also is one of the most insignificant elements by optimization of a site, nevertheless it is not necessary to forget about him.