- From: Nick Doty via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Jun 2022 21:41:40 +0000
- To: public-patcg@w3.org
"FRAND" and "licensing" terminology is being used here in potentially ambiguous ways. W3C attempts to publish standards under a royalty-free patent policy: https://www.w3.org/Consortium/Patent/ In requiring no royalties and limiting what additional conditions can be applied, I believe this typically satisfies (and goes beyond) fair, reasonable and non-discriminatory as those terms are used in other SDOs regarding patent licensing. In other cases, it seems like "licensing" is being used to refer to data about users. @jwrosewell could you clarify what you mean by "input data"? It's possible that you mean that any data that might be used by some implementer to trigger, for example, sending attribution reports must be sold or shared under fair terms to any other organization that wants that data. I don't think that "licensing" would apply in that case because I think that most of the data isn't copyrightable (or patentable), but is instead facts about users, like their browsing history or when they visited particular websites. Mandatory sale or sharing of browsing history would be deeply concerning to user advocates, and I expect to many people in a group working on private advertising technology. It could also be that "input data" is a reference to the kind of data that is used in discussing standards designs, as @martinthomson referred to above. That data can be important to evaluating the feasibility of different approaches. I would suggest that as a group that works in public, we would typically rely on data that is shared publicly (which may necessarily be limited) in any decision making, rather than licensing or sharing data under some confidentiality terms. And I would agree that because of those limits, we also sometimes have to be skeptical or look for corroboration or additional evidence when we don't have access to private data. -- GitHub Notification of comment by npdoty Please view or discuss this issue at https://github.com/patcg/meetings/issues/52#issuecomment-1163634833 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 22 June 2022 21:41:41 UTC