I've been out of action or on-a-plane a lot these last few days. Am eager to follow up on updating the draft model text in CommonAccord. It was very well structured at the time (and Eve pushed me to work with some CSS). But now can do even better. If anyone interested in taking the lead, I'm delighted to provide tech and editorial support. Am busy most of this week, but eager to start.On Sun, Jun 11, 2017 at 8:07 PM, Eve Maler <eve@xmlgrrl.com> wrote:In Friday's call we discussed existing work that might "fill in" sample license text. Here is what we did to date (keeping in mind that the terminology might not survive our current process, but that we pretty much need to decide all that by the time we exit deliverable #3):
- The Binding Obligations spec (officially obsolete). You can actually search throughout to look for PAT, RPT, and (this was written in UMA1 times) AAT mentions. The AAT is a pretty good substitute for the PCT for now.
- Our CommonAccord draft model text. Again, it mentions the tokens specifically, and was prepared in the UMA1 era -- but it post-dates the Binding Obs.
Our intent has been to prepare "model clauses" (or whatever you want to call them) using the CommonAccord parameterized prose/code system as one of our legal toolkits. Probably our main legal toolkit, with others that might look like checklists and such.
_______________________________________________
WG-UMA mailing list
WG-UMA@kantarainitiative.org
http://kantarainitiative.org/mailman/listinfo/wg-uma
--@commonaccord