- From: Agnese Farinelli <agnese.farinelli@studenti.unimi.it>
- Date: Tue, 21 Apr 2015 15:57:35 +0200
- To: public-odrl@w3.org
Hello! Thanks so much for your fast and precious answers. I think that it's better to extend the type of asset and container directly outside from the ODRL Schema instead to simply modify the asset and container type adding one or two row of code whitin the ODRL Schema. So I can leave intact the original ODRL Schema and, at the same time, make changes on my side. My purpose is to create a specific ODRL profile for a musical standard developed by my university. In the event that this new ODRL profile can be published, I think it is better to have a dedicated Schema that isn't the same as the ODRL Schema. So the original ODRL Schema remains public and easy to find like the standard that it is, while my specific profile becomes an extension (obviously, in case that profile can be released outside of a scientific research). Do you think it's a good idea? My best regards. Farinelli Agnese
Received on Tuesday, 21 April 2015 13:58:07 UTC