Re-usable bits/facets was: Re: aggregateRating and review under /Person

Matija, I do not have an answer to your question, but this brings up 
something that I have been meaning to address here for a while.

It would be good to look through for re-usable bits and/or 
facets that should be separated out from particular schemas for easy 
discovery and re-use. I am thinking of common elements like address, 
review, place, time, etc., that could conceivably combine with a wide 
variety of entities and that should be available to schema users as 
"universal add-ons" in their instance data.

In the library world our classification systems make use of "facets," 
some of which are entirely "free-floating" (e.g. can be used with any 
other term), and some of which are restricted to certain parts of the 
classification scheme. These are not added to the classification scheme 
as such but are only implemented in the assignment of classifications to 
particular items.

At the moment, takes a class/sub-class approach to sharing 
properties. This is not in conflict with the use of facets, and in fact 
library classifications combine hierarchical arrangement with the use of 

Exactly what should be a "facet" is hard to define theoretically, but a 
good clue is when the same elements or patterns begin to appear in 
separate schemas.


On 2/6/13 1:35 AM, Matija Urh wrote:
> Hi,
> I'm building webpage and a stumble upon a problem.
> I have three types of pages (artist, event and venue). The last two
> (/Event and /Place) have "aggregateRating" and "review" properties, but
> artist (i will use /Person) doesn't.
> So what are my options? Googles Structured Data Testing Tool
> <> returns a
> Warning.. Can I do this or is this bad for my SEO?
> thx
> -- matija urh

Karen Coyle
ph: 1-510-540-7596
m: 1-510-435-8234
skype: kcoylenet

Received on Wednesday, 6 February 2013 16:53:51 UTC