Re: Would it be useful to include web payments "data rights & responsibilities" in the standard

RE: "What we can do is provide mechanisms to make the collection of
statistics easier for organizations like consumer protection agencies,
tax/revenue collection agencies, and anti-money laundering initiatives."

I had two mechanisms in mind:

1. Is there already an ODRL+WebPayments data model relationship?
— Resource Description Framework (RDF) http://www.w3.org/RDF/
— ODRL Community Group http://www.w3.org/community/odrl/

Examples:
— Describing Copyright in RDF http://creativecommons.org/ns#
— Introducing RDF for GNU Licenses
http://www.fsf.org/blogs/licensing/2009-06-rdf See:
http://www.gnu.org/licenses/gpl-3.0.rdf

2. I'm wondering if XrML already provides metadata that can be used for
implementers to associating rights/responsibilities/restrictions to
WebPayments data in any implementation
— A Formal Foundation for XrML (eXtensible rights Markup Language)
www.cs.cornell.edu/home/halpern/papers/xrml.pdf

XrML Reference Implementation:
— MPEG-21 Rights Expression Language
http://mpeg.chiariglione.org/standards/mpeg-21/rights-expression-language
— MPEG-21 Rights Data Dictionary
http://mpeg.chiariglione.org/standards/mpeg-21/rights-data-dictionary

-- 
Joseph Potvin
Operations Manager | Gestionnaire des opérations
The Opman Company | La compagnie Opman
http://www.projectmanagementhotel.com/projects/opman-portfolio
jpotvin@opman.ca
Mobile: 819-593-5983
LinkedIn (Google short URL): http://goo.gl/Ssp56


On Mon, Dec 16, 2013 at 10:27 AM, Manu Sporny <msporny@digitalbazaar.com>wrote:

> On 12/14/2013 09:33 AM, Joseph Potvin wrote:
> > What shall be considered "acceptable use" of transactional data
> > generated through web payments systems?
>
> This is a huge policy can of worms typically covered by laws and
> regulations in a particular country. We can provide guidance via W3C
> NOTEs, but it will be very difficult to build technical standards to
> enforce the sort of behavior that we'd like, even if we come to a
> consensus on what the behavior should be.
>
> > Is the web payments standard itself the place to state a code of good
> > practice regarding what transaction data should normally be
> > structured into openly available statistics, and what's to be
> > restricted? Or can the standard simply refer to a coherent statement
> > on this?
>
> Technical standards typically do neither.
>
> What we can do is provide mechanisms to make the collection of
> statistics easier for organizations like consumer protection agencies,
> tax/revenue collection agencies, and anti-money laundering initiatives.
>
> We can certainly refer to coherent statements on the matter, but keep in
> mind that technical standards are supposed to be about just that - the
> technology. They're documents that implementers read to build
> interoperable systems. If there is a certain policy that we want to
> enforce, the technology must be designed to enforce that particular policy.
>
> A good example of this policy-enforcement-via-technology approach is the
> do-not-track login mechanism used by Persona. A Persona login assertion
> is created by the Identity Provider (IdP), but the IdP has no idea which
> website you're using that identity assertion with (it can't track what
> you're logging into).
>
> > For analytical purposes I would hope that anonymized data could be
> > available about "currency of transaction", but I wonder if making
> > any such info available would bother others. The thing is, for
> > analytical work it's really helpful
>
> If it's available, it would have to be voluntary by the payment
> processor, merchant, or other participant in the transaction. There
> could be legal/privacy issues related to the sharing of this data as
> well. The most that I think we could do is provide a standard data
> format for the data to be shared in. I have a feeling that governments
> will have more input in this area.
>
> -- manu
>
> --
> Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
> Founder/CEO - Digital Bazaar, Inc.
> blog: Meritora - Web payments commercial launch
> http://blog.meritora.com/launch/
>
>



<http://goo.gl/Ssp56>