Closed Bug 98392 Opened 23 years ago Closed 1 month ago

Internal "nextVal" property shouldn't be in RDF namespace

Categories

(Core Graveyard :: RDF, defect)

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

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE
Milestone:
Future

People

(Reporter: tingley, Unassigned)

References

Details

Dan Brickley wrote on n.p.m.rdf:

If Mozilla depends on using a 'nextVal' property in W3C's
http://www.w3.org/1999/02/222-rdf-syntax#nextVal then that should be filed
as a bug. W3C RDF 1.0 defines no such property, although it might've been
handy if it did. Consequently it would be better if Mozilla used its own
utility vocabulary for this sort of thing, eg
http://mozilla.org/rdf/util#nextVal or similar. Such extensions could then
be used as design input into future RDF specs from W3C.
See also bug 12161.
Blocks: 11650
The root marking stuff in bug 70966 includes a suitable "meta" namespace.
Depends on: 70966
Target Milestone: --- → Future
Status: NEW → ASSIGNED
No longer depends on: 70966
tever is not RDF QA anymore
QA Contact: tever → nobody
Blocks: 232445
waterson left the building
Assignee: waterson → nobody
Status: ASSIGNED → NEW
QA Contact: nobody → core.rdf
Product: Core → Core Graveyard
Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.