Ticket #28 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

dc:date and content-type invalid in RSS feed

Reported by: dom Owned by: earle
Priority: normal Milestone:
Component: openguides Version: 0.51
Severity: normal Keywords:
Cc:

Description

http://purl.org/rss/1.0/modules/wiki/ which is referenced in the RDF/RSS feeds is 404ing and this causes http://www.feedvalidator.org/ to fail to validate our feeds.

Change History

Changed 3 years ago by ChristopherSchmidt

I don't think that this is actually the case. I agree that the feed validator does not validate the feeds, but the reason for it is not that the wiki: namespace is 404ing - or at least, it shouldn't be. RSS 1.0 makes no recommendations or requirements for namespaces to be active URLs. The fact that feedvalidator does not consider these feeds to be valid is in violation of the specification to my understandig of it, and is not something that requires changing on the part of OpenGuides.

The other issues that the FeedValidator? brings up are valid, though, and should be changed: The dc:date fields are not in W3CDTF, nor is the content-type correct.

Changed 3 years ago by Earle Martin

The fact that feedvalidator does not consider these feeds to be valid is in violation of the specification to my understandig of it

As far as I can see there's nothing wrong with the namespace either. On the other hand,

The dc:date fields are not in W3CDTF, nor is the content-type correct.

Right. The former is a bug in CGI::Wiki::Plugin::RSS::ModWiki. The latter is a bug in OpenGuides::RDF. I'm on both.

Changed 3 years ago by dom

  • summary changed from Missing reference to wiki xmlns. to dc:date and content-type invalid in RSS feed

Changed 3 years ago by earle

  • owner set to earle

Changed 3 years ago by earle

  • status changed from new to assigned

Changed 3 years ago by dom

  • component set to openguides

Changed 3 years ago by earle

  • status changed from assigned to closed
  • resolution set to fixed

(In [718]) fixes #28

Note: See TracTickets for help on using tickets.