Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Bug in Dataset / DataCatalog relationship #1066
Currently we have:
These both point from Dataset to DataCatalog. The original wording was poor, we had "A data catalog which contains a dataset."; I think it should have been "A data catalog which contains this dataset.".
The new wording is wrong, in that catalogs are the containers for datasets rather than the other way around. It is always easier to change textual definitions than term IDs but in this case I suggest we do both.
Also note that http://schema.org/DataCatalog has http://schema.org/dataset property, defined as "A dataset contained in a catalog." - this is the same relationship named in the opposite direction (and also with awkward wording).
added a commit
Apr 6, 2016
This is mostly because we have a huge vocabulary so imposed the belated discipline of avoiding terms that could have multiple independent meanings. When v2.0 shipped 'catalog' was deemed too general for a property name (it might mean very different things in a digital library versus ecommerce versus datasets setting); whereas a 'dataset' property pretty much does what it says on the tin.
Unfortunately the name 'includedDataCatalog' was misnamed based on the impression that the catalog was within the dataset rather than vice-versa. Hence this tweak. Is it bearable, @joshsh ?
Thanks. Yes, there's a tradeoff between verbosity and consistency. Given that it is already called 'dataset' and that it has been that name all along, I'm not feeling a very strong case for changing it to a longer name. So we pay the price of the two properties being named in different styles. On the positive side, I have actually marked them in the schemas as inverseOf each other now, so they are properly cross-linked.
Another thing we could do on the usability front is to collect a few more inspirational examples and add them to the site. Any suggestions?