Thad, 

    I actually don't see how using internal properties would go against Wikidata policy. There is the  requirement of notability, "
  1.  It fulfills some structural need, for example: it is needed to make statements made in other items more useful." [1]
I might be wrong, but I would consider creating a new item to describe a subclass, fulfilling a structural need. 
Modelling classes and subclasses this way, also makes writing federated queries where the WDQS is used in the SERVICE operator easier. I only need to consider one wikidata property to bridge Wikidata with external sources, and deal with child and parent classes in Wikidata.

Cheers,

Andra 

 
[1] https://www.wikidata.org/wiki/Wikidata:Notability


On Tue, Sep 13, 2016 at 3:34 AM, Thad Guidry <thadguidry@gmail.com> wrote:
Andra,

That type of powerful expressiveness is certainly doable in Wikidata.
To blatantly create properties on a whim by pseudo proxy of using Wikidata items to do the heavy lifting.
But that idea is against most of what I have seen in Wikidata documentation, policy, and community best practices say to do.

The right way forward is to patiently wait for the new property to exist, and then we can continue.
Thank you for drafting the property proposal by the way.  I'll wait for it for review.

Here's some examples where we have subclasses under these :

    should also ideally have all of Schema.org's subclasses of Action that we have like

    should also ideally have the subclass of Videogame

Here's an example of flipping it around and saying that Schema.org can be used as an 'external parent class'
    should also ideally have a proeprty on it for 'external parent class' or something similar with the value of

Our full heirarchy is here for your perusal :  http://schema.org/docs/full.html


_______________________________________________
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata