RE: [obix-xml] News on XML iCalendar

["Thorsten Roggendorf" <troggendorf@echelon.de>]

Hi Brian

Dropping scheduling for 1.1 sounds reasonable to me -  at least more
reasonable than shipping something that may be outdated in no time.
Echelon has no oBIX implementation.

    Regards
   Thorsten


-----Original Message-----
From: Jeremy Roberts 
Sent: Friday, August 28, 2009 4:20 PM
To: Brian Frank; Thorsten Roggendorf
Cc: obix-xml@lists.oasis-open.org
Subject: RE: [obix-xml] News on XML iCalendar

Brian, Thorsten, & others interested: 

The mini-data spec to handle calendar info as a label appears to be very
close to the hCalender format.  LonMark uses this in our html calendar
page today.  You can view the page source to see how it's constructed
(for a home-grown example): 

http://www.lonmark.org/calendar  

I'd put the source here but I'm on my phone in an airport (an it's an
old phone).

Cheers,
Jeremy J. ROBERTS, Technical Director
LONMARK International - http://www.lonmark.org/
Technical Office - mailto:tech@lonmark.org
PO Box 268, Jamison PA 18929-0268, USA
T: +1 215 918-1026 . F: +1 215 918-1027
________________________________________________________________



-----Original Message-----
From: Brian Frank [mailto:brian.tridium@gmail.com]
Sent: Fri 2009-08-28 08:39 AM
To: Thorsten Roggendorf
Cc: obix-xml@lists.oasis-open.org
Subject: Re: [obix-xml] News on XML iCalendar
 
Thorsten,

I agree on picking the most used calendar modeling by the industry
(although
sounds like the model is *still* iCalendar), just a question of
encoding.
My proposal is that we should drop scheduling from 1.1 for two reasons:
  - let things shake out to see where rest of industry goes
  - because it is highly unlikely to get real implementations anytime
soon,
and we need implementations for standardization

So my suggestion is we focus on the 1.1 release with existing date,
time,
and timezone stuff and new binary encoding section.

By the way Thorsten, does Echelon have an oBIX implementation?


On Fri, Aug 28, 2009 at 8:33 AM, Thorsten Roggendorf
<troggendorf@echelon.de
> wrote:

>  Hi
>
>
>
> There may be a new standard for the iCalendar XML mapping on the way.
It is
> part of W3C's HTML5 proposal! It is a new concept called microdata and
there
> is an example for vEvent
here<http://www.w3.org/TR/2009/WD-html5-20090825/microdata.html#md-veven
t>
> .
>
> The current proposal for HTML5 is scheduled to go on last call (before
> becoming a recommendation) in October. However, the very introduction
of
> microdata may block HTML5 from going to last call in October as stated
at
> the
top<http://www.w3.org/TR/2009/WD-html5-20090825/microdata.html#microdata
>of the page.
>
> HTML5 is not XML but
XHTML5<http://www.w3.org/TR/2009/WD-html5-20090825/introduction.html#htm
l-vs-xhtml>is and this the same specification.
>
>
>
> XHTML5 is potentially the most influential XML standard in the making
- by
> a very far cry. If this microdata concept and the vevent example make
it to
> that standard then there is a good chance that this format will become
*
> the* no-way-around standard for encoding iCalendar in XML.
>
> The timing is rather bad. I would not bet anything on W3C making HTML5
a
> recommendation any time soon, but you never know. Yet we want to get
1.1 out
> rather sooner than later. Now even if W3C takes its time we may want
to
> check whether Mozilla and/or WebKit (i.e. Safari and Chrome) are
taking that
> up on that and doing something with microdata (those browsers made
canvas<http://www.w3.org/TR/2009/WD-html5-20090825/the-canvas-element.ht
ml#the-canvas-element>a de facto standard even though that also should
wait for HTML5 maturity).
>
> Whatever we do, we should give microdata a good look and reconsider
our
> "standard".
>
>
>
>        Regards
>
>      Thorsten
>