From k.j.w.alexander at gmail.com Thu Jan 13 13:46:18 2011 From: k.j.w.alexander at gmail.com (Keith Alexander) Date: Thu, 13 Jan 2011 12:46:18 +0000 Subject: [goodrelations] 24 hours opening Message-ID: Hi, How do you say that something is open 24hrs a day? All I could think of was: g:openingHoursSpecification [ g:open "00:00" ; g:close "00:00" ] . but doesn't seem clear that that is "always open" or "never open". Cheers, Keith From daniel.schmidt at conlabz.de Thu Jan 13 13:55:01 2011 From: daniel.schmidt at conlabz.de (Daniel Schmidt) Date: Thu, 13 Jan 2011 04:55:01 -0800 Subject: [goodrelations] 24 hours opening In-Reply-To: Message-ID: Hi Keith Am 13.01.11 13:46 schrieb "Keith Alexander" unter : > g:openingHoursSpecification [ g:open "00:00" ; g:close "00:00" ] . > >but doesn't seem clear that that is "always open" or "never open". What about g:openingHoursSpecification [ g:opens "00:01" ; g:closes "24:00" ] . Best regards, Daniel From martin.hepp at ebusiness-unibw.org Fri Jan 14 10:30:00 2011 From: martin.hepp at ebusiness-unibw.org (Martin Hepp) Date: Fri, 14 Jan 2011 10:30:00 +0100 Subject: [goodrelations] 24 hours opening In-Reply-To: References: Message-ID: Hi all: > Am 13.01.11 13:46 schrieb "Keith Alexander" unter > : > >> g:openingHoursSpecification [ g:open "00:00" ; g:close >> "00:00" ] . Note that there are a structural and syntactical problems in your example: It should be foo:myShop a gr:LocationOfSalesOrServiceProvisioning ; gr:hasOpeningHoursSpecification [ a gr:OpeningHoursSpecification ; gr:opens "00:00:00"^^xsd:time ; gr:closes "23:59:59"^^xsd:time ] . - gr:opens and gr:closes instead of open and close - gr:hasOpeningHoursSpecification instead of g:openingHoursSpecification - missing type for the blank node (can be inferred of course) >> >> but doesn't seem clear that that is "always open" or "never open". > > What about g:openingHoursSpecification [ g:opens "00:01" ; > g:closes > "24:00" ] . > > Best regards, Daniel It's as Daniel says: The best way to indicate all-day opening hours is 00:00:00 - 23:59:59. However, as per xsd:time, you must include the seconds: foo:Mondays a gr:OpeningHoursSpecification ; gr:opens "00:00:00"^^xsd:time ; gr:closes "23:59:59"^^xsd:time . If no time-zone suffix is included, the time is given in the local time valid at the location. For a time in GMT/UTC, simply add a "Z" following the times: foo:Mondays a gr:OpeningHoursSpecification ; gr:opens "00:00:00Z"^^xsd:time ; gr:closes "23:59:59Z"^^xsd:time . Alternatively, you can specify an offset from the UTC time by adding a positive or negative time following the time: foo:Mondays a gr:OpeningHoursSpecification ; gr:opens "00:00:00-09:00"^^xsd:time ; gr:closes "23:59:59-09:00"^^xsd:time . or foo:Mondays a gr:OpeningHoursSpecification ; gr:opens "00:00:00+09:00"^^xsd:time ; gr:closes "23:59:59+09:00"^^xsd:time . Best Martin -------------------------------------------------------- martin hepp e-business & web science research group universitaet der bundeswehr muenchen e-mail: hepp at 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/ * Quickstart Guide for Developers: http://bit.ly/quickstart4gr * Vocabulary Reference: http://purl.org/goodrelations/v1 * Developer's Wiki: http://www.ebusiness-unibw.org/wiki/GoodRelations * Examples: http://bit.ly/cookbook4gr * Presentations: http://bit.ly/grtalks * Videos: http://bit.ly/grvideos From martin.hepp at ebusiness-unibw.org Wed Jan 19 18:00:52 2011 From: martin.hepp at ebusiness-unibw.org (Martin Hepp) Date: Wed, 19 Jan 2011 18:00:52 +0100 Subject: [goodrelations] Fwd: POI Data Format References: Message-ID: FYI - This shows how GoodRelations and the tickets extension can be used in combination with POI data in RDF. Begin forwarded message: > From: Martin Hepp > Date: 19. Januar 2011 17:59:54 MEZ > To: jacques lemordant > Cc: "public-poiwg at w3.org W3C" > Subject: Re: POI Data Format > > Hi, > looks interesting! > > Note that you can directly attach opening hours information with > GoodRelations [1] and entrance fee information / tickets with the > TIO extension to GoodRelations [2]: > > > # Point of interest: foo:GVAbastille > > # Opening hours > > foo:GVAbastille gr:hasOpeningHoursSpecification foo:Workdays, > foo:Saturdays . > > foo:Workdays > a gr:OpeningHoursSpecification ; > gr:opens "08:00:00"^^xsd:time ; > gr:closes "18:00:00"^^xsd:time ; > gr:hasOpeningHoursDayOfWeek > gr:Monday, gr:Tuesday, gr:Wednesday, gr:Thursday, gr:Friday . > > foo:Saturdays > a gr:OpeningHoursSpecification ; > gr:opens "08:30:00"^^xsd:time ; > gr:closes "14:00:00"^^xsd:time ; > gr:hasOpeningHoursDayOfWeek gr:Saturday . > > > # Tickets > foo:ticket3 a tio:TicketPlaceholder ; > rdfs:label "Day ticket for the Bastille"@en ; > tio:accessTo foo:GVAbastille . > > foo:HeppTickets gr:offers foo:offer3 . > > foo:offer3 a gr:Offering ; > gr:name "Day tickets for the Bastille - just EUR 8"@en ; > gr:description "Day tickets for the Bastille"@en ; > gr:includes foo:ticket3 ; > gr:hasBusinessFunction gr:Sell ; > gr:hasPriceSpecification > [ a gr:UnitPriceSpecification ; > gr:hasCurrency "EUR"@en ; > gr:hasCurrencyValue "8"^^xsd:float ; > gr:validThrough > "2010-12-31T23:59:59"^^xsd:dateTime ] . > > > Best > Martin > > > [1] http://purl.org/goodrelations/v1#hasOpeningHoursSpecification > > [2] http://purl.org/tio/ns#museum_example > > > > On 19.01.2011, at 12:51, jacques lemordant wrote: > >> Just an small example of the format in RDF we have implemented in >> our AR browser. >> At this time, we are using mainly HTML5 for the content. >> (we are using two FOAF element to allow searching and aggregating >> of POIs) >> >> > xmlns:poap="http://wam.inria.fr/poap/0.1/" >> xmlns:foaf="http://xmlns.com/foaf/0.1/"> >> >> >> Bastille >> > ele="386.58"/> >> >> >> >> >> >> >> > end="2011-12-31T18:17:44Z" /> >> >> >> >> >> T?l?ph?rique de la Bastille >> > ele="221.399"/> >> >> >> >> >> >> >> > end="2011-12-31T18:17:44Z" /> >> >> >> >> >> >> Jardin de Ville >> > ele="217.861"/> >> >> >> >> >> >> >> >> >> >> >> >> jacques >> >> > -------------------------------------------------------- martin hepp e-business & web science research group universitaet der bundeswehr muenchen e-mail: hepp at 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/ * Quickstart Guide for Developers: http://bit.ly/quickstart4gr * Vocabulary Reference: http://purl.org/goodrelations/v1 * Developer's Wiki: http://www.ebusiness-unibw.org/wiki/GoodRelations * Examples: http://bit.ly/cookbook4gr * Presentations: http://bit.ly/grtalks * Videos: http://bit.ly/grvideos From martin.hepp at ebusiness-unibw.org Thu Jan 20 15:02:41 2011 From: martin.hepp at ebusiness-unibw.org (Martin Hepp) Date: Thu, 20 Jan 2011 15:02:41 +0100 Subject: [goodrelations] RDFa pattern to display opening hours in a human-friendly way Message-ID: <0F4AF731-1548-4739-99F0-735A8E0F27B6@ebusiness-unibw.org> Hi all: When you publish opening hours information with GoodRelations, you often want to display them in the form hh:mm to human readers in their browsers, e.g. Mondays: 08:00 - 14:00 but you have to use them in the form hh:mm:ss for RDFa, since seconds are a mandatory part of the datatype xsd:time . This means that by default, you have to use the "content" attribute in order to produce a page that - is valid and - looks nice. Example:
08:00
For dynamic Web pages, this is also the recommended way of doing this. If, however, you have static Web content or content edited by "lay people" in a WYSIWG editor, you usually want to make sure that updating the visible content will also update the RDFa data, in order to avoid that they may diverge, e.g.
09:00
where the data says 8:00 a.m. and the Web page says 9:00 a.m. One elegant way of solving this problem is to mark the seconds as invisible using an additional element:
08:00
and to hide that part in the CSS: Untitled Document Then, any change of the opening hour data in the visible form hh:mm will automatically update the RDFa data as well. There are two risks associated with this: - In a WYSIWYG editor, it is easy to delete the invisible span element. People editing the page should be advised to use overwrite mode, if possible. - In the past, Google discouraged site owners to use invisible content. To our knowledge, the main effect of using hidden content right know is that Google will ignore the hidden part for indexing. However, it is not entirely impossible that Google will punish the massive use of hidden elements with a lower ranking. From a pure SEO perspective, using the "content" attribute is safer, but a data maintenance perspective may often recommend the pattern shown above if your page is a static one or CMS-based. Best wishes Martin Hepp