You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
license has @code, @variant, and @version. All good.
license also has @pub-year, @price. Aren't these logically separated from license?
Also, I think it is allowable to openly license a book under the conditions of several licenses. Your book is your book, and you tell the world:
You are welcome to use this book under the terms of CC BY-SA. But if you prefer, you are also welcome to use this book under the terms of GFDL. Choose one. You can't mix some clauses from this one with other clauses from that one."
My point is, is there a provision for a project having more than one license element?
The text was updated successfully, but these errors were encountered:
Length of traditional copyright term depends on publication date.
Copyright is what allows you to sell copies.
So they are related, and I don't think making a distinction buys much clarity for XSL processing. But two licenses is something we should support. The year might be relevant to each license. Uncertain about the best way to handle this...
license
has@code
,@variant
, and@version
. All good.license
also has@pub-year
,@price
. Aren't these logically separated fromlicense
?Also, I think it is allowable to openly license a book under the conditions of several licenses. Your book is your book, and you tell the world:
My point is, is there a provision for a project having more than one
license
element?The text was updated successfully, but these errors were encountered: