This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 13271 - Soap12 format does not provide a way to programatically associate warnings to their corresponding errors
Summary: Soap12 format does not provide a way to programatically associate warnings to...
Alias: None
Product: Validator
Classification: Unclassified
Component: check (show other bugs)
Version: HEAD
Hardware: All All
: P2 enhancement
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: qa-dev tracking
Depends on:
Reported: 2011-07-15 14:13 UTC by Laurent Goderre
Modified: 2015-08-23 07:41 UTC (History)
2 users (show)

See Also:

Validation View (26.64 KB, image/jpeg)
2011-07-15 14:13 UTC, Laurent Goderre

Description Laurent Goderre 2011-07-15 14:13:24 UTC
Created attachment 1011 [details]
Validation View

Some warning are document wide, for instance character encoding error or missing doctype error. However, some are related to an error, for example, a warning is issue with duplicate id error to show where the id was first defined.

In the HTML view, the warning appears after the error. However, when using the soap format, errors and warnings are separate (which makes a lot of sense) but there is no way to determine if a warning goes with an error.

There should be an additional child element of the error object that contains a unique id in the validation result and a child element in the warning object to reference the error id when relevant.

This would make it much easier than rely on string parsing to guess it.

Comment 1 Michael[tm] Smith 2015-08-23 07:41:15 UTC
The soap output option is obsolete and no longer maintained and should no longer be used or relied on.

We recommend instead using the current HTML Checker with the out=json option.