Hi all, Des’ understanding reflects my own when I put these in. I see these are pretty distinct, because confidentiality is not about licensing, but about whether you can expose the content publicly in a process. You might have a case where you have content that will be GPLed (licensingTerms) but not want it exposed publicly yet (confidentiality). The first would tend to be in published materials (i.e., you've put something on the web and you are telling a tool, potentially one you don't even know is looking at your content, whether it can scrape it and use it; the second would be process metadata telling you how to act in your process. I think they are distinction enough (and operate in different areas) that it makes sense to separate them. -Arle Sic scripsit Des Oates in Apr 26, 2012 ad 05:59 : > Dave, re this case below, I’m not sure if this is a full overlap. The use case mentioned in the contentLicensingTerms section covers MT Training corpora. Confidentiality is more applicable to a Translation Workflow use case, where the decision logic is more likely to be implemented in a TMS. If both cases are covered by this data category, then it would be OK, but I want to confirm this is the case first. > > Thanks > > Des > > > > Moritz, Des: I think there is potential to combine 'confidentiality' with 'contentLicensingTerms', with confidentiality being a specific value of contentLicensingTerms, whcih could perhaps be relaised using Creative Commons license classes > > > >
Received on Thursday, 26 April 2012 14:08:06 UTC