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 1391 - Direct Input validation needs a "parse mode" option?
Summary: Direct Input validation needs a "parse mode" option?
Status: NEW
Alias: None
Product: Validator
Classification: Unclassified
Component: check (show other bugs)
Version: 0.7.0
Hardware: All All
: P4 minor
Target Milestone: 1.0
Assignee: Olivier Thereaux
QA Contact: qa-dev tracking
: 2510 (view as bug list)
Depends on:
Reported: 2005-05-12 00:53 UTC by Olivier Thereaux
Modified: 2007-04-04 04:07 UTC (History)
1 user (show)

See Also:


Description Olivier Thereaux 2005-05-12 00:53:56 UTC
Since the Direct Input validation cannot rely on mime type to get a hint of the proper parse mode to be 
applied, cases when the other methods to detect the parse mode fail (e.g unknown FPI) result in a 
fallback to SGML mode, which is not always the proper thing to do.

Perhaps an SGML/XML switch (similar in a way to what Nick is doing) would help.
Comment 1 Olivier Thereaux 2007-02-20 07:37:54 UTC
Working on this, in the context of multiparser work.
Comment 2 Olivier Thereaux 2007-03-15 04:58:45 UTC
*** Bug 2510 has been marked as a duplicate of this bug. ***
Comment 3 Olivier Thereaux 2007-03-27 05:23:12 UTC
See also
for an alternative to a parse mode option in direct input, something I am still unsure is a great idea...

Quoted here:
> I think in the absence of media type information, the validator should either
> (1) force the user to choose one before performing validation, or (2) first
> issue a warning about lack of media type information and then check if the
> character stream begins with (ignoring BOM) "<?xml", and, if so, use XML mode,
> otherwise SGML mode. In case of (2) the user should be able to change the mode
> and revalidate.

Comment 4 Olivier Thereaux 2007-04-04 04:07:21 UTC
Still unsure about proper handling of this question, moving target to "the future", to be revisited.