Overview
First it is necessary to separate SharePoint's definition of a publication from Hyper.Net's. Hyper.Net defines a publication as 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. Thus 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.
Each publication has two important identifiers: a unique publication ID (PUB_ID) and a publication title (PUB_TITLE). The same is true of Topics: each has a unique ID (DOC_UNID) and a title. The title is used for display and categorization purposes, much in the same way any metadata value would be used (in fact it is a metadata value). The ID is used not only as a metadata value but also as a unique identifier for naming folders in SharePoint. For each publication, there will therefore be a SharePoint folder having the publication ID as its name. Each publication folder will then contain one or more folders representing topics within the publication. Each of these folders has a unique topic ID as its name and contains all of the elements representing the content of the topic. Each rendition regardless of type (PDF, HTML, etc.), as well as each hypertext topic belonging to a Rich Hypertext rendition, is represented as a Topic folder containing the relevant data for that rendition.
Within Hyper.Net's sample WCMS application, the URL of any Topic has this format:
http://myhost:myport/sites/myrootsite/myfirstsubsite/mypublishingsite/Lists/Publications/PUB_ID/DOC_UNID/topic.aspx