Bug 1053927

Summary:	Enable DocBook 5 as a valid DTD value
Product:	[Community] PressGang CCMS	Reporter:	Lee Newson <lnewson>
Component:	CSProcessor	Assignee:	Lee Newson <lnewson>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.3	CC:	mcaspers
Target Milestone:	---
Target Release:	1.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-02-23 23:43:52 UTC	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:
Bug Depends On:
Bug Blocks:	1051919

Description Lee Newson 2014-01-16 01:54:26 UTC

Currently the only value that can be used in Content Specs is "DocBook 4.5", however once all other components have been implemented for BZ#1051919, we'll need to add "DocBook 5" as a valid option.

Comment 1 Lee Newson 2014-01-16 23:05:05 UTC

Also with this we need to ensure DocBook 4.5 and DocBook 5.0 topics aren't mixed in a Content Spec as they aren't compatible (mainly due to DocBook 4.5 using DTD's and DocBook 5.0 using a schema)

Comment 2 Lee Newson 2014-02-10 07:08:57 UTC

Added in 1.4-SNAPSHOT build 201402071538

DocBook 5.0 can now be used as a DTD/Format option. I've also changed the "DTD" metadata name to "Format", to better describe the the metadata (since DocBook 5.0 uses Relax NG). This also allows for future additions (ie possibly AsciiDoc).

Note: This can be tested on the test/development server.

Comment 3 Matthew Casperson 2014-02-12 00:09:51 UTC

Confirmed that the Format metadata element can be set to DocBook 5.0, and that topics with xml formats that do not match are identified as validation errors.