RDF container elements not handled correctly after specifying container type with <rdf:type>

NEW
Unassigned

Status

()

Core
RDF
17 years ago
12 years ago

People

(Reporter: Chase Tingley, Unassigned)

Tracking

Trunk
Future
x86
All
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
From bug 15006:

While testing this I noticed a (afaik) unreported bug in the RDF-XML
parsing/model building -- if I use |<rdf:type resource="http://w3.org/.../#Seq"
/>| to specify a container type, the parse state in the RDFContentSink does not
change from eRDFContentSinkState_InDescriptionElement to
eRDFContentSinkState_InContainerElement.  This causes a problem with subsequent
rdf:li data -- since the parser isn't aware that it's in a container, it treats
these like normal properties and doesn't update nextVal.  As a result,
attempting to enumerate the items in the container will return no items (since
it loops up to nextVal) -- this is evident when re-serializing the datasource.

I'll split this off, but this fix will come for free when the "a container is
just another typed node" cleanup happens, since that would presumably eliminate
the state distinction.

Updated

17 years ago
Target Milestone: --- → Future

Updated

17 years ago
Status: NEW → ASSIGNED

Comment 1

15 years ago
tever is not RDF QA anymore
QA Contact: tever → nobody

Comment 2

14 years ago
waterson left the building
Assignee: waterson → nobody
Status: ASSIGNED → NEW
QA Contact: nobody → core.rdf
You need to log in before you can comment on or make changes to this bug.