Closed
Bug 33197
Opened 26 years ago
Closed 24 years ago
no support for parseType="Resource|Literal"
Categories
(Core Graveyard :: RDF, enhancement, P3)
Core Graveyard
RDF
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla1.0.1
People
(Reporter: waterson, Assigned: waterson)
References
()
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.
| Assignee | ||
Updated•26 years ago
|
| Assignee | ||
Comment 1•26 years ago
|
||
nominating for nsbeta2, this is a standards issue
Keywords: nsbeta2
Comment 2•26 years ago
|
||
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]
| Assignee | ||
Comment 3•26 years ago
|
||
I cannot quantify the "impact to user" of standards support. This will affect
parsing of RDF/XML files.
| Assignee | ||
Updated•26 years ago
|
Whiteboard: [NEED INFO]
Comment 4•26 years ago
|
||
Eric, can you please comment on the standards issue here?
Whiteboard: [NEED INFO]
Comment 5•26 years ago
|
||
Putting on [nsbeta2-] radar. Not critical to beta2.
Whiteboard: [NEED INFO] → [nsbeta2-]
| Assignee | ||
Updated•25 years ago
|
Target Milestone: --- → mozilla1.0
Comment 6•24 years ago
|
||
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
| Assignee | ||
Comment 8•24 years ago
|
||
Fixed with checkin for bug 118865.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•