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
serviceAudience vs. audience #145
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?
added a commit
Jan 25, 2015
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
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.
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.