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] RDFa prefix definitions

Martin Hepp martin.hepp at ebusiness-unibw.org
Wed Aug 3 10:55:12 CEST 2011

There was a discussion on the RDFa mailing list which may be relevant for users of GoodRelations, see below.

In a nutshell, the RDFa prefix definitions are better put in the <body> element than in the <html> element of HTML markup.


Martin Hepp

Begin forwarded message:

>> Resent-From: public-rdfa-wg at w3.org
>> From: Ivan Herman <ivan at w3.org>
>> Date: August 2, 2011 1:51:41 PM GMT+02:00
>> To: Manu Sporny <msporny at digitalbazaar.com>
>> Cc: RDFa WG <public-rdfa-wg at w3.org>
>> Subject: Re: PROPOSAL: Restrict @prefix declaration to the root element
>> This proposal would lead to major issues with character encoding, see
>> http://lists.w3.org/Archives/Public/public-rdfa-wg/2011Apr/0107.html
>> Executive summary of that mail: HTML5 works with content sniffing to find out the character encoding of the source (looking for a relevant <meta> element in the head). This is done by HTML parsers, too, not only browsers. Having lots of prefix declarations in the <html> elements might lead to erroneous character encoding in the literal objects of the generated RDF; and there is no real defense against that (unless the HTTP return header provides a correct character encoding, but that is not always the case).
>> Actually, the advise (currently in the Primer, too) is _not_ to put too many @prefix declaration in the <html> element to avoid such issues, but put them into, say, the <body> element.
>> I do not think we should do this.
>> Ivan
>> On Jul 19, 2011, at 04:54 , Manu Sporny wrote:
>>> This proposal was raised during the telecon last week[1]. Since document
>>> authors can declare @prefix anywhere in the document, they could
>>> introduce authoring mistakes due to copy-paste. That is, if they do not
>>> pay attention to where the @prefix is declared, they may accidentally
>>> attempt to express triples that do not have a CURIE prefix defined.
>>> While a number of people in the group feel that copy-paste issues are
>>> not really that prevalent, limiting the use of @prefix to just the root
>>> element of the document may decrease the possibility of copy-paste
>>> errors. That is, copying from one place to another place in the document
>>> would not be affected by @prefix declaration.
>>> The down-side to this is that all Web page authors do not have access to
>>> the root element in a document, which is typically set by the content
>>> management system. This would disallow people that know what they're
>>> doing from expressing triples in their sub-sections of the document -
>>> such as blog articles or comment posts.
>>> PROPOSAL: Limit @prefix declaration to the root element in the document.
>>> -- manu
>>> [1]http://www.w3.org/2010/02/rdfa/meetings/2011-07-14#ISSUE__2d_96__3a__Document_not_ready
>>> -- 
>>> Manu Sporny (skype: msporny, twitter: manusporny)
>>> President/CEO - Digital Bazaar, Inc.
>>> blog: PaySwarm Developer Tools and Demo Released
>>> http://digitalbazaar.com/2011/05/05/payswarm-sandbox/
>> ----
>> Ivan Herman, W3C Semantic Web Activity Lead
>> Home: http://www.w3.org/People/Ivan/
>> mobile: +31-641044153
>> PGP Key: http://www.ivan-herman.net/pgpkey.html
>> FOAF: http://www.ivan-herman.net/foaf.rdf

More information about the goodrelations mailing list