-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
publisher
vs creator
vs ? / certificates and feature lists
#11
Comments
Just highlighting an inconsistency with the above proposal: One advantage of
This also works well in terms of any conformance certificate - as it is necessarily the product that gets the conformance certificate, rather than the organisation. Additionally the On reflection, perhaps it's best that we stick with the original proposal (which just uses Additionally perhaps |
Discussed on W3C call of 2020-09-09. Agree to retain current implementation. |
There's conflicting language being used here: |
Actually, aren't we really talking about a schema.org I would then suggest in relation to #15 that what we really want is |
Yes, great idea! Additionally I did look at |
Sorry, was reflecting on |
Ha, no worries, I edited mine to match :) |
Sorry, wasn't clear. I was referring to
|
Formalised in 0.2 as in the example immediately above. For discussion. |
The discussion in the W3C Community Group call on 13 January 2021, taking inspiration from the WebAPI discussions, concluded that one evolution of the above could be to use Looking at this further, and given that it is difficult for us to add to the range to existing schema.org properties (we avoid doing so where possible), perhaps defining a new property within Using the pattern of
Advantages:
Disadvantages:
|
Another comparison for the above: |
publisher
vs creator
vs ?publisher
vs creator
vs ? / certificates and feature lists
Problem
We need to align how we're representing organizations that are related to a dataset with Google's expectations for the purposes of SEO.
The current draft data model for Dataset API Discovery includes:
bookingService
is a property in the OpenActive namespace, and is not recognised by Google. It is also not clear whether thepublisher
property is being used correctly in this context.Considerations
Google's Structured Data Documentation
Google's Structured Data Documentation recommends the use of the property
creator
to represent the "The creator or author of this dataset", and does not provide specific references for other properties (though points to schema.org for more information).schema.org
schema.org includes several options for attibution of the roles of organizations relating to a schema:Dataset:
creator
- The creator/author of this CreativeWorkmaintainer
- A maintainer of a Datasetpublisher
- The publisher of the creative work.sourceOrganization
Existing OpenActive dataset sites
The dataset site text reads:
Note that single database systems generally set
bookingService
to matchpublisher
, as they are the same.Proposal
Note this proposal doesn't consider
maintainer
, which could be useful to include within the JSON-LD as a duplicate ofcreator
(if set)?Multiple database systems
For multiple database systems, where there is one dataset site per activity provider:
creator
- The activity providerpublisher
- The booking systemSingle database systems
For single database systems, where there is one dataset site that contains data from multiple activity providers:
publisher
- The booking system(Note in this proposal the "Platform" reference is removed from the HTML for Single database systems)
Implementation note
We need to ensure the embedded DCAT markup reflects this change.
The text was updated successfully, but these errors were encountered: