W3C home > Mailing lists > Public > semantic-web@w3.org > July 2009

Re: Recipe for Shops: Showing up in Yahoo and in the Web of Data in One Turn

From: Benjamin Nowack <bnowack@semsol.com>
Date: Wed, 22 Jul 2009 13:20:35 +0200
To: Martin Hepp (UniBW) <martin.hepp@ebusiness-unibw.org>
Cc: "semantic-web at W3C" <semantic-web@w3c.org>
Message-ID: <PM-GA.20090722132035.4AC7C.1.1D@semsol.com>

Interesting. I guess this is another argument/example pro Hugh 
Glaser's idea of simply conflating resource IDs for the sake of
"deployability". The example types <#business> as Vcard, Business
and also as BusinessEntity which would usually be considered wrong
RDF, but, as argued before, is more intuitive for HTML authors, 
especially if they found their way to the SemWeb through pragmatic
solutions like microformats. We should really give this contextual
semantics idea another thought.

(I fear you'll lose a significant chunk of the possible audience at 
"change your DTD" and "add ... to the head tag", these sort of tweaks
are not necessarily easy to do in CMS-based or commercial publishing 
tools unless there is a dedicated plugin that is not erased with the 
next site upgrade. For root/head-level changes, the content *authors*
have to coordinate their tasks with the tech/site *admins*, which 
leads to non-trivial friction loss and hence lowers the deployment 

A general suggestion would be to keep the added markup at a minimum,
until GR is more deployed and people start asking for more on their
own. Remove as many non-mandatory descriptions as possible, at least
if the recipes are targeted at newcomers. Stuff like
"ProductOrServicesSomeInstancesPlaceholder" or
"LocationOfSalesOrServiceProvisioning" is probably not very 
attractive to web dev people who are only just getting acquainted 
with structured markup and want to check out if/how it works.

I *personally* think that RDF-in-HTML snippets are most convincing 
when the amount of additional RDF markup does not outweigh the 
human-oriented content. Otherwise it becomes hard to track the 
initial meaning of the page and examples become less illustrative.
Maybe drop some of the @typeofs which repeat the @rel values (e.g. 
as in
   <div rel="gr:hasOpeningHoursSpecification">
      <div typeof="gr:OpeningHoursSpecification">
), or cheat visually by picking some shorter, less Cyc/AI-like 
predicate names, perhaps? 

Just some thoughts,

Benjamin Nowack

On 21.07.2009 19:42:00, Martin Hepp (UniBW) wrote:
>Dear all:
>I just completed a recipe meant for larger audiences (Web developers,
>SEO companies) on how a business can enrich its pages using
>RDFa+GoodRelations so that the data
>- shows up in Yahoo AND
>- it at the same time useful for comprehensive RDF applications.
>The recipe is at
>It tries to combine pure recipes from the RDF world with the "Web
>developer's" how-tos provided by Yahoo.
>Any feedback is very welcome.
>Martin Hepp
>martin hepp
>e-business & web science research group
>universitaet der bundeswehr muenchen
>e-mail:  mhepp@computer.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 the GoodRelations vocabulary for E-Commerce on the Web of Data!
>Talk at the Semantic Technology Conference 2009:
>"Semantic Web-based E-Commerce: The GoodRelations Ontology"
>Tool for registering your business:
>Overview article on Semantic Universe:
>Project page and resources for developers:
>Tutorial materials:
>Tutorial at ESWC 2009: The Web of Data for E-Commerce in One Day: A 
>Hands-on Introduction to the GoodRelations Ontology, RDFa, and Yahoo! 
Received on Wednesday, 22 July 2009 11:21:12 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 07:42:13 UTC