- From: Martin Hepp <martin.hepp@ebusiness-unibw.org>
- Date: Mon, 19 Nov 2012 15:21:36 +0100
- To: Michael Hopwood <michael@editeur.org>
- Cc: Joseph F <joseph.rl.fournier@hotmail.com>, "public-vocabs@w3.org" <public-vocabs@w3.org>
Hi Michael: I am not sure whether Joseph is really wanting to expose his database schema. I think the main issue discussed is how to mark up page templates that are populated with content not until some user interaction has taken place on the respective page. Martin On Nov 19, 2012, at 2:05 PM, Michael Hopwood wrote: > Hello Joseph, > > Nice use case - you are actually talking about marking up a representation of the *database schema* rather than any instances within it... > > -----Original Message----- > From: Martin Hepp [mailto:martin.hepp@ebusiness-unibw.org] > Sent: 19 November 2012 06:42 > To: Joseph F > Cc: public-vocabs@w3.org > Subject: Re: Using schema.org microdata for Database Content > > In general, it is better to suppress the respective microdata keywords using conditionals in the template language if the value is empty. You will not get any official statements from search engines on which patterns they penalize and which they assess as good quality content, but from the perspective of a microdata extractor, empty fields create just data garbage. > > There is one exeception: For pointing from a data element to the URI of the current page, it if often a handy shortcut to use an empty string. > > Best > Martin Hepp > > On Nov 15, 2012, at 9:36 PM, Joseph F wrote: > >> Hi, >> >> >> I was wondering if one should mark html text fields with schema.org microdata for fields which will contain values (of known type) retrieved from a database, but which are initially empty upon loading the web page (and thus empty for Search Engines). Basically, I have some fields that I would like to mark using microdata, which will not contain any data until the values are retrieved from a database, the population of which would be initiated by users. >> >> Are there any risks for Search Engines to "penalize" a Web Site having microdata for fields which are not yet populated? From my understanding of the schema.org specifications, a Web Site can be "penalized" when marking content which is not visible to users. Is this rule applicable to fields which have not yet been populated (although its content is known)? Does the schema.org specifications take into account this situation? I would like to avoid having my Web Site erroneously penalized. >> >> Thank you for your time. >> >> Regards, >> >> JF > > -------------------------------------------------------- > martin hepp > e-business & web science research group > universitaet der bundeswehr muenchen > > e-mail: hepp@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/ > > > > > -------------------------------------------------------- martin hepp e-business & web science research group universitaet der bundeswehr muenchen e-mail: hepp@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/
Received on Monday, 19 November 2012 14:22:09 UTC