Closed Bug 33197 Opened 20 years ago Closed 18 years ago

no support for parseType="Resource|Literal"

Categories

(Core Graveyard :: RDF, enhancement, P3)

enhancement

Tracking

(Not tracked)

RESOLVED FIXED
mozilla1.0.1

People

(Reporter: waterson, Assigned: waterson)

References

(Blocks 1 open bug, )

Details

(Whiteboard: [nsbeta2-])

We currently do not support <RDF:li parseType="Resource|Literal"> in rule 
[6.30].

Supporting parseType="Resource" should be fairly straight-forward; it is simply 
a shorthand syntax for adding properties to an anonymous, inline resource.

parseType="Literal" is a bit more difficult because it allows arbitrary XML to 
be embedded in the body: we'd want to treat this as a string, not as a content 
model. The parser may have "issues" with that.
Blocks: 11650
Status: NEW → ASSIGNED
Target Milestone: --- → M20
nominating for nsbeta2, this is a standards issue
Keywords: nsbeta2
Putting on [NEED INFO] radar. PDT needs to know impact to user and risk of fix 
to make a call on this bug. 
Whiteboard: [NEED INFO]
I cannot quantify the "impact to user" of standards support. This will affect 
parsing of RDF/XML files.
Whiteboard: [NEED INFO]
Eric, can you please comment on the standards issue here?
Whiteboard: [NEED INFO]
Putting on [nsbeta2-] radar. Not critical to beta2. 
Whiteboard: [NEED INFO] → [nsbeta2-]
Target Milestone: --- → mozilla1.0
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 
(you can query for this string to delete spam or retrieve the list of bugs I've 
moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
This is implemented in bug 118865.
Depends on: 118865
Fixed with checkin for bug 118865.
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
tever is not RDF QA anymore
QA Contact: tever → nobody
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.