273342 - RDF iCal export uses deprecated RDF

Status: RESOLVED INVALID

(Calendar :: General, defect)

Description

[Daniel O'Connor]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

<rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns="http://www.w3.org/2000/10/swap/pim/ical#"
xmlns:i="http://www.w3.org/2000/10/swap/pim/ical#">
<Vcalendar rdf:about="">
<version>2.0</version>
<prodid>-//Mozilla.org/NONSGML Mozilla Calendar V 1.0 //EN</prodid>
</Vcalendar>
<Vevent>
<uid>61df8bf0-4768-11d9-976b-84c004c34bbf</uid>
<summary>fdgfg</summary>
<description/>
<categories/>
<status/>
<class resource="http://www.w3.org/2000/10/swap/pim/ical#private"/>
<dtstart parseType="Resource">
<value>20041225T092500Z</value>
</dtstart>
<dtstamp>20041205T225240Z</dtstamp>
<due/>
</Vevent>
</rdf:RDF>

When validated, gives:
Warning: {W101} Unqualified use of rdf:resource has been deprecated.[Line = 15,
Column = 68]
Warning: {W101} Unqualified use of rdf:parseType has been deprecated.[Line = 16,
Column = 31]

Solution:
All instances of the "resource" attribute should be prefixed with the rdf:
namespace.

Reproducible: Always
Steps to Reproduce:
1. Export an event as RDF
2. Paste RDF to http://www.w3.org/RDF/Validator


Actual Results:  
Warning: {W101} Unqualified use of rdf:resource has been deprecated.[Line = 15,
Column = 68]
Warning: {W101} Unqualified use of rdf:parseType has been deprecated.[Line = 16,
Column = 31]

Expected Results:  
Valid RDF

Comment 1

[gekacheka]

Confirmed.

Comment 2

[gekacheka]

Attachment: replacement for xcs2rdf.xsl (result passes verifier)

calendar/resources/content/converters/xcs2rdf.xsl

Diagnosis:  problem was that in the xsl transform file, the rdf namespace was
not defined around the xsl:templates for the vtodo and vevent, so the rdf in
rdf:parseType was unbound.  Solution to this problem is to also define the
namespaces on the top level xsl:stylesheet element.  (They must still appear on
the RDF element so they appear in the output as well.)

This replacement also makes a few updates:
* the ical namespace url is updated to the 2002 version
  (see http://www.w3.org/2002/12/cal/)
* removed nested element inside dtstart, no longer used in the 2002 version.
* added missing event properties that appear in the xcs (xCAL) file,
  including location, dtend, rrule, valarm
* removed that rdf:about=""
 
http://esw.w3.org/topic/RdfCalendarDocumentation#head-d21d3fbaaed6578a5d57264533457fcc4377b57a

* used the UID to generate a rdf:ID
* nested vcalendar/component/vevent (component is the relation)
 
http://esw.w3.org/topic/RdfCalendarDocumentation#head-660090e9c34296c5b6cd2b677a2b568c1a2b6171


Using this updated file, tested exported rdf files pass the rdf validator at
http://www.w3.org/RDF/Validator/

Comment 3

[Simon Paquet [:sipaq]]

Comment on attachment 174180 [details]
replacement for xcs2rdf.xsl (result passes verifier)

Moving review request to Joey, since Mostafah is pretty at the moment.

Comment 4

[Mostafa Hosseini]

> Moving review request to Joey, since Mostafah is pretty at the moment.
Thanks for the compliment :)

Comment 5

[Joey Minta]

Comment on attachment 174180 [details]
replacement for xcs2rdf.xsl (result passes verifier)

I'm completely ignorant on what needs to be done here/what the problems are.  Switching review over to mvl.

Comment 6

[Michiel van Leeuwen (email: mvl+moz@)]

I also have no idea what the problem here is. Is there any use-case for exporting to rdf? (And even then, this code will never be called anymore)

Comment 7

[Dan Mosedale (:dmosedale, :dmose)]

After trolling the web a bit, the only thing I can find that RDF calendar is useful for is if you want to mix calendar data with other RDF data in order to do some sort of querying on the combined dataset.  I'm having a hard time imagining an end-user ever wanting to do this, so this sure seems out of scope for a calendar client to me.  I vote we cvs remove that file instead.

Comment 8

[Daniel O'Connor]

(In reply to comment #7)
> ... the only thing I can find that RDF calendar is
> useful for is if you want to mix calendar data with other RDF data in order to
> do some sort of querying on the combined dataset.

Exporting data to applications such as EventSherpa (http://www.eventsherpa.com/) & PiggyBank(http://simile.mit.edu/piggy-bank/). Admittedly, there's few applications out there that make use of iCal as RDF and the end user is unlikely to have them installed. Applications for the end user that would fall into this space would be found under the topic of "Semantic Desktop" (http://www.google.com/search?q=semantic+desktop)

Comment 9

[Joey Minta]

(In reply to comment #8)
> (In reply to comment #7)
> Exporting data to applications such as EventSherpa
> (http://www.eventsherpa.com/) & PiggyBank(http://simile.mit.edu/piggy-bank/).
> Admittedly, there's few applications out there that make use of iCal as RDF and
> the end user is unlikely to have them installed. Applications for the end user
> that would fall into this space would be found under the topic of "Semantic
> Desktop" (http://www.google.com/search?q=semantic+desktop)
> 
I think the relevant question is: Are there any programs out there that *only* accept RDF, but do not accept standard iCalendar?  If the end-user can export as iCal, then the rdf export is superfluous.

Comment 10

[Daniel O'Connor]

> I think the relevant question is: Are there any programs out there that *only*
> accept RDF, but do not accept standard iCalendar?  If the end-user can export
> as iCal, then the rdf export is superfluous.

PiggyBank (http://simile.mit.edu/piggy-bank/) would be an example of an RDF only application - it's not specifically a calendaring application but rather a general information store that speaks RDF.

Comment 11

[Michiel van Leeuwen (email: mvl+moz@)]

Comment on attachment 174180 [details]
replacement for xcs2rdf.xsl (result passes verifier)

There is no xcs export anymore, so until that's back, removing this from my queue.

Comment 12

[Matthew (lilmatt) Willis]

Reassigning all automatically assigned bugs from Mostafa to nobody@m.o

Bugspam filter: TorontoMostafaMove

Comment 13

[Stefan Sitter [:ssitter]]

Are there any plans to add RDF export back to Sunbird/Lightning core? If not this bug should be closed. Maybe this can be implemented and provided as an extension, similar to the existing VCS export extension?

Comment 14

[Martin Schröder [:mschroeder]]

(In reply to comment #13)
> Are there any plans to add RDF export back to Sunbird/Lightning core? If not
> this bug should be closed. Maybe this can be implemented and provided as an
> extension, similar to the existing VCS export extension?

No response. So, we resolve this as INVALID because the feature does not exist anymore, and it is unlikely to come back.