Skip to content
pCon.configurator onlineDocumentation
Esc
↑↓navigate↵open⌘Jpreview
On this page

Catalog Service

The catalog web service API presents registered manufacturer catalogs as a set of trees1 of catalog nodes. Each tree represents a single manufacturer catalog2. Trees consist of folder, article and information nodes.

To uniquely identify a catalog node one must either use a catalog path or the pair of catalog ID and catalog node key.

The catalog path is similar to a file system path. It consists of a list of node names, starting with the name of the root node, followed by the name of one of it’s child nodes, an so on. The last name in the list is the name of the node to identify.

When a catalog node is identified by catalog ID and catalog node key, then the catalog ID identifies the manufacturer catalog containing the node, and the catalog node key uniquely identifies the node within this catalog.

The catalog implementation supports XCF and OAS catalogs. It allows mixing of XCF and OAS catalogs within a single data or catalog profile.

Contents

Footnotes

  1. Strictly speaking, it is a directed acyclic graph of catalog nodes, as a) the edges between nodes are directed (from parent node to child node), and b) some types of nodes (nodes that can’t have outgoing edges) may have multiple incoming edges (i.e. parent nodes). ↩

  2. Old-style manufacturer profiles may result in more than one manufacturer catalog. ↩