Warning: This tool or project is no longer maintained and kept available only for archival purposes. Since GoodRelations and schema.org have evolved significantly in the past years, the current status available on this page is unlikely to function as expected. We take no responsibility for any damage caused by the use of this outdated work, to the extent legally possible.

Due to a lack of resources, we are unable to provide support for this project outside of consulting projects or sponsored research. Please contact us if you can contribute resources to update and enhance these resources.

GoodRelations - The Web Vocabulary for E-Commerce

This is the archive of the goodrelations dicussion list

GoodRelations is a standardized vocabulary for product, price, and company data that can (1) be embedded into existing static and dynamic Web pages and that (2) can be processed by other computers. This increases the visibility of your products and services in the latest generation of search engines, recommender systems, and other novel applications.

[goodrelations] GoodRelations and Web Payments (aka. Payswarm)

☮ elf Pavlik ☮ perpetual-tripper at wwelves.org
Sat Dec 28 18:20:35 CET 2013 

I've just watched a video by Manu Sporny on generating and registering 
Asset & Listing for Web Payments: http://youtu.be/n5KBw7K65hg

I tried searching http://wiki.goodrelations-vocabulary.org for terms 
*asset*, *listing* with no results and payswarm giving just two:
* http://wiki.goodrelations-vocabulary.org/Changelog/20110401
* http://wiki.goodrelations-vocabulary.org/Events/ISWC2012

I wonder if some way of aligning between Web Payments and GoodRelations 
terms exists?

https://web-payments.org/specs/source/vocabs/payswarm
http://www.heppnetz.de/ontologies/goodrelations/v1.html

I also notice gr:PaySwarm as subclass of gr:PaymentMethod in range of
gr:acceptedPaymentMethods

Wouldn't at least those terms somehow map to each other:
gr:ProductOrService <-> payswarm:Asset
gr:Offering <-> payswarm:Listing

GoodRelations terms already got included in schema.org and maybe Web 
Payments could somehow reuse/extend them:
http://schema.org/Product
http://schema.org/Offer | http://schema.org/Demand

Otherwise publishers may need to mark things as both?
Product & Asset
Offer & Listing

Thanks for help with clarifying it!

More information about the goodrelations mailing list