Re: Proposal: Audiobook

A variant proposal: on each schema.org/SomeType page, annotate each
property with a star icon if it's popular (used on, say, >25% of hosts
marking up that type in the wild), as well as a "new" icon if it's recently
added (so that authors don't ignore the newly added properties just because
they're not popular yet). This way the annotations are completely automatic
and external to the schema, and won't need to debated by the community each
time a new property is added.

jb


On Fri, Sep 27, 2013 at 2:42 PM, Thad Guidry <thadguidry@gmail.com> wrote:

> You misunderstood me, Phil.  Not Domain Types per se, but Types that can
> be reused for various Domains.  But it is not the Types that are the
> "interesting" parts...it is the Properties that everyone really cares about
> in actuality.
>
> An example would be like, "Article" or "about"...used in lots of different
> Domains.
> What are the useful, interesting properties that could be widely used
> across many Domains.
>
> Dan and I agree, there has to be some hierarchy with some visual or
> machine readable clue that these properties are more "useful" on certain
> Types.
>
> So something like, "base" properties for Types, and call them or "hint"
> them as a "base", or "standard", etc... versus some "extra" properties that
> are more niche to only a few domains.
>
> So you would have something like this on the RDFS for the Property pages
> on Schema.org :
>
> http://schema.org/creator
>
> <div resource="http://schema.org/creator" typeof="rdf:Property
> owl:Property" property="rdfs:label" content="creator">
>
>  <h1 class="page-title">Property: <a href="creator">creator</a></h1>
>
> <div property="rdfs:comment">The creator/author of this CreativeWork or
> UserComments. This is the same as the Author property for
> CreativeWork.</div>
>
> <table cellspacing="3" class="definition-table">
>   <tbody><tr><th class="rangeIncludes-vals" scope="row" colspan="2">Values
> expected to be one of these types:</th></tr>
>
>   <tr class="type-nam"><td><code><a property="
> http://schema.org/rangeIncludes"
> href="/Person">Person</a></code></td><td></td></tr>
>
>   <tr class="type-nam"><td><code><a property="
> http://schema.org/rangeIncludes"
> href="/Organization">Organization</a></code></td><td></td></tr>
>
>   <tr><th class="domainIncludes-vals" scope="row" colspan="2">Used on
> these types:</th></tr>
>
>   <!---  SOMETHING LIKE THIS THAT SIGNIFIES ITS A BASE PROPERTY (most
> useful) FOR THE CreativeWork Type --->
>
>   <tr class="type-nam"><td><code><a property="
> http://schema.org/domainIncludes/base"
> href="/CreativeWork">CreativeWork</a></code></td><td></td></tr>
>
>   <!---  SOMETHING LIKE THIS THAT SIGNIFIES ITS A EXTRA PROPERTY (least
> useful) FOR THE Diet Type --->
>
>   <tr class="type-nam"><td><code><a property="
> http://schema.org/domainIncludes/extra"
> href="/Diet">Diet</a></code></td><td></td></tr>
>
> </tbody></table>
>
> </div>
>
>
> Or however you wish to signify a "most useful / applicable on these
> Types".  hinting toward sub-typing eventually, I guess, lol.
>
> --
> -Thad
>
> Thad on Freebase.com <http://www.freebase.com/view/en/thad_guidry>
> Thad on LinkedIn <http://www.linkedin.com/in/thadguidry/>
>