Glossary

The glossary contains a useful list of concepts and definitions used by PageSeeder.

Created on 25 June 2010, last edited on 7 June 2024 at 18:15

A

Account activation: Account activation is an important security feature. It ensures the email address is valid and verifies who controls it.

Account lockout: A user account is locked automatically by PageSeeder after multiple consecutive failed sign-in attempts. While their account is locked, users cannot sign in. They must wait for the account lockout time to expire or contact an administrator to unlock their account.

Activity – group: Provides a list of the activities, sortable by the activity of members, including the following:

Administrator: A particular role with elevated permission to configure a PageSeeder server.

Ambiguous xref: See resolve references.

Ant task: Apache Ant tasks perform actions in a publish script.

Approver: The Approver role, has the highest level of permission within a group.

Archive: is a default folder in every group, and it is also a verb that describes a feature of the system. The folder is created by the system when the group is created. How the feature works is easier to understand with some background.

AsciiMath: A free, open-source project that supports the creation of MathML equations using a simple, plain text syntax and a standard web browser.

Assignee: The group member who is currently assigned a task or document workflow.

Author: The person who submitted a comment, version, note or edit to PageSeeder. In the user interface, PageSeeder displays a human-readable name to identify the author.

Authorization code: The authorization is a one-time use code that is issued by PageSeeder as part of a Single-Sign-On process or OAuth authorization code flow.

Auto-save: When editing a document, there is an auto-save feature that stores the current draft version of the fragment every few seconds after you stop typing.

B

Backup: Requires backing up both the file system and the database. The following folder can be excluded as it contains only temporary files:

Bastille: Bastille is a Java library which extends Berlioz to better integrate with PageSeeder and provide common functionalities for websites.

Batch (or “bulk”) processing: There are two ways to batch process PageSeeder documents through the user interface. One is using the search results, and the other is to configure a publish task to run at the folder level using the task config.

Berlioz: Berlioz is an open source Java library, written by the PageSeeder team to provide a simple developer framework that uses URI template notation to allocate services and XSLT for serving XML to the web as HTML. Although Berlioz can be used to serve any type of XML, it comes with native support for processing PageSeeder Markup Language (PSML) and includes the following infrastructure:

Block label: In PSML, a block label associates semantics to a block of text.

Block xref: A type of cross-reference that references content that is to appear as a standalone element. The different ways a block xref can be processed are the following:

Bridge: Open source library that simplifies the task of accessing the PageSeeder service API from Java or Kotlin applications. Bridge allows applications to support the following:

build.xml: the standard file object for the Ant API. For further information, see using Ant.

Built-in document types: PageSeeder comes preconfigured with three document types:

C

Cache-Control: There are multiple levels at which PageSeeder utilizes caching to improve performance. This entry is specifically oriented to HTTP caching.

Client ID: A unique identifier for an OAuth client.

Comment: A fundamental capability of PageSeeder, comments are a class of XLink that can be attached to different locations in the data or system. Because commenting is so integral to PageSeeder’s architecture, understanding how they work can help to explain the broader concepts.

Comment formatting: Comments posted by email or through the user interface are stored in plain text. However, to leverage the formatting capabilities of modern browsers, comments can include basic formatting through the use of the popular language, Markdown.

Comment ID: There is a unique system-wide generated identifier for every PageSeeder comment.

Component document: Do not have to be a specific document type, "component" reflects the role of the documents that are bound together by a references document to create a publication.

Content labels: Content labels are a class of label used to describe information inside PageSeeder documents. The two types of content labels: block label and inline label are analogous to the idea of paragraph and character styles in publishing or word processing systems, or to the HTML elements of <div> and <span>.

Context path: A location value used by several PageSeeder functions, mostly to do with importing or exporting data.

Copy: See duplicate.

CORS: Cross-Origin Resource Sharing (CORS) is an HTTP-header based mechanism that allows a server to indicate any origins (domain, scheme, or port) other than its own, from which a browser is to permit to load resources.

Cross-reference (xref): Also known as an xref.

Cross-reference (xref) label: A label attached to an xref.

D

Daily digest: Daily digest is a method of notification, allowing the member to keep up to date with the latest comments and discussion related to a group by receiving a single email once daily.

Date and time: Correctly understanding where the date and time are sourced and applied is important for getting the most out of PageSeeder. The orderly processing of edits or comments is critical to efficient collaboration, but it isn’t always straightforward with globally distributed group members.

Date picker: Common interface components such as a date picker can be added to PSML documents using a <properties-fragment>.

Default group setup: These are the settings used to initialize a group. They include the folder structure (documents, image, attachments and more) and files like the homepage.

Default template: The default template is a set of configuration files that are used by default for all projects.

Delete: In general, PageSeeder doesn’t encourage ‘deleting’. Even when it isn’t obvious by appearance, the PageSeeder XLink architecture means that most information objects are created by processing links to users, content and context.

Developer license: The developer license for PageSeeder allows developers to create unlimited projects, groups and members as long as they access PageSeeder through localhost or *.localhost only. This license is configured by setting the product key to ‘dev’ and website address to ‘localhost’ or ‘[x].localhost’.

Developer tools: A collection of tools and options included when the developer view is enabled.

Developer view: To keep the user interface straightforward for end users, PageSeeder provides a developer view (previously referred to as “Developer mode”), which when enabled, turns on additional features, tools and information specifically aimed at developers.

Discussion: A thread consisting of one or more related comments.

DITA: DITA is an XML standard for documentation and processing from OASIS. It shares some of the same architectural concepts as PageSeeder.

Document: PageSeeder terminology defines a document as anything that has a URI ID and is not a URL. This includes the following:

Document event: An event that occurred on a document, a document fragment or a URL.

Document history: Document history refers to the list of events that affected a PageSeeder document.

Document ID (or DocID): The PageSeeder server allows any document – PSML or binary – to be assigned a server-wide, unique identifier. This value is commonly referred to as the DocID and it has the same use case for both developers and end users. That is, the DocID is an alternative method to folder path and filename for locating a document, like a primary key.

Document info: documentinfo is one of the metadata containers for a PSML document (the other is fragmentinfo). See the metadata element reference for further detail.

Document label: Labels can be added to a PageSeeder document by the following:

Document metadata: A set of properties that can be attached to a document based on its document type or media type.

Document status: Assigning a status is a way of associating a group member with a document, a task and a date. The primary objective of the document status is to formalize lifecycle stages such as creation, review and release. Using the collaboration and reporting tools of PageSeeder, the document status can eliminate much of the overheads and inaccuracies associated with managing document lifecycles using spreadsheets and email.

Document template: A pre-configured structure and semantics defined as part of a document type.

Document title: Refers to a property of a document. All PageSeeder documents, regardless of their media type or content, have a Document title.

Document type: In PageSeeder, a document type can be compared to a ‘template’ in Word or FrameMaker. Document types are used to customize aspects of the content such as:

Document view: Refers to the display of a PSML (PageSeeder Markup Language) document.

DOCX: See Microsoft Word DOCX format and Open XML.

Download: In the document context, the download option allows any document to be saved locally in its native format.

Draft: PageSeeder auto-saves content that you type in the app as a draft, every few seconds after you stop typing.

Duplicate: Computer science has long discussed the issue of redundancy vs dependency and from time-to-time, it is a topic that arises in PageSeeder modeling.

E

Edit note: An edit note is a particular type of XLink (a note) attached to a specific change in a fragment (an edit).

Edit note label: Edit note labels are attached to a note made on a document edit.

Edit sheet: As the name implies, this is a hybrid of a spreadsheet and a conventional editor. Available from the search results, the Edit sheet makes it straightforward for users to open an entire folder of documents or binary objects and edit their metadata, properties, or filename. In the case of PSML documents, the Edit sheet also exposes fragment properties or inline labels for editing.

Editing – batch: PageSeeder provides the infrastructure necessary to support batch or bulk editing. Effectively, this process can be thought of as re-uploading PSML files. Therefore, batch editing can support use cases such as:

Export: Like download and publish, export is simply a meaningful name for publish scripts that use PageSeeder’s batch API. By default, PageSeeder comes with publish scripts that export to the following formats:

F

Faceted navigation: Faceted navigation is a methodology for organizing information to optimize navigation by values in the data.

File size: Size in bytes of PageSeeder documents.

File system: PageSeeder relies on the file system to store documents and binary files. For information about files managed by PageSeeder, see folders and files.

Filename: Whether it is a normal binary file, such as ZIP file, or an Office document, or a PageSeeder document, any file viewed in PageSeeder has both a filename and document title. However, because these files are physically stored on the file system of the host server, they mustn't have names that violate the naming rules of the host operating system.

FOConfig: also known as FO Config

Folder: As a term, ‘folder’ can be used in multiple contexts including the following:

Folder view: Also known as group documents page (or ‘Document browse’ in version 5).

Folders and files: Files and folders in PageSeeder can be used in multiple contexts. For general explanations, see the glossary entries for document or folder.

Forms: For information about the creation and editing of electronic forms or fielded data in PageSeeder, see the following documents:

Fragment: Documents in PageSeeder are composed of fragments.

Fragment identifier: A unique identifier for a fragment within a document. The fragment ID provides developers with a more precise mechanism for updating documents that have been created outside PageSeeder.

Fragment label: A label which applies to a fragment.

Fragment template: part of the document template.

G

Generator: A generator is a server-side component written in Java which produces an XML response from a content request. Berlioz libraries provide a number of built-in generators for common use cases.

Global template: The Global template (previously known as custom folder) is a custom project template that applies to all projects on the server. It is specified by the optional globalTemplate property in global properties.

Group: A key PageSeeder concept, the group restricts access to content, such as documents and comments to a list of members.

group config – advanced options: These settings can be found in Advanced Options on the group configuration page located under group administration. For more information about the API, see Service: edit-group.

Group configuration: Group configuration includes the group title, name, description. Advanced options are available, which include a welcome message for new members, and in the group properties form values can be configured for tasks, workflows, notification and index. These are available when the group (or project) is first created or can be accessed at any time by a manager of the group.

Group folder: Is an object that acts as a container for URIs in a group. All documents and folders belong to at least one group folder. Each group folder contains its own tree of documents and folders.

Group owner: Is a value used to cluster, or differentiate, groups. Typically the name of an individual or organization, the “owner” is visible through the projects and groups page under the system admin menu. The owner value is set through the advanced options tab of the group configuration option under the admin menu. See the following screens.

Group properties: Accessed by selecting Group configuration, under the Administration tab on the group dashboard page, these are values that control various aspects of group behavior such as whether returned email messages are forwarded to a nominated address. While these same values can be set at the project level, the rules of inheritance and overrides can prove confusing for new users. Group properties defined in the global template are used as the default for all groups.

H

Help document type: The help document type is a built-in document type to create help articles.

Host: In PageSeeder, a host is one of the attributes of group folder and URI. It must be a valid hostname as defined by RFC 3986.

HTML: A key component in PageSeeder, HTML is used to provide an editing interface for PSML documents.

HTTP servlet: An HTTP servlet is a server-side component that receives and responds to requests from clients to perform a particular task or retrieve data over HTTP.

I

ID token: An ID token contains claims that carry information about the user. Information in ID tokens let PageSeeder verify that a user is who they claim to be.

Image: Might refer to:

Image shell: This technique is no longer recommended. The preferred alternative is to create a media template that includes the relevant metadata using the <metadata> element instead.

Index XML: The index XML is the XML format used by the PageSeeder Index Engine as a source.

Inline label: Designed to associate custom styles or semantics to running pieces of content inside a text block (paragraph). Inline labels play the equivalent role for PageSeeder as “character” or “inline” styles play in traditional publishing or word processing systems.

Invitation: A two-step process to add someone to a group by sending them an invitation email – then they must confirm acceptance.

J

Java: Java is the language used to write much of the core of the PageSeeder application and the generators for any Berlioz application.

Java API: see Bridge.

Jetty: A servlet engine and HTTP server where most Berlioz apps are deployed.

L

Labels: Labels are a convenient mechanism for adding semantics to PageSeeder artifacts. They are divided in two broad categories:

License: PageSeeder is available under more than one license. What follows is the non-legal explanation of the different options.

List: In PageSeeder terminology, ‘list’ is interpreted as the generic description for ordered (<nlist>) or unordered (<list>) items (<item>) in a document, not as the programming term for a type of data structure.

Loading zone: The loading zone is a temporary location in the file system where files are stored before being uploaded into PageSeeder.

Logging: PageSeeder provides several types of logs for developers and administrators to assess the health of their system and diagnose problems.

M

Manager: A particular role with permission to configure a PageSeeder group.

Markdown: A simple, lightweight text-based language for formatting documents.

MathML: MathML is intended to facilitate the use and re-use of mathematical and scientific content on the Web. It is supported for display and storage in PageSeeder.

Media icon: To identify the media type of a document quickly, PageSeeder uses a consistent set of icons.

Media type: PageSeeder uses the media type of a document as a trigger to invoke document processors that have specific capabilities to process data formats such as XML or PDF.

Member: The groups that a user is a member of, determine the content they can see. The role attached to each specific group membership, determines the functionality the user has. Membership and role for any group is unrelated to what it might be on any other group.

Member – add/remove: Previous or pending members of a group are visible when a user with a role of manager or higher views the member list.

Member – registration: The process of joining a member to a group.

Metadata: The broad scope of PageSeeder has left some important terms with more than one meaning. “'document'”, “properties”, and “metadata” are all such terms. The uses of metadata are as follows:

Microsoft Excel: Is supported by PageSeeder in several different ways. The most common being the following:

Microsoft Word DOCX format: Support for converting PSML documents to DOCX and DOCX to PSML is a standard feature of PageSeeder. Available when viewing a document, there is a standard conversion that processes any PSML document without modification.

Moderated group: A group with the role of moderator assigned to a member. PageSeeder then directs different transactions to the nominated individual for approval. Transactions that can be moderated are: anyone applying to join the group or comments being posted to members.

Moderator: A manager who can accept or reject memberships and comments.

N

Name-value pair: A common data structure in computing, they are natively supported in PageSeeder. For further information, see property and PSML properties editor.

Notification: When certain events occur on the PageSeeder server, email notifications are sent to members. Who is notified and when depends on the options of the event and the notification settings for the member in a particular group.

Numbered headings: A numbered heading is a <heading> element in PSML which is preceded by an automatically generated number when published.

Numbered paragraphs: A significant amount of development effort has been invested to ensure that even the most complex numbering schemes can be supported in PageSeeder. In many cases, this is achievable with less effort than using Microsoft Word or similar applications and produces superior results. However, the issue of numbering can span the entire document lifecycle, which makes it hard to cover in a single article.

O

OAuth client: An external app using the PageSeeder API through OAuth.

OAuth scopes: When an app connects to PageSeeder using OAuth it acts as a PageSeeder member. In PageSeeder v6.1 and higher the app no longer has all the permissions that the member has but only those allowed by the scope specified for the app’s OAuth client. The scope consists of one or more scopes described in the following separated by spaces, for example: openid profile email.

Object labels: With no predetermined semantics, a label can be used for any purpose. The most fundamental difference for PageSeeder is whether the label is attached to an object, or part of the content. Native objects that support labels include document, fragment, comment, task, workflow, version or xref.

Object model: One of PageSeeder’s main design strengths is how quick and straightforward it can be to import, edit and publish complex XML documents. The reason for this is PageSeeder’s object model (see document) and how it is used to represent XML data in an easily editable, generic form.

Open XML: See Microsoft Word DOCX format.

Organization: An aspect of the service provider license that supports branding of the PageSeeder interface and messages, such as lost password and group invitations.

Overwrite: An option or setting which allows content to be replaced during an upload operation.

P

PageSeeder Ant API: A common requirement for PageSeeder is to process numerous files through multiple stages. To support this, a version of the PageSeeder API can be called from a batch processing environment, Apache ANT. This is the basis of PageSeeder publish.

PageSeeder design objectives: The PageSeeder approach to XML publishing workflows is different from that of conventional applications. PageSeeder was conceived and implemented as a web-based platform, not adapted from a desktop app. The orientation of the product has always been around collaboration and the constraints that are necessary to effectively and productively coordinate groups of users.

PageSeeder file system: Directly interacting with the host file system is not advised! Use the API or user interface to move files in or out of PageSeeder.

PageSeeder server: Is a somewhat ambiguous term. It can be the conceptual term for the overall PageSeeder solution or it can refer to the main software component of the system (and counterpart to the publish engine).

Paragraph style: A widely-understood concept that is part of most unstructured document editing and publishing apps. A style groups a collection of format settings under an arbitrary name so a user can apply the identical settings elsewhere.

Password: Passwords are required for all users to authenticate or access private groups.

PDF documents: PageSeeder stores, indexes, searches, and displays PDF documents. It can also create PDF format from PSML documents. See PDF export config usage.

Personal group: A personal group is a reserved PageSeeder group used as a private space for PageSeeder members to receive messages and store personal documents.

Placeholder: An inline <placeholder> element that displays the value of a metadata property directly in content. This allows content (text, date or datetime) to be edited in one location, but shown in multiple. Because the property can belong to the publication, the same component document can display different content in different publications.

Preferences: Personal preferences are stored in PageSeeder against the user’s account. They are accessible from the account Preferences page.

Priority: Defines the level of urgency or importance of a task or workflow.

Project: Fundamentally, a PageSeeder project provides the following two functions:

Project and group names: Only use lowercase alpha characters, numbers (top level project name can’t start with a number), underscore (_), or tilde (~) in your project or group names.

Project template: The project template is a set of files that configure the behavior of groups within a project.

Properties: Another PageSeeder term with multiple contexts, like ‘document’ and ‘metadata’.

PSML – PageSeeder Markup Language: PSML (PageSeeder Markup Language) is an XML markup language designed to represent a broad range of documents. It is natively supported by the components of the PageSeeder platform with no need for additional configuration. This includes the editor, publishing processes, validator, index/search engine and more.

Public: The conventional meaning for ‘public’ refers to an external, often anonymous, community. In PageSeeder, setting to ‘public’ means you provide access to people who are NOT registered to the same group – public just means we don't check for the group membership.

Public API support: Indicates the level of support of an HTTP servlet that is part of the public API for a particular usage.

Publication: A PageSeeder concept that was redefined with the release of version 5.96xx.

Publication config: Among other properties, this controls the way a “Publication” is numbered. The publication-config.xml is available through the Publication types tab, on the template configuration page.

Publication ID: A server-wide, unique value represented by a document property. Any document with a value in this field is displayed in the list of Group Publications.

Publish: A concept of batch processing in PageSeeder. Publish can mean exporting PageSeeder XML into non-PageSeeder formats such as PDF, DOCX or arbitrary XML formats. It can also mean importing Microsoft Word or Excel into PageSeeder XML.

Publish action: <action> elements are specified in the publish config. They include:

Publish engine: A key component of the PageSeeder solution, the Publish Engine handles all import, export, publish and some process operations by executing customizable Ant scripts. It is included as part of each PageSeeder server, but one PageSeeder server can use the Publish Engine on a different PageSeeder server so CPU-intensive tasks, such as document composition or transformation, can be distributed.

Publish engine API: see PageSeeder Ant API.

Publish script: An Apache Ant build file (build.xml) that calls the Ant API through Ant tasks so they can be processed by the Publish engine.

Publish task: An alternate, ambiguous and non-preferred term that refers to an Ant task.

Publisher: See Publish engine.

Q

Question (search): The conceptual foundation of the search service is the idea of “question field” and “question”. Examples of question fields are “document title” and “author”. A questions would be one or more word that appear in either or both question fields. After processing the question, the search service will return a list of results in the specified format (documents, comments, URLs) where the content of a question field fully or partially matched the content of the question.

R

Read only – section or document: Prevents a document or section from being edited through the standard PageSeeder user interface. This is especially useful for content that is being maintained externally but integrated with PageSeeder content for publishing. An example of this class of content are comments that are maintained in source code.

References document type: The “references” document type is the default way to assemble multiple PSML documents into a publication.

Resolve references: To ensure the integrity of xrefs, when an xref is created. PageSeeder checks that the target document exists. If it does. then the xref is considered resolved. Otherwise, it is considered unresolved, and is displayed in red.

Reverse cross-reference: For a bi-directional link, the reverse cross-reference (or reverse xref) is the component that exists on the link target and refers to the link source. By default, PageSeeder xrefs are bidirectional. This means that, by processing a document, it is possible to know what other documents link to them.

Role: The role determines the permissions of a member in a PageSeeder group.

S

Scheduled jobs: A publish script can be scheduled to run at set times using the scheduler.

Schematron: An ISO standard with powerful validation capabilities and configurable error messages. Further information about the standard is available via the Schematron Wikipedia page. Also see XSD files.

Search: Built on the Apache Lucene technology, PageSeeder offers end users and developers several interfaces to find and retrieve content using the search capability.

Search facets: Typically a property value or a label, facets work best when they are consistently applied to most of the documents in a collection. For example, if most documents include a property of "city", the value of that property can be used to navigate or categorize documents in the collection.

Section: Defined in each PSML document as containers for related fragments, sections are used to divide a document into fixed parts that remain in place throughout the lifecycle of the document.

Section ID: An ID for a section. The section ID must be unique within the document and is constrained by a pattern or by enumerated values.

Section title: A section title is stored outside the editable area of a section. It is displayed but cannot be removed or altered using the standard editing interface. This can be a useful way of building documents that are composed of specifically defined, or ordered, sections.

Server message: A server message is a global message that an administrator can enter in the administrator dashboard for display on all pages on the server. It is generally used to notify ALL users currently logged into that particular PageSeeder server of an imminent server wide event, such as an upgrade or restart.

Shared document: A document viewable by more than one group.

Single Sign-On (SSO): Single sign-on lets users sign in with a single ID to an external identity provider to authenticate with PageSeeder. The credentials are maintained by the external identity provider.

Site prefix: Is the prefix assigned to PageSeeder URLs. The value of the site prefix is stored in the global properties.

Status: Is a value that can be given to a task or a document workflow to represent their current state. The status values, and roles that can use them, are configurable in the group properties.

Subgroup: Subgroups allow all the members of one group to be added to another group (the supergroup) with one action, as if it was an individual member.

Subproject: Is a project below another project or subproject.

Supergroup: A supergroup is any group with a subgroup as a member. There are no special characteristics of a supergroup, except that knowing which individuals can access the group requires processing the membership of the subgroup.

T

Table of Contents (ToC): <toc> is a placeholder element for the generation of a Table of contents.

Task: A task is an action to be undertaken and is defined by its status. An active task is a task which has an active status. In the user interface, PageSeeder uses the task icon for tasks.

Task status: The task status applies to comments in a discussion. The status of the last comment is the status of the task.

Template folder: The template folder is a container for most of PageSeeder’s customizable code.

Token: A random string generated by PageSeeder and used for authentication or authorization depending on the type of token used.

Transclusion: A transclusion is type of cross reference that is resolved directly, so that the referenced content (a document or part of a document) is included into the source document.

U

Universal format: The universal format refers to a collection of PageSeeder files when outside PageSeeder. It consists of a file organization and uses PSML as a representation for PageSeeder documents and their metadata.

URI: URI is used as a generic term for documents, folders and URLs which are specific types of URIs. They all have a unique URI ID and share many common features.

URI ID / uriid: Is PageSeeder’s internal identifier, as opposed to the document ID which is designed to be a public identifier.

URI pattern: A URI pattern (or URL pattern) is simple URL-like notation to match URLs. They are used by the PageSeeder services and Berlioz to identify the user interface to render or service to invoke from a URL.

URL: Also known as an external URI.

Username: It is an optional public identifier for a user account in PageSeeder, and it is only required when the user account doesn’t have an email address.

V

Validation: See Schematron or validating documents.

Variation: A document originally created as a copy of a document using the duplicate function.

Version: A version is a “named” snapshot of a single document. A name can be any of the following:

W

Webapp: Refers to the folder structure below the Web application server.

Webhook: A mechanism that lets PageSeeder notify a client app with an HTTP callback when a specified event occurs.

Weborganic folder: The weborganic folder is where PageSeeder stores the application-level styles, scripts and images to be served over the web. Where a project has been customized, the equivalent material is stored in style folders under the template folder.

Weekly digest: Weekly digest is a method of notification, allowing the member to keep up to date with the latest comments and discussion related to a group by receiving a single email once weekly.

Workflow: An XLink object that expresses the stages in a document’s lifecycle – reducing coordination overheads in a collaborative writing environment. In the user interface, workflows use the workflow icon.

X

XHTML sanitization: When comment content is submitted with contenttype=application/xhtml+xml the content is sanitized for security and consistency so that it only contains the following elements or attributes. Named entities such as   are also converted to numerical entities or Unicode characters so the content can be processed easily as XML.

XLink: XLinks are a key component in the PageSeeder architecture. Sometimes their role is obvious (cross-references), and sometimes it is less obvious (a new document).

Xref: See:

Xref list editor: This is a specialized PSML fragment editor to add to, delete or reorganize a list of xrefs (cross-references). Edits to the <xref-fragment> element invoke this editor. By default, the second fragment of a references document is configured to invoke the xref list editor. Adding an <xref-fragment> must be done through the PSML document template – there is no way to add one through the standard end-user interface.

XSD files: There are a number of schema files that are useful for validating different aspects of PageSeeder. Both the files and documentation are available through schemas.