W3C home > Mailing lists > Public > public-poiwg@w3.org > October 2011

minutes 20 October 2011

From: Matt Womer <mdw@w3.org>
Date: Thu, 20 Oct 2011 12:01:55 -0400
Message-Id: <68ECE07D-ACB6-431C-B09C-C8305DD16FFA@w3.org>
To: public-poiwg W3C <public-poiwg@w3.org>
Hi all,

Minutes for today's meeting are at:

and as text below.


      [1] http://www.w3.org/

                               - DRAFT -

            Points of Interest Working Group Teleconference

20 Oct 2011


      [2] http://lists.w3.org/Archives/Member/member-poiwg/2011Oct/0016

   See also: [3]IRC log

      [3] http://www.w3.org/2011/10/20-poiwg-irc


          [IPcaller], Matt, rsingh2, ahill2




     * [4]Topics
         1. [5]Next meeting
         2. [6]Time
     * [7]Summary of Action Items

   <trackbot> Date: 20 October 2011

   <robman> hey matt

   <rsingh2> let me warn you I may fall asleep any minute. I'm in China
   at a conference and just got back from the big banquet dinner...

   <ahill2> kakim, +IPcaller is ahill2

   <scribe> Scribe: Matt

Next meeting

   ahill2: Next week is ISMAR, we will likely need to cancel.
   ... We will reconvene on 3 November
   ... October 27 meeting is canceled
   ... Actually, let's keep the meeting for the 27th, and cancel the
   meeting on the 3rd.

   RESOLUTION: Cancel 3rd November Meeting


   ahill2: At one point we came up with a time method that was very
   flexible, like categories and such.
   ... Perhaps we could make time a POI Controlled Vocabulary Type?
   ... Is a flexible time primitive worth creating a new data type for?
   ... I could live with the restricted set, but it doesn't seem like a
   bad idea to consider something more flexible.

   robman: Updated/created are very publishing centric, while start/end
   are extent related. More flexible could be good.

   rsingh2: We could leave the updated/created stuff and flexible.

   ahill2: Yeah, we could leave updated/created in there, and then have
   flexible times for start/end, etc.
   ... This could all be for naught if people are going to throw in
   other things like iCalendar, etc.

   rsingh2: iCalendar would give you a more flexible way to describe
   more than a single point in time, but it doesn't give you names for
   it, e.g. this is an opening time.

   ahill2: That's an argument for having start and end be a POI
   controlled time type.

   robman: It would be good if you had time as a POI controlled type,
   and inside that you could pack an iCalendar type thing as optional.

   ahill2: So do we not need a new type?

   robman: I was thinking you would.

   rsingh2: Term doesn't change from a string to a date, the value

   robman: The content of the time element would either be a simple
   date or a more complex structure

   rsingh2: It gets complicated.

   ahill2: You could even have times having times. Though, maybe that's
   not unreasonable.

   <robman> mob-labs.com/poiwg/example02/index.html

   <robman> [8]http://mob-labs.com/poiwg/example02/index.html

      [8] http://mob-labs.com/poiwg/example02/index.html

   -> [9]http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi
   Syntax Highlight docs

      [9] http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi

   [[<syntaxhighlight lang="xml">xml goes here</syntaxhighlight>]]
   should work


     [10] http://lists.w3.org/Archives/Public/public-poiwg/2011Oct/0016.html


     [11] http://lists.w3.org/Archives/Public/public-poiwg/2011Oct/0003.html


     [12] http://www.rajsingh.org/poiwg/W3CPOI_NVTPOI_03_01_5800_001.xml


     [13] http://www.rajsingh.org/poiwg/W3CPOI_NVTPOI_03_ZAF_9517_001.xml

   <robman> [14]http://www.w3.org/TR/html4/types.html#h-6.11

     [14] http://www.w3.org/TR/html4/types.html#h-6.11

   -> [15]http://www.w3.org/TR/html4/types.html#h-6.11 HTML types

     [15] http://www.w3.org/TR/html4/types.html#h-6.11

   <ahill2> <label term="is open 24 hours">TRUE</label>

   <ahill2> <label term="is open 24 hours"/>

   <rsingh2> <category term="open24hours"

     [16] http://www.example.com/openingtimes

   <ahill2> <label term="TRUE" category="open 24 hours options">

   <ahill2> <category term="TRUE" category="has a drivethrough">

   <ahill2> <category term="TRUE" scheme="drivethrough options"/>

   <ahill2> <category term="drivethrough options">TRUE</category>

   RESOLUTION: We will publish on Alex's birthday, 10 November

   ahill2: See you next week!

   <rsingh2> syntax highlight works!


     [17] http://www.w3.org/2010/POI/wiki/A_UNESCO_World_Heritage_site

Summary of Action Items

   [End of minutes]

    Minutes formatted by David Booth's [18]scribe.perl version 1.136
    ([19]CVS log)
    $Date: 2011/10/20 14:01:44 $

     [18] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
     [19] http://dev.w3.org/cvsweb/2002/scribe/

Scribe.perl diagnostic output

   [Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.136  of Date: 2011/05/12 12:01:43
Check for newer version at [20]http://dev.w3.org/cvsweb/~checkout~/2002

     [20] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/TURE/TRUE/
Succeeded: s/drivethorugh/drivethrough/
Succeeded: s/label/category/
Found Scribe: Matt
Inferring ScribeNick: matt
Default Present: [IPcaller], Matt, rsingh2, ahill2
Present: [IPcaller] Matt rsingh2 ahill2
Agenda: [21]http://lists.w3.org/Archives/Member/member-poiwg/2011Oct/00

     [21] http://lists.w3.org/Archives/Member/member-poiwg/2011Oct/0016

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 20 Oct 2011
Guessing minutes URL: [22]http://www.w3.org/2011/10/20-poiwg-minutes.ht
People with action items:

     [22] http://www.w3.org/2011/10/20-poiwg-minutes.html

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.

   End of [23]scribe.perl diagnostic output]

     [23] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
Received on Thursday, 20 October 2011 16:02:09 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:48:31 UTC