project
- summary
- tutorial (2) (3)
(4) (5) (6) (7) (8) (9)
- usage (2)
technical
- reasoning
- two passes
- still tiny
- sitemaps
- variables
- accessibility
WAI SubSects
examples
- horizontal
- vertical
- tabbed (2)
- multi section
- printer style
links
- some hints
- faq&issues
- all features #
- about me
- our sitemap
- download
(C) 2004-10-12
Guido Draheim
How to get... meta variables
Just have a look the generated "*.html" files - you will see that the mksite.sh script has already generated a series of <meta> tags in the header block. Most of these automatic variables will pick up the names of the "Dublic Core" ontology of meta information which is a real internet standard. Some search engines like google may pick that information to enhance their results.
<meta name="formatter" content="mksite.sh" /> <meta name="DC.title" content="How to get... meta variables" /> <meta name="DC.relation.isFormatOf" content="tutorial9.htm" /> <meta name="DC.date.modified" content="2004-10-12" /> <meta name="DC.date" content="2004-10-12" /> <meta name="DC.relation.section" content="index.html" /> <meta name="DC.title.selected" content=" (9)" /> <meta name="DC.publisher" content="guidod" />
It is possible to add more such meta variables by adding pieces to your content text. Just mark them up with then name of the Dublin Core give it as markup. So, in order to override the "DC.publisher" and the "DC.date" you would add these two lines somewhere in your content text:
<publisher>Guido Draheim</publisher>
<date>2004-11-07</date>
That way one can memorize the last edit date in the document and also the last editor of the document. The automatic values would be the last modification time of the source file in the file system for edit date and the current login user as the being the publisher. This is mostly correct for home pages but it would be not if you share some doc files with collegues.
The list of current DC term values is as follows:
contributor date source language coverage identifier
rights relation creator subject description
publisher DCMIType
and a lot of these can take subcategories - the "date" parameter
can also be subdivided into "DC.date.issued", "DC.date.modified",
"DC.date.available", "DC.date.created" - and you can set each of
these by adding the subcategory inside the text with a colon-prefix
like this:
<date>created:2004-11-07</date>
<relation>isReplacedBy:OtherPage.html</relation>
None of these meta-tags will be copied as text content - they are
removed during generation of the content block, so they will be
only set as meta-variables in the header block. For more information
on the current Dublin Core terms, see
http://dublincore.org/documents/dcmi-terms/