This is the archive of the goodrelations dicussion list

Dear all:

There may be scenarios in which you cannot or do not want to expose  
all information expressed using GoodRelations to the general public.

Typical examples are reseller discounts, price lists for restricted  
audiences, or data about what products you own (gr:owns) or seek  
(gr:seeks).

In principle, you can use any established HTTP-based access control  
technique for managing access to such data. For example, you could  
require user credentials for accessing the resource containing the  
reseller price-list.

Still, mixing the public data (e.g. product features) with private  
data (e.g. reseller prices) is simple, as long as the same objects use  
the same URIs.

For a more distributed scenario, I highly recommend looking into the  
evolving WebID specification (formely FOAF+SSL) at

   http://payswarm.com/webid/

There is a bit of additional information already on the following Wiki  
page:

   http://www.ebusiness-unibw.org/wiki/AccessControl4GoodRelations

Best wishes

Martin Hepp


--------------------------------------------------------
martin hepp
e-business & web science research group
universitaet der bundeswehr muenchen

e-mail:  hepp at ebusiness-unibw.org
phone:   +49-(0)89-6004-4217
fax:     +49-(0)89-6004-4620
www:     http://www.unibw.de/ebusiness/ (group)
          http://www.heppnetz.de/ (personal)
skype:   mfhepp
twitter: mfhepp

Check out GoodRelations for E-Commerce on the Web of Linked Data!
=================================================================
* Project Main Page: http://purl.org/goodrelations/
* Quickstart Guide for Developers: http://bit.ly/quickstart4gr
* Vocabulary Reference: http://purl.org/goodrelations/v1
* Developer's Wiki: http://www.ebusiness-unibw.org/wiki/GoodRelations
* Examples: http://bit.ly/cookbook4gr
* Presentations: http://bit.ly/grtalks
* Videos: http://bit.ly/grvideos