Missing properties in CreativeWork - side effect of rNews merge?

[Stéphane Corlosquet]

I've noticed today that usageTerms and copyrightNotice were removed from http://schema.org/CreativeWork and all its subtypes. Here is the old description of these properties:

usageTerms  A statement about the usage terms pertaining to the CreativeWork.

copyrightNotice  Any necessary copyright notice for claiming the intellectual property for the CreativeWork.

Is that a side effect of the merge of rNews? Was it intentional to drop these two properties, or is it a bug? May I suggest you provide a changelog for future reference so that developers know to update their schema.org tools and mappings, especially in the case where properties are dropped. Please also suggest what new properties to use instead.

Steph.

[jaysonlorenzen]

Hey this is bad, these are indeed gone, though I have them in
printouts from just days ago. Ugh! These are both properties of
rNews:NewsItem (rNews v.07 and probably v1.0 that is). So what do we
use for these for CreativeWork objects now?



On Sep 23, 9:06 am, Stéphane Corlosquet <scorlosq...@gmail.com> wrote:
> I've noticed today that usageTerms and copyrightNotice were removed fromhttp://schema.org/CreativeWorkand all its subtypes. Here is the old

> description of these properties:
>
> usageTerms  A statement about the usage terms pertaining to the
> CreativeWork.
> copyrightNotice  Any necessary copyright notice for claiming the
> intellectual property for the CreativeWork.
>
> Is that a side effect of the merge of rNews? Was it intentional to drop
> these two properties, or is it a bug? May I suggest you provide a changelog
> for future reference so that developers know to update their

> schema.orgtools and mappings, especially in the case where properties

[Guha]

Sorry about the brief appearance of these terms on schema.org. They were accidentally copied over when incorporating some of the rnews terms.

There is no plan to address this class of vocabulary terms in the
core schema.org vocabulary.

This might be a good use case for schema.org's 3rd party extensibility model, which allows external vocabularies to be included, even if they're not understood by implementations of the core.

Sorry again for the confusion.

Guha