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
serviceAudience vs. audience #145
Comments
BTW Service may need some more tweaking, currently |
also http://schema.org/serviceType doesn't make much sense to my, maybe better to allow additionalType to accept Text since people focusing on RDF will most likely use multiple values on type ? |
@elf-pavlik 's proposal seems sensible to me. @vholland - any thoughts? |
Sounds good to me. |
Thanks. Historically it is pretty rare for us to actually erase terms, so far we usually just mark as supersededBy. In this case maybe that is too conservative and best to avoid clutter. Any thoughts? |
You could mark the obsolete terms in HTML with I've been treating superseded as implying sub property and obsolete . The sub property relationship might be wrong, if a superseding property can |
@danbri if you like I can revert | drop this change and then use schema:supersededBy instead! |
Yes, I think schema:supersededBy would be most appropriate here. @elf-pavlik could you tweak your branch that #285 draws from? I've filed this for the next release, and can't see it proving controversial. Simon is right that we could say more about what it means. We have never said that it implies subPropertyOf, since it is easy enough to assert that independently at the same time where needed. In this case I believe serviceAudience would also be a sub-property of audience. |
removed serviceAudience and reused audience rel #145
Revert "removed serviceAudience and reused audience rel #145"
I've implemented this manually after failing with the pull request. I tweaked the definition to be "An intended audience, i.e. a group for whom something was created." rather than use "item" or "subject" to refer to the thing that has the audience. Also "an" rather than "the" since the property is repeatable. |
http://schema.org/audience
http://schema.org/serviceAudience
related email: http://lists.w3.org/Archives/Public/public-vocabs/2014Oct/0023.html
I would suggest removing serviceAudience and using generic audience. If some reasons exist for not doing so maybe at least defining serviceAudience as subPropertyOf audience?
The text was updated successfully, but these errors were encountered: