serviceAudience vs. audience

[elf-pavlik]

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?

[elf-pavlik]

BTW Service may need some more tweaking, currently
Service --{serviceArea}--> AdministrativeArea
Service --{serviceAudience}--> Audience --{geographicArea}--> AdministrativeArea

[elf-pavlik]

BTW Service may need some more tweaking, currently
Service --{serviceArea}--> AdministrativeArea
Service --{serviceAudience}--> Audience --{geographicArea}--> AdministrativeArea

[elf-pavlik]

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]

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 ?

[danbri]

@elf-pavlik 's proposal seems sensible to me. @vholland - any thoughts?

[danbri]

@elf-pavlik 's proposal seems sensible to me. @vholland - any thoughts?

[vholland]

Sounds good to me.

[vholland]

Sounds good to me.

[danbri]

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?

[danbri]

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?

[sesuncedu]

You could mark the obsolete terms in HTML with . In the type rendering
you could group the obsoleted terms together with the term that obsoleted
them.

I've been treating superseded as implying sub property and obsolete .

The sub property relationship might be wrong, if a superseding property can
have a narrower meaning than the older term.

[sesuncedu]

You could mark the obsolete terms in HTML with . In the type rendering
you could group the obsoleted terms together with the term that obsoleted
them.

I've been treating superseded as implying sub property and obsolete .

The sub property relationship might be wrong, if a superseding property can
have a narrower meaning than the older term.

[elf-pavlik]

@danbri if you like I can revert | drop this change and then use schema:supersededBy instead!

[elf-pavlik]

@danbri if you like I can revert | drop this change and then use schema:supersededBy instead!

[danbri]

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.

[danbri]

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.

[danbri]

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.

[danbri]

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.