Looking for way to disable 'Key reference' validation error
When validating a ditamap currently we are getting a lot of 'Key reference' errors. In our current environment they are to be expected as they are related to glossary terms we haven't 'hooked' up yet. Is there any way to filter out these errors when running the validate operation on the ditamap from the 'DITA Maps Manager'? Is there an extension or something that can be added? I checked to see if it was being output based on any of the schematron validation files but didn't find anything. The type of error when copied from the 'Errors' tab is: System ID: C:\DEVELOPMENT\TCE_RESEARCH\LOGICAL_OPERATIONS\PRODUCTION_CONTENT\lo_092012\trunk\092012\lsn_01\intro.dita Engine name: oXygen Severity: error Description: Key definition "gloss_raster" not found in the DITA Map context. Type: Key reference Start location: 10:27 End location: 10:55 Any insight would be greatly appreciated. -Aaron Claypoole [Description: LO_email-sig-logo96] Aaron Claypoole Senior Software Engineer aaron.claypoole@logicaloperations.com<mailto:aaron.claypoole@logicaloperations.com> www.logicaloperations.com<http://www.logicaloperations.com/> 500 Canal View Blvd. | Rochester, NY 14623 (W) +1.585.350.7021 [cid:image002.png@01CD6690.14C067D0]<http://www.linkedin.com/company/2539101?trk=tyah>[cid:image003.png@01CD6690.14C067D0]<https://twitter.com/logicalops> This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message and any attachment.
Hi Aaron, I understand the problem. When the DITA Map is checked, the validation is correct, those keys are not defined anywhere. We do not have any API to filter some errors from being shown, the Validate and Check for Completeness is done entirely in the Java code. The best you could do after the validation would be to sort the results by "Type" and remove the problems you do not want to look at. Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 11/7/2012 10:58 PM, Aaron Claypoole wrote:
When validating a ditamap currently we are getting a lot of ‘Key reference’ errors. In our current environment they are to be expected as they are related to glossary terms we haven’t ‘hooked’ up yet.
Is there any way to filter out these errors when running the validate operation on the ditamap from the ‘DITA Maps Manager’? Is there an extension or something that can be added? I checked to see if it was being output based on any of the schematron validation files but didn’t find anything.
The type of error when copied from the ‘Errors’ tab is:
System ID: C:\DEVELOPMENT\TCE_RESEARCH\LOGICAL_OPERATIONS\PRODUCTION_CONTENT\lo_092012\trunk\092012\lsn_01\intro.dita
Engine name: oXygen
Severity: error
Description: Key definition "gloss_raster" not found in the DITA Map context.
Type: Key reference
Start location: 10:27
End location: 10:55
Any insight would be greatly appreciated.
-Aaron Claypoole
Description: LO_email-sig-logo96
**
*Aaron Claypoole*
Senior Software Engineer
aaron.claypoole@logicaloperations.com <mailto:aaron.claypoole@logicaloperations.com>
www.logicaloperations.com <http://www.logicaloperations.com/>
500 Canal View Blvd. | Rochester, NY 14623
(W) +1.585.350.7021
cid:image002.png@01CD6690.14C067D0 <http://www.linkedin.com/company/2539101?trk=tyah>cid:image003.png@01CD6690.14C067D0 <https://twitter.com/logicalops>
This email message is for the sole use of the intended recipient(s) and
may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply email and destroy
all copies of the original message and any attachment.
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Dear Aaron, The easiest way to not be bothered by those errors is to just define those keys in the map. For example, let's suppose you have the keys x1 and x2 that are expected but not yet available then you can add at the end of the map an entry like below: <keydef keys="x1 x2"/> and oXygen will not give errors anymore when these keys are used. Please remember to remove the keys from there as soon as they are actually defined on the topics. Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 11/8/12 8:55 AM, Oxygen XML Editor Support wrote:
Hi Aaron,
I understand the problem. When the DITA Map is checked, the validation is correct, those keys are not defined anywhere. We do not have any API to filter some errors from being shown, the Validate and Check for Completeness is done entirely in the Java code. The best you could do after the validation would be to sort the results by "Type" and remove the problems you do not want to look at.
Regards, Radu
Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com
On 11/7/2012 10:58 PM, Aaron Claypoole wrote:
When validating a ditamap currently we are getting a lot of ‘Key reference’ errors. In our current environment they are to be expected as they are related to glossary terms we haven’t ‘hooked’ up yet.
Is there any way to filter out these errors when running the validate operation on the ditamap from the ‘DITA Maps Manager’? Is there an extension or something that can be added? I checked to see if it was being output based on any of the schematron validation files but didn’t find anything.
The type of error when copied from the ‘Errors’ tab is:
System ID: C:\DEVELOPMENT\TCE_RESEARCH\LOGICAL_OPERATIONS\PRODUCTION_CONTENT\lo_092012\trunk\092012\lsn_01\intro.dita
Engine name: oXygen
Severity: error
Description: Key definition "gloss_raster" not found in the DITA Map context.
Type: Key reference
Start location: 10:27
End location: 10:55
Any insight would be greatly appreciated.
-Aaron Claypoole
Description: LO_email-sig-logo96
**
*Aaron Claypoole*
Senior Software Engineer
aaron.claypoole@logicaloperations.com <mailto:aaron.claypoole@logicaloperations.com>
www.logicaloperations.com <http://www.logicaloperations.com/>
500 Canal View Blvd. | Rochester, NY 14623
(W) +1.585.350.7021
cid:image002.png@01CD6690.14C067D0 <http://www.linkedin.com/company/2539101?trk=tyah>cid:image003.png@01CD6690.14C067D0 <https://twitter.com/logicalops>
This email message is for the sole use of the intended recipient(s) and
may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply email and destroy
all copies of the original message and any attachment.
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
participants (3)
-
Aaron Claypoole -
George Cristian Bina -
Oxygen XML Editor Support