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] Fwd: [Fwd: Please allow JS access to Ontologies and LOD]

Martin Hepp martin.hepp at ebusiness-unibw.org
Mon Oct 25 16:02:42 CEST 2010

Dear all:

I just fixed the server configurations for GoodRelations,

the Vehicle Sales Ontology,


and the GoodRelations RDFa 1.1 Profile:


So all three resources should be accessible by client-side scripts now.

Personally, I think that Javascript-based scripts will allow very  
useful browser extensions that built atop of GoodRelations data in the  
current page.

Best wishes

Martin Hepp

> -------- Original Message --------
> Subject: Please allow JS access to Ontologies and LOD
> Hi All,
> Currently nearly all the web of linked data is blocked from access via
> client side scripts (javascript) due to CORS [1] being implemented in
> the major browsers.
> Whilst this is important for all data, there are many of you reading
> this who have it in your power to expose huge chunks of the RDF on the
> web to JS clients, if you manage any of the common ontologies or
> anything in the LOD cloud diagram, please do take a few minutes from
> your day to expose the single http header needed.
> Long story short, to allow js clients to access our "open" data we  
> need
> to add one small HTTP Response header which will allow HEAD/GET and  
> requests - the header is:
>  Access-Control-Allow-Origin "*"
> This is both XMLHttpRequest (W3C) and XDomainRequest (Microsoft)
> compatible and supported by all the major browser vendors.
> Instructions for common servers follow:
> If you're on Apache then you can send this header by simply adding the
> following line to a .htaccess file in the dir you want to expose
> (probably site-root):
>  Header add Access-Control-Allow-Origin "*"
> For NGINX:
>  add_header Access-Control-Allow-Origin "*";
> see: http://wiki.nginx.org/NginxHttpHeadersModule
> For IIS see:
>  http://technet.microsoft.com/en-us/library/cc753133(WS.10).aspx
> In PHP you add the following line before any output has been sent from
> the server with:
>  header("Access-Control-Allow-Origin", "*");
> For anything else you'll need to check the relevant docs I'm afraid.
> Best & TIA,
> Nathan
> [1] http://dev.w3.org/2006/waf/access-control/

More information about the goodrelations mailing list