When viewing a topic the Raw Text link can be clicked to show the text of a topic (ie: as seen when editing). This is done by adding raw=on to URL. raw=debug shows the meta data as well as the topic data, ex: debug view for this topic

When viewing a topic the Raw Text link can be clicked to show the text of a topic (i.e., as seen when editing). This is done by adding raw=on to URL. raw=debug shows the meta data as well as the topic data, ex: debug view for this topic

-- MikeMannix - 03 Dec 2001

-- MikeMannix - 03 Dec 2001
-- PeterThoeny - 10 Jan 2002

Appendix B: TWiki Meta Data

TWiki Meta Data

Additional topic data, not editable from main freeform text box, stored in META variable name/value pairs

Additional topic data, program-generated or from TWikiForms, is stored in META variable name/value pairs

TWikiMetaData uses META variables to store topic data that's separate from the main free-form content. This includes program-generated info like FileAttachment data, and user-defined TWikiForms info.

TWikiMetaData uses META variables to store topic data that's separate from the main free-form content. This includes program-generated info like FileAttachment and topic movement data, and user-defined TWikiForms info. Use META variables to format and display Meta Data.

-- MikeMannix - 02 Oct 2001

-- MikeMannix - 03 Dec 2001

TWiki Meta Data

Appendix B: TWiki Meta Data

-- MikeMannix - 02 Oct 2001

Topic data not editable from main freeform text box, stored in name/value META variable pairs

Additional topic data, not editable from main freeform text box, stored in META variable name/value pairs

TWikiMetaData uses META variables to store topic data that's separate from the main free-form content. This includes program-generated info like FileAttachment data, and user-defined Form Template info.

TWikiMetaData uses META variables to store topic data that's separate from the main free-form content. This includes program-generated info like FileAttachment data, and user-defined TWikiForms info.

• Format is the same as in TWikiVariables, except all fields have a key.
  • %META:<type>{key1="value1" [key2="value2" [...]]}%

• Format is the same as in TWikiVariables, except all fields have a key.
  • %META:<type>{key1="value1" key2="value2" ...}%

%META:TOPICMOVED{from="Codev.OldName" to="CoDev.NewName"

%META:TOPICMOVED{from="Codev.OldName" to="Codev.NewName"

Specifications

Meta Data Specifications

TOPICINFO

META:TOPICINFO

TOPICMOVED

META:TOPICMOVED

This is optional, exists if topic has ever been moved. If a topic is moved more than once, only the most recent TOPICMOVED meta variable exists in the topic, older ones are to be found in the rcs history.

This is optional, exists if topic has ever been moved. If a topic is moved more than once, only the most recent META:TOPICMOVED meta variable exists in the topic, older ones are to be found in the rcs history.

%META:TOPICMOVED{from="Codev.OldName" to="CoDev.NewName" by="talintj" date="976762680"}%

%META:TOPICMOVED{from="Codev.OldName" to="Codev.NewName" by="talintj" date="976762680"}%

TOPICPARENT

META:TOPICPARENT

FILEATTACHMENT

META:FILEATTACHMENT

FORM

META:FORM

FIELD

META:FIELD

Should only be present if there is a FORM entry. Note that this data is used when viewing a topic, the form template definition is not read.

Should only be present if there is a META:FORM entry. Note that this data is used when viewing a topic, the form template definition is not read.

• TOPICINFO

• META:TOPICINFO

• TOPICMOVED (optional)
• TOPICPARENT (optional)
• FILEATTACHMENT (0 or more entries)
• FORM (optional)
• FIELD (0 or more entries; FORM required)

• META:TOPICMOVED (optional)
• META:TOPICPARENT (optional)
• META:FILEATTACHMENT (0 or more entries)
• META:FORM (optional)
• META:FIELD (0 or more entries; FORM required)

• Future Development: There are numerous development directions and specific features to consider. A couple of obvious possibilities:
  • Rendering to formats other than tables: bullet lists, formatted body text;
  • Specifying templates to be used for rendering.

There no absolute need for meta data variables to be in a specific order, however, it does for the following reasons:

• Keep (form) fields in the order they are defined
• Allow diff command to give output in a logically sensible order

These could be done in other ways, but this adds complexity

• Order fields - definition could be read on each rendering (expensive)
• Diff - render data before doing diff, has something to offer, but not likely to be available for next TWiki release

There is no absolute need for Meta Data variables to be listed in a specific order within a topic, but it makes sense to do so a couple of good reasons:

• form fields remain in the order they are defined
• the diff function output appears in a logical order

The recommended sequence is:

So the order is:

• text of topic
• TOPICMOVED - optional
• TOPICPARENT - optional
• FILEATTACHMENT - 0 or more entries
• FORM - optional
• FIELD - 0 or more entries (FORM required)

• text of topic
• TOPICMOVED (optional)
• TOPICPARENT (optional)
• FILEATTACHMENT (0 or more entries)
• FORM (optional)
• FIELD (0 or more entries; FORM required)

Meta Data is rendered with the %META% variable. This is mostly used in the view, preview and edit scripts.

Meta Data is rendered with the %META% variable. This is mostly used in the view, preview and edit scripts.

Current support is fairly basic:

Current support covers:

There is currently no support for meta data for Plugins. However, the format is readily extendable and the Meta.pm code that supports the format needs only minor alteration.

At present, there is no Meta Data support for Plugins. However, the format is readily extendable and the Meta.pm code that supports the format needs only minor alteration.

Merged into TWikiMetaData - this topic to be rolled back.

TWiki Meta Data

Topic data not editable from main freeform text box, stored in name/value META variable pairs

Overview

TWikiMetaData uses META variables to store topic data that's separate from the main free-form content. This includes program-generated info like FileAttachment data, and user-defined Form Template info.

Meta Data Syntax

• Format is the same as in TWikiVariables, except all fields have a key.
  • %META:<type>{key1="value1" [key2="value2" [...]]}%

• Order of fields within the meta variables is not defined, except that if there is a field with key name, this appears first for easier searching (note the order of the variables themselves is defined).

• Each meta variable is on one line.

• \n (new line) is represented in values by %_N_ and " (double-quotes) by %_Q_%.

Example of Format

%<nop>META:TOPICINFO{version="1.6" date="976762663" author="PeterThoeny" format="1.0"}%
   text of the topic
%<nop>META:TOPICMOVED{from="Codev.OldName" to="CoDev.NewName"
   by="JohnTalintyre" date="976762680"}%
%<nop>META:TOPICPARENT{name="NavigationByTopicContext"}%
%<nop>META:FILEATTACHMENT{name="Sample.txt" version="1.3" ... }%
%<nop>META:FILEATTACHMENT{name="Smile.gif" version="1.1" ... }%
%<nop>META:FORM{name="WebFormTemplate"}%
%<nop>META:FIELD{name="OperatingSystem" value="OsWin"}%
%<nop>META:FIELD{name="TopicClassification" value="PublicFAQ"}%

Specifications

The current version of Meta Data is 1.0, with support for the following variables.

TOPICINFO

TOPICMOVED

This is optional, exists if topic has ever been moved. If a topic is moved more than once, only the most recent TOPICMOVED meta variable exists in the topic, older ones are to be found in the rcs history.

%META:TOPICMOVED{from="Codev.OldName" to="CoDev.NewName" by="talintj" date="976762680"}%

Notes:

• at present version number is not supported directly, it can be inferred from the RCS history.
• there is only one META:TOPICMOVED in a topic, older move information can be found in the RCS history.

TOPICPARENT

FILEATTACHMENT

Extra fields that are added if an attachment is moved:

FORM

FIELD

Should only be present if there is a FORM entry. Note that this data is used when viewing a topic, the form template definition is not read.

Recommended Sequence

There no absolute need for meta data variables to be in a specific order, however, it does for the following reasons:

• Keep (form) fields in the order they are defined
• Allow diff command to give output in a logically sensible order

These could be done in other ways, but this adds complexity

• Order fields - definition could be read on each rendering (expensive)
• Diff - render data before doing diff, has something to offer, but not likely to be available for next TWiki release

So the order is:

• TOPICINFO
• text of topic
• TOPICMOVED - optional
• TOPICPARENT - optional
• FILEATTACHMENT - 0 or more entries
• FORM - optional
• FIELD - 0 or more entries (FORM required)

Viewing Meta Data in Page Source

When viewing a topic the Raw Text link can be clicked to show the text of a topic (ie: as seen when editing). This is done by adding raw=on to URL. raw=debug shows the meta data as well as the topic data, ex: debug view for this topic

Rendering Meta Data

Meta Data is rendered with the %META% variable. This is mostly used in the view, preview and edit scripts.

Current support is fairly basic:

• Future Development: There are numerous development directions and specific features to consider. A couple of obvious possibilities:
  • Rendering to formats other than tables: bullet lists, formatted body text;
  • Specifying templates to be used for rendering.

Known Issues

There is currently no support for meta data for Plugins. However, the format is readily extendable and the Meta.pm code that supports the format needs only minor alteration.

-- JohnTalintyre - 29 Aug 2001

TWiki Meta Data

%META:TOPICINFO{author="MikeMannix" date="999188491" format="1.0" version="1.1"}% %META:TOPICPARENT{name="WebHome"}%

• TWiki Meta Data
  • • • Merged into TWikiMetaData - this topic to be rolled back.

TWiki Meta Data

Merged into TWikiMetaData - this topic to be rolled back.