Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Aaron's use of RDF/N3 that you linked to is fascinating. He's integrated Dublin Core [dublincore.org] terms with DOAP [usefulinc.com] plus a "changefile" vocabulary of his own invention (although the schema for it seems yet to be written).

    The use of RDF as a change format has numerous benefits. A large amount of work has already put into constructing metadata vocabularies in it, which saves us from reinventing a big wheel with some crufty format based on YAML (as acme pointed out [perl.org], YAML is a failed format). RDF is also expressable in different forms: you can take the N3 as linked above and transform it to XML, and then almost everything can read it; or you can apply XSLT to the XML and transform it into something else (like the traditional "Changes" format). It's flexible and powerful.

    • I agree that it's a great format, but for most people it's painful to write.

      I'm also interested in the way microformats solve the RFC pain in XHTML, so that they use a rough standard in CSS class names or link@rel etc. so that we can automatically translate these XHTML into RDF later. Can we take a similar approach to that?