Invalid TOC XML - id cannot start with a number
Expected behaviour
TOC XML should be valid to BITS DTD and PMC style checker compliant.
Current behaviour
Many TOC XML are invalid because IDs are beginning with a number when this is not permitted.
Steps to reproduce
- Validate attached TOC.xml -TOC_1640.xml
- See error -
System ID: C:\Users\lathrops\OneDrive - National Institutes of Health\Desktop\Unconfirmed 2202.crdownload
Main validation file: C:\Users\lathrops\OneDrive - National Institutes of Health\Desktop\Unconfirmed 2202.crdownload
Schema: \\fridge\pmcprod\load\converter4\DTD\dtd-niso-z39.96\extensions\bits\2.0\BITS-book2.dtd
Engine name: Xerces
Severity: error
Problem ID: IDInvalidWithNamespaces
Description: Attribute value "17q12foundationbreakgrimesiowa" of type ID must be an NCName when namespaces are enabled.
Start location: 545:1993
End location: 545:2025
Environment
This is occurring in domain gene
. I cannot reproduce it on Coko site. @deniskar can you understand why? Affiliations should not get tagged in TOC.XML but they are in content in NCBI deployment but not Coko deployment.
Possible solution
QA Steps
[To be completed by Coko once dev is done]