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
To implement the two different kinds of licensing for services and functions we have agreed, I suggest to add somewhere within the descriptors a licence type field. If absent, the service/function would be considered Public (i.e., any developer can reuse it, any customer can buy). If present and with Private value, an extra field should also be present and filled with a URL (i.e., download by a developer or acquisition by a customer will call this URL for validation). I think that in this way we can remove most of the complexity of managing software licences, while allowing for scenarios where that can be taken into account.
What do you think?
The text was updated successfully, but these errors were encountered:
To implement the two different kinds of licensing for services and functions we have agreed, I suggest to add somewhere within the descriptors a
licence type
field. If absent, the service/function would be consideredPublic
(i.e., any developer can reuse it, any customer can buy). If present and withPrivate
value, an extra field should also be present and filled with a URL (i.e., download by a developer or acquisition by a customer will call this URL for validation). I think that in this way we can remove most of the complexity of managing software licences, while allowing for scenarios where that can be taken into account.What do you think?
The text was updated successfully, but these errors were encountered: