Re: toIcal.xsl -- progress on syntactic profile

On Wed, 2004-11-10 at 00:55 -0600, Dan Connolly wrote:
>         DanC: I got started on toIcal.xsl. v1.5 passes
>         test/spec01-conf3.rdf

Hmm... the design I sketched back in January was:

"The rdf2ical.py tool could be split in two: (1) a filter
to grab just the .ics-relevant properties from an RDF knowledge
base and format the results in the syntactic profile, and
(2) a syntactic converter that only groks the profile."

toIcal.py showed that part (2) was workable in at least
one case, but I just tried to make a justIcal.n3
filter and realized it won't work: The syntactic profile
is sensitive to the order of properties; it needs
the cal:prodid property before any of the cal:component
properties. There's no way to express that in an N3
filter; i.e. no matter what the filter says,
cwm's pretty-printer will sort the properties alphabetically:

$ python cwm.py itin.rdf --filter=cal-filter.n3  --rdf

    <cal:Vcalendar r:about="itin.rdf">
        <cal:component r:parseType="Resource">
<!-- hmm... need this to be <cal:Vevent>. but that's a separate issue -->
            <r:type r:resource="http://www.w3.org/2002/12/cal/ical#Vevent"/>
            <cal:summary>#1241 to DFW on AMERICAN AIRLINES</cal:summary>
        </cal:component>
        <cal:component r:parseType="Resource">
            <r:type r:resource="http://www.w3.org/2002/12/cal/ical#Vevent"/>
            <cal:summary>#1240 to DCA on AMERICAN AIRLINES</cal:summary>
        </cal:component>
<!-- ... -->
<!-- Here's today's problem: prodid needs to go up above --->
        <cal:prodid>file:/home/connolly/w3ccvs/WWW/2000/10/swap/pim/itin2ical.n3</cal:prodid>
    </cal:Vcalendar>




rdf2ical.py has since become http://www.w3.org/2000/10/swap/pim/toIcal.py

One option is to add an option to toIcal.py to spit
out the syntactic profile of RDF/XML as well
as producing .ics format, so that you could do:

  $ python toIcal.py --rdf anyRDF.rdf >cal-constrained.rdf
  $ xsltproc toIcal.xsl cal-constrained.rdf >cal.ics

I'm not entirely sure what the point of that would be, though.

-- 
Dan Connolly, W3C http://www.w3.org/People/Connolly/
D3C2 887B 0F92 6005 C541  0875 0F91 96DE 6E52 C29E