A number of entities are essential reserved. These include BUILD_NAME BUILD_DATE BUILD_BZPRODUCT BUILD_BZCOMPONENT BUILD_BZVERSION BUILD_BZKEYWORDS BUILD_JIRA_PID BUILD_JIRA_CID BUILD_JIRA_VID BOOKID YEAR TITLE HOLDER BZURL BZCOMPONENT BZPRODUCT There is nothing currently stopping writers from manually defining these entities in a spec and (in the case of the "report a bug" link entities) using them in topics. Manually defining these entities should result in a warning at the very least.
BOOKID YEAR TITLE HOLDER BZURL BZCOMPONENT BZPRODUCT are fine as they are generated from the Content Spec data and won't change. Only entities prefixed with "BUILD" shouldn't be used.
Fixed in 1.4-SNAPSHOT build 201402171457 The validator will now throw errors when any of the reserved entities are used in the "Entities" metadata.
Note: This version has been deployed to the test/development server.
Confirmed that the BUILD_ entities can not be defined in a spec: WARN: No Subtitle specified, so a default will be used instead. WARN: No Abstract specified, so a default will be used instead. ERROR: Invalid XML Entities! BUILD_BZCOMPONENT, BUILD_BZKEYWORDS, BUILD_BZPRODUCT, BUILD_BZVERSION, BUILD_DATE, BUILD_JIRA_CID, BUILD_JIRA_PID, BUILD_JIRA_VID and BUILD_NAME are reserved entities and cannot be defined. -> Entities = [ <!ENTITY BUILD_NAME 'something'> <!ENTITY BUILD_DATE 'something'> <!ENTITY BUILD_BZPRODUCT 'something'> <!ENTITY BUILD_BZCOMPONENT 'something'> <!ENTITY BUILD_BZVERSION 'something'> <!ENTITY BUILD_BZKEYWORDS 'something'> <!ENTITY BUILD_JIRA_PID 'something'> <!ENTITY BUILD_JIRA_CID 'something'> <!ENTITY BUILD_JIRA_VID 'something'> ] ERROR: The Content Specification is not valid.