use base-class properties when available

[satra]

@vsoch - just took a quick look at containers, which is derived from softwareappliance but creates new properties instead of using the baseclass ones.

in schema.org new things should only add properties that are not in its parent classes.

perhaps its just a rendering thing in openschemas, but the way schema.org does it is kinda nice:

https://schema.org/SoftwareApplication

tells you which properties are specific to this thing, and which are derived from parents, grandparents, etc.,. this will make it easier to comment on specific properties that are being added for these classes.

[vsoch]

ooof thanks @satra ! I'm looking at the original sheets and this information is represented there, so it's 100% a bug / bad on my part (hopefully with just rendering on jekyll). I'll have a look later today and let you know when I figure it out! Thank you for the feedback and catching this 🐛 !

[vsoch]

hey @satra one quick question - if you look at bioschemas, for example here --> http://bioschemas.org/specifications/DataCatalog/ is this structure akin to what I was doing (which is different than what schema.org is doing?) If so, then what I can do is mimic what schema.org is doing.

[vsoch]

and I should probably make it okay that a draft specification can inherit from another draft (e.g., Container --> ContainerRecipe) or maybe it should be the case that the parent must be integrated into schema.org first (and then not trigger an error, as it would not being integrated).