Closed Bug 256430 Opened 22 years ago Closed 2 years ago

XML parsing errors need a storyline

Categories

(Core Graveyard :: RDF, defect)

Product:
Core Graveyard
Component:
RDF
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: axel, Unassigned)

References

Details

(Keywords: arch)

When getting an xml datasource, xml parsing errors and other problems are just dropped. This is both inconsistent with the way that we parse regular XML files and it makes working with RDF harder than it should be. On the other hand, I have no idea how much content relies on us being fine with broken XML. Firefoxens update is just the most prominent example that comes to my mind. All this should integrate smoothly with our datasource loading story, that is, asynch calls probably want to add a notification callback.
*** Bug 256403 has been marked as a duplicate of this bug. ***
Firefox's Live Bookmarks use the RDF parser for RSS 1.0, so it accepts and (partially, at least) uses not-well-formed RSS 1.0 while refusing not-well-formed RSS 2.0 and Atom.
Product: Core → Core Graveyard
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.