| |
|
|
Term
|
Description
|
|
audit trail
|
Record-keeping within the document manager or publication system that allows an organization to prove to an auditing authority, usually a regulatory agency, that its documents have been handled as required by law.
|
|
document metadata
|
Metadata used to describe or categorize the content of a document or to define how it is used within the organization. Document metadata are usually needed in the WCMS application.
|
|
document type profile
|
A Hyper.Net descriptor that defines how a document of a specified content type should be transformed. Access to document type profiles is through the Hyper.Net Administration Console.
|
|
field mapping
|
The process of mapping a property from the content type profile (document metadata) into a publication metadata for use during the conversion process. Field mappings are defined in the wssFieldMapping.xml file located in the HyperNet folder on the transformation server.
|
|
front matter
|
All of the content in a structured document that occurs before the first topic. The front matter is itself represented by a topic, and is thus the first topic in the Rich Hypertext rendition of a publication.
|
|
HNXML
|
An intermediate, object-oriented description of source content authored in Word or a Word-compatible application. Rather than converting the content directly into page-oriented HTML pages as most conversion filters do—and which is difficult to convert intelligently into other markup formats—HNXML represents the content using objects like publication, table of contents, topic, etc. The HNXML contains all of the information needed to generate any XML-based markup, including HTML, WML, custom XMLs (any DTD) and SGML.
|
|
matcher
|
A matcher is a descriptor that tells Hyper.Net how to look for content in the document being converted. Style Matchers look for paragraph and character styles, Formatting Matchers look for specific formatting regardless of applied style and Pattern Matchers look for text patterns regardless of formatting or applied style. Pattern Matchers are created through the use of regular expressions to allow powerful wildcarding.
|
|
publication
|
A unique conceptual data object containing all of the converted topics and supporting binary elements associated with the various renditions belonging to a converted source document. A publication could contain an HTML file, a PDF rendition, a copy of the source file (source file rendition), a collection of hypertext topics (Rich Hypertext rendition), all images and binary items associated with the Rich Hypertext topics, a table of contents and an index.
|
|
publication metadata
|
Metadata used to describe an instance of a publication or to define how it will be transformed.
|
|
rendition
|
A publication component representing a specific converted format of the source document, for example, HTML, PDF, Flash and Rich Hypertext. A rendition is represented as a publication component that contains all of the elements associated with the format. This can include binary files (such as the PDF file itself), images embedded in HTML files, all of the files belonging to a native HTML export from PowerPoint, and the like.
|
|
revision marks
|
Markup in the Word or Word-compatible source file indicating where changes such as additions and deletions have been made in the text. The changes typically need to be approved or rejected before a document is printed or converted, otherwise the revision marks may be visible. Revision marks are produced with Word's Track Changes feature.
|
|
schema
|
A Hyper.Net descriptor that defines fine-grained transformation options, including how document structure should be detected. A schema can be used with multiple document type profiles.
|
|
subtraction matcher
|
A Subtraction Matcher is a Pattern Matcher that is applied to the text returned from a Style, Formatting or Pattern Matcher. The Subtraction Matcher text is used to identify text within the returned text and remove it before the text is published. Subtraction Matchers can thus be used to make small on-the-fly edits to text without having to make sweeping changes across large numbers of source files.
|
|
topic/Topic
|
In a Word-compatible source document, a topic is comprised of all content beginning with a section heading and ending with the last character before the next section heading, regardless of whether the next section heading is a sibling or subtopic. Within a publication, a Topic is a folder containing all data elements required to represent the topic, regardless of type. The Topic folder may include HTML files, aspx files, PDF files, images and other data.
|
|
transformation
|
The process of converting a source document into one or more target formats and publishing the results into a publication containing one or more renditions corresponding to the formats.
|
|
transformation request
|
When a source document is saved into SharePoint, a transformation request referencing the source document itself and containing all of the document's properties is created and sent to the Hyper.Net Request Queue on the Hyper.Net Transformation Server. The transformation request contains all information Hyper.Net requires to convert, publish and update the associated publication correctly.
|
|
transformer
|
A transformer is a compiled code module that handles the actual conversion and publication process for a source file. A transformer typically opens source files in Hyper.Net's "working" folder, pre-processes them as needed, calls any required conversion software, pre-processes the resulting output as needed and assembles the final data and metadata into a package that is published into the publication library.
|