Skip to content
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

Add a property to accompany /license that explains how to acquire licenses etc. #2454

Closed
danbri opened this issue Jan 31, 2020 · 7 comments
Closed
Assignees

Comments

@danbri
Copy link
Contributor

@danbri danbri commented Jan 31, 2020

We have had a property /license for some years ("A license document that applies to this content, typically indicated by URL."). Sometimes publishers have mistaken this for a property that points to a page for getting (e.g. buying) a license.

This proposal is to add a term to address this need. Calling it /usageInfo rather than something more specific, to allow us to address related usecases.

Definition:

Thing > CreativeWork 
Property:  https://schema.org/usageInfo
Values: CreativeWork, URL

The schema.org "usageInfo" property indicates further information about a creative work. This property is applicable both to works that are freely available and to those that require payment or other transactions. It can reference additional information e.g. community expectations on preferred linking and citation conventions, as well as purchasing details. For something that can be commercially licensed, usageInfo can provide detailed, resource-specific information about licensing options.

This property can be used alongside the license property which indicates license(s) applicable to some piece of content. The usageInfo property can provide information about other licensing options, e.g. acquiring commercial usage rights for an image that is also available under non-commercial creative commons licenses.

@danbri danbri self-assigned this Jan 31, 2020
@philbarker
Copy link
Contributor

@philbarker philbarker commented Feb 3, 2020

That name might lead to confusion. To me it sounds more like information on how something is used (e.g. "used by 40% of sites on the web"). licenseCondition or licenseExpectation might be better.

The phrase "further information about a creative work" in the explanation is very ambiguous; better make it "further information about licensing a creative work"

Maybe think about wrapping this into Offer rather than CreativeWork.

offerCondition : "further information on requirements and expectations regarding an offer to transfer some rights to an item or to provide a service"

@danbri
Copy link
Contributor Author

@danbri danbri commented Feb 5, 2020

Thanks @philbarker. Considering this comment and talking with others, including colleagues from Google who are expecting to build around this, I agree that the initial property is a bit too loose. This was on my advice as, while info about license acquisition was a big motivator here, there are other usecases we might cover too. I have just added an additional more explicit property into the Pending draft called /acquireLicensePage which has /usageInfo as a superproperty. I would rather not involve offer in detail at this stage, but the page we point to obviously has potential for being host to that sort of thing (and more).

danbri added a commit that referenced this issue Feb 5, 2020
* Reinstated 301 redirect to https

* Fixed typo: Recommendation not Recommended.

* Add in tweaks to OPTIONS request response headers

* Drafting implementation of MediaReview for discussion. /cc #2450

* Updated mediaAuthenticityCategory label.

* Added disclaimer. /cc #2450

* updated so that label matches id.

* usageInfo and acquireLicensePage properties #2454

Co-authored-by: Richard Wallis <rjw@dataliberate.com>
@nicolastorzec
Copy link
Contributor

@nicolastorzec nicolastorzec commented Feb 26, 2020

I also find the phrase "indicates further information about a creative work` ambiguous". I'd use a more specific explanation, such as "indicates further information about the rights and obligations associated with (the usage of) a creative work".

@WeaverStever
Copy link

@WeaverStever WeaverStever commented May 22, 2020

Perhaps we should look at an inverse to this property for "free to use" content on a website?

I downloaded a social media icon yesterday, but the Creative Commons - Share Alike citation terms required that the host to be linked in the footer of the website. Of course, I went elsewhere and found a truly free icon.

A licensesAquired property could be useful for these Creative Commons citations, purchased or leased artwork, music licensing for video background music, and cover song licensing.

@RichardWallis
Copy link
Contributor

@RichardWallis RichardWallis commented Jul 1, 2020

Implemented in commits b866e1f & fde3730

@Abhishek5772705
Copy link

@Abhishek5772705 Abhishek5772705 commented May 1, 2021

@Abhishek5772705
Copy link

@Abhishek5772705 Abhishek5772705 commented May 1, 2021

I love universe

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants