Bug 816811

Summary: RFE: Extensible topic types
Product: [Community] PressGang CCMS Reporter: Joshua Wulf <jwulf>
Component: Web-UIAssignee: Nobody <nobody>
Status: NEW --- QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 1.xCC: topic-tool-list
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Joshua Wulf 2012-04-27 04:51:02 UTC 
Define new topic types in the system, with their own configurable xml templates.

The new topic types should be subclasses of the existing base topic types Concept, Task and Reference. 

So that when a processing system encounters a topic type for which it has no information, it will treat it as the base class.
Comment 1 Joshua Wulf 2012-05-01 02:56:42 UTC 
A couple of additional factors:

1) Sub-classing new topic types from the three base types is important for forward-compatibility with DITA.

2) The Content Spec Processor will probably need to pull a list of supported topic-types by name from the server to validate a spec.

I'd be happy to get extensible topic types with templates before CSP support for them is available, because I can create a book using the base types, and then manually set the subclassed topic types in the Skynet interface.