Having spent the last few weeks creating a Drupal module that give
users a tool to add events to their personal calendars, the challenges
inherent in moving date information are definitely in my mind.
First off, your tool needs to be aware of your date handling system.
In Drupal, you can base on U
On Wed, Jun 8, 2011 at 3:08 PM, Nate Vack wrote:
> On Wed, Jun 8, 2011 at 1:45 PM, Brice Stacey wrote:
> > You can't necessarily say "We 8:00-2:00" because your closing hour could
> be after your opening hour on the next day and it would be ambiguous. E.g.
> Opening at 2am and closing the next d
On Wed, Jun 8, 2011 at 1:45 PM, Brice Stacey wrote:
> You can't necessarily say "We 8:00-2:00" because your closing hour could be
> after your opening hour on the next day and it would be ambiguous. E.g.
> Opening at 2am and closing the next day at 4am.
Hm, good point.
> Ideally, if working wi
You can't necessarily say "We 8:00-2:00" because your closing hour could be
after your opening hour on the next day and it would be ambiguous. E.g. Opening
at 2am and closing the next day at 4am. I know that's absurd for most libraries
but it may happen. A better example is when a library stays
On Wed, Jun 8, 2011 at 11:45 AM, Kevin S. Clarke wrote:
> Mondays,
> Wednesdays, and Fridays 5-9pm
Or, if you just want to talk about
http://library.example.com/hours/today, (which I think is what the OP
was about?) you could do:
Open today
(Wednesday, June 8) from 8:00 am to 5:00 pm
Note tha
On Wed, Jun 8, 2011 at 12:28 PM, Keith Jenkins wrote:
> - Days are specified using the following two-letter combinations: Mo,
> Tu, We, Th, Fr, Sa, Su.
> - Times are specified using 24:00 time. For example, 3pm is specified as
> 15:00.
> Here is an example: Tuesdays and Thursdays 4-8pm
> """
>
>
schema.org may have some potential, but it's not clear to me how the
LocalBusiness/openingHours is supposed to work with anything but
regular hours...
Here's how openingHours are described at http://schema.org/LocalBusiness
"""
The opening hours for a business. Opening hours can be specified as a
In the end, it is only the output format that matters to anyone except
the data producer/holder. You can have whatever you want in your
system and I could not care less -- I only care when I need to process
data you provide, and at that moment I cared deeply how you provide
it. What I care deeply a
On Wed, Jun 8, 2011 at 9:39 AM, Simon Spero wrote:
> HTML is an output format;
Everyone's output format is someone else's input format.
-Nate
On Wed, Jun 8, 2011 at 10:23 AM, Ed Summers wrote:
> On Wed, Jun 8, 2011 at 10:00 AM, Simon Spero wrote:
> > [cue edsu ]
>
> And people wonder why Google/Yahoo/Bing chose to favor html5 microdata
> on schema.org :-)
>
HTML is an output format;
BTW, if you didn't see it, the folks at DERI creat
On Wed, Jun 8, 2011 at 10:00 AM, Simon Spero wrote:
> [cue edsu ]
And people wonder why Google/Yahoo/Bing chose to favor html5 microdata
on schema.org :-)
//Ed
On Tue, Jun 7, 2011 at 7:18 PM, Owen Stephens wrote:
> I'd suggest having a look at the Goid Relations ontology
> http://wiki.goodrelations-vocabulary.org/Quickstart - it's aimed at
> businesses but the OpeningHours specification might do what you need
> http://www.heppnetz.de/ontologies/goodrela
On Tue, Jun 7, 2011 at 4:28 PM, Doran, Michael D wrote:
> I'm trying to figure out the most flexible output markup (RDF schema?), one
> that would allow the widest use of the web service in addition to outputting
> HTML markup for a mobile site page.
Not to start an RDF -vs- Microformats -vs-
on behalf of Brice Stacey
> [brice.sta...@umb.edu]
> Sent: Tuesday, June 07, 2011 11:27 PM
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: Re: [CODE4LIB] RDF for opening times/hours?
>
> Honestly, the API and schema are second to UX to manage the hours. The actual
> API to the we
]
Sent: Tuesday, June 07, 2011 11:27 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] RDF for opening times/hours?
Honestly, the API and schema are second to UX to manage the hours. The actual
API to the web service is trivial and just a matter of deciding on an interface
and schema that yo
Honestly, the API and schema are second to UX to manage the hours. The actual
API to the web service is trivial and just a matter of deciding on an interface
and schema that you like and that most future-proofs your work. Personally, I
would probably disregard it unless it has a JSONP format so
I'd suggest having a look at the Goid Relations ontology
http://wiki.goodrelations-vocabulary.org/Quickstart - it's aimed at businesses
but the OpeningHours specification might do what you need
http://www.heppnetz.de/ontologies/goodrelations/v1.html#OpeningHoursSpecification
While handling publ
There was a time, about 5 years ago, when I assumed that microformats
were the way to go and spent a bit of time looking at hCalendar for
representing iCalendar-formatted event information.
http://microformats.org/wiki/hcalendar
Not long after that, there was a lot of talk about RDF and RDFa for
I am building a little web service that spits out info on when the libraries (a
central library and two branches) are open and what the hours are for that day.
As those who work in academic libraries know, it's not the *regular* hours,
but all the exception dates/hours that are important (Sprin
19 matches
Mail list logo
