Kingsley's comments

[mhausenblas]

See: http://linkeddata.uriburner.com/describe/?url=http%3A%2F%2Fschema.org%2FPlace .

isDefinedBy relation should associate a Class or Property with its Defining Ontology. wdrs:describedby can be used to associate Object Name with Object Address.

Looking at your first cut, I would swap current isDefinedBy relations with wdrs:describedby. Then add isDefinedBy relations between Ontology Name and each of the Classes and Properties its defines.

The subtle difference between Description and Definition (a special kind of description) is highlighted by these suggested tweaks. Ditto the difference between Name and Address via wdrs:describedby.

• indirection via 303
• default representation HTML+RDFa

• note; I don't see said indirection or default representation at the current time. Evidence: http://uriburner.com/c/EYD4P4

  http://schema.org/Thing rdfs:DefinedBy http://schema.org/ . http://schema.org/Thing wdrs:describedby http://schema.org/Thing .

OR

• indirection via # terminated URI based Object Name

• implicit de-reference (indirection) via fragment identifier handling

  http://schema.org/Thing#this rdfs:DefinedBy http://schema.org/ .

• Address-of relation that exposes actual Named Object Representation via a Resource URL

  http://schema.org/Thing#this wdrs:describedby http://schema.org/Thing .

Sample page: http://uriburner.com/describe/?url=http%3A%2F%2Fschema.rdfs.org%2Fall&p=2&lp=4&first=&op=0&gp=2

[cygri]

A lot of this is very valid advice for general RDF publishing. Our situation is difficult because we don't control schema.org and try to say reasonable things about a site that doesn't actually provide any RDF.

I think we should rather not squat the schema.org namespace to have http://schema.org/Thing#this because that contradicts the RDFa modeling documented on schema.org itself, where http://schema.org/Thing is used as the class URI.

I don't feel good about

schema:Thing rdfs:isDefinedBy <http://schema.org/>.

because that page doesn't actually say anything about schema:Thing. It's just a homepage from where to navigate into the site. So I'd rather not make that assertion. I was looking for another property to express that relationship. rdfs:isPartOf? void:inDataset?

And given the choice between

schema:Thing rdfs:isDefinedBy <http://schema.org/Thing>.
schema:Thing wdrs:describedby <http://schema.org/Thing>.

I prefer the first because rdfs:isDefinedBy is the more important property to assert. And the canonical definition of that class is really found on that page, so it's an accurate statement to make given the current configuration of HTTP resources at schema.org.

I'm tempted to make http://schema.rdfs.org/all a void:Dataset and relate all the classes and properties to it via void:inDataset, but that's also a bit fishy because they are not RDF documents.