Re: using hCalendar in a meeting record

On Mon, 2005-08-29 at 10:53 -0400, Karl Dubost wrote:
> Hi Dan,
> 
> very interesting stuff,
> 
> Le 2005-08-28 à 01:04, Dan Connolly a écrit :
> > I went to a pretty cool meeting last week and served as scribe...
> >    http://www.policyawareweb.org/2005/ftf2/paw-mtg
> 
> I have looked at the source file… pretty crowded markup :/

Yes... I could have used a more concise idiom that's special
to this meeting or special to meeting records in general,
but I went with hCalendar, which is more general and
perhaps makes it more verbose in this case...

> <p class='phone'>
>      <strong class='resolution'>
>      <span id="item15ev" class="vevent">
>      <span class="description">
>          RESOLUTION: to meet <abbr class="dtstart"
>          title="2005-08-31T14:30:00-0400">2:30pmET Weds 31 Aug</abbr>
>          for <abbr title="PT1H30M" class="duration">1.5hrs</abbr> to
>          <b class="summary">advance cwm work</b>. timbl, danc, vlad,
>          daniel.
>      </span>
>      </span>
>      </strong>
> </p>
> 
> You accumulate span and classes
> 
> 1st possible factorization
> 
> <p class='phone'>
>      <strong class='resolution'>
>      <span id="item15ev" class="vevent description">
>          RESOLUTION: to meet <abbr class="dtstart"
>          title="2005-08-31T14:30:00-0400">2:30pmET Weds 31 Aug</abbr>
>          for <abbr title="PT1H30M" class="duration">1.5hrs</abbr> to
>          <b class="summary">advance cwm work</b>. timbl, danc, vlad,
>          daniel.
>      </span>
>      </strong>
> </p>

I tried something like that; using the same element for vevent
and description didn't work. I'm not sure if that's a limitation
of the hCalendar spec or a bug in my code.

> 
> 2nd possible factorization
> 
> <p class='phone'>
>      <strong id="item15ev" class="resolution vevent description">
>          RESOLUTION: to meet <abbr class="dtstart"
>          title="2005-08-31T14:30:00-0400">2:30pmET Weds 31 Aug</abbr>
>          for <abbr title="PT1H30M" class="duration">1.5hrs</abbr> to
>          <b class="summary">advance cwm work</b>. timbl, danc, vlad,
>          daniel.
>      </strong>
> </p>
> 
> The code is now a lot lighter.

I don't want to use the same element for the resolution and
the vevent, because I don't want to say that paw-mtg#item15ev
is both an event on 31 Aug and a decision (which is also an
event) in this (23-24 Aug) meeting.

>  Too many classes in XHTML makes it as  
> difficult to type and understand than RDF/XML and a lot of efforts  
> not typo-free.
> 
> I do not agree with the use of abbr for date transformation, but I  
> know some people have different opinions on that. So it could be  
> considered as an open issue, and still be discussed.
> 
> QUESTION:
>      How the XHTML code has been created? by hand? by an automatic tool?
>      It certainly uses [Scribe script][1], but how was done the  
> hcalendar “enrichment”?

by hand.

> 
> 
> [1]: http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
> 
> 
-- 
Dan Connolly, W3C http://www.w3.org/People/Connolly/
D3C2 887B 0F92 6005 C541  0875 0F91 96DE 6E52 C29E

Received on Monday, 29 August 2005 15:13:19 UTC