Interview with Barry Schaeffer, icon in XML circles

Anyone who’s been in the SGML/XML industry for any length of time knows Barry Shaeffer. Barry is a frequent speaker and contributor on subjects related to information and content management. His work with structured information began in 1979 with SGML, and with XML at its initial publication as a standard in 1996.

He was Founder and President of X.Systems.Inc., a system development and consulting firm specializing in the conception and design of text-based information systems, with industrial, legal/judicial and publishing clients among the Fortune 500, non-profit organizations and government agencies, until it’s acquisition by XyEnterprise in 2008. X.Systems was the first Arbortext partner company.

Continue reading “Interview with Barry Schaeffer, icon in XML circles”

Transform Your Content Strategy for Today’s Media and Beyond

Your information content is a critical business asset. It is a key differentiator of you, your organization, and what you have to offer customers. For some, it is the first introduction you have to potential new customers and for the rest an integral tool in retaining and expanding your existing customer relationships.

Traditionally people have viewed content in isolated silos. Separating marketing and product management from the engineering development from support services. In today’s market place, leaders have taken a transformative approach and have broken down the archaic barriers to allow for a dynamic flow of information and collaboration while still maintaining a high level of visibility into all facets of the lifecycle. How? By changing the way they manage content!

In this recorded web session, we discuss what true component-level content management can do for you and your bottom line. We will give you tips and pointers of key things to look for when evaluating solutions and red flags to avoid.

Watch the Video Continue reading “Transform Your Content Strategy for Today’s Media and Beyond”

Common Questions: Bursting

Bursting, chunking and content reuse in Arbortext

This week’s topic: Bursting

We start talking about something we call “bursting” when we get questions like the following:

Can a writer or translator work just on paragraph chunks while an editor can see entire sections?

This question is nearly always followed by this question:

Can this level of granularity be specified in ACM?

Before we can answer either question, we need to address some of the implicit assumptions here.

First, we’re assuming you’ve using the component content management functionality of Arbortext Content Manager (ACM). This means you have created reusable chunks, or have implemented bursting rules so that ACM creates the chunks for you. Once you have the chunks in ACM, you can set permissions so that individual users can only access those parts that they have permission to see.

In Arbortext, we call this process of automatically chunking your documents into individual, reusable pieces “bursting.”

Arbortext Content Manager performs document bursting based on configuration files that are stored on the server.  If no burst configuration is specified, the ACM will treat each document as a single document object. For some document types, such as the DITA document types, the burst configuration is used to import document objects rather than burst a larger document into smaller objects. DITA documents are already modular and typically do not require bursting.

Bursting rules are also used when you use the Documentum Adapter, the DB2 Adapter, or the Oracle Adapter with Arbortext Editor.

Note that much of the “work” involved in document bursting is researching your authors’ requirements and determining a burst configuration that meets their needs. It may be helpful to get some assistance defining your first burst configuration and then using an advisor to confirm your first solo bursting project.

As always, if you have a question that we haven’t answered or if you want more details, remember to send us your questions or add them to the comments!