Last Comment Bug 90566 - rdf:instanceOf needs to be rdf:type, Suggestion
: rdf:instanceOf needs to be rdf:type, Suggestion
Status: NEW
Product: Core
Classification: Components
Component: RDF (show other bugs)
: Trunk
: x86 Windows 2000
P5 minor with 1 vote (vote)
: Future
Assigned To: Nobody; OK to take it and work on it
: Axel Hecht [:Pike]
Depends on: 15006
  Show dependency treegraph
Reported: 2001-07-12 15:33 PDT by Eric Murphy
Modified: 2006-08-18 20:22 PDT (History)
3 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Description User image Eric Murphy 2001-07-12 15:33:24 PDT
In your docs, this should be changed because the W3C docs changed rdf:instanceOf
to be rdf:type (bottom)
4-September-1998: instanceOf -> type


Also, I would note that containers are essentialy a subtype of resources, and
replace "A" with something descriptive yet generic. Maybe 

( instance of )
( a Container )

because it's a rdfs:Container? I dunno, I understand RDF better after reading
the schema, so maybe it would be good to hint at what is there.

In my opinion, the W3C RDF docs don't do it right either, as they just have a
blank circle.
Comment 1 User image Eric Murphy 2001-07-12 16:41:06 PDT
Oh, and you may want to consider representing B, C , D with ... because it makes
more sense as used in the templates as well.


Comment 2 User image Chris Waterson 2001-07-16 13:37:52 PDT
Sure. I'll have to find the tool that I used to draw those picture, I guess.
Comment 3 User image Chase Tingley 2001-08-24 10:48:12 PDT
depends on bug 15006: stop using rdf:instanceOf internally
Comment 4 User image Asa Dotzler [:asa] 2001-12-03 10:40:52 PST
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 
Comment 5 User image benc 2003-07-25 15:35:10 PDT
tever is not RDF QA anymore
Comment 6 User image Axel Hecht 2004-04-19 12:29:14 PDT
waterson left the building

Note You need to log in before you can comment on or make changes to this bug.