rdf::doap::changesets(3pm) [debian man page]

RDF::DOAP::ChangeSets(3pm)				User Contributed Perl Documentation				RDF::DOAP::ChangeSets(3pm)

NAME

       RDF::DOAP::ChangeSets - create pretty ChangeLogs from RDF

SYNOPSIS

	use RDF::DOAP::ChangeSets;
	use URI::file;

	my $file     = 'path/to/changelog.rdf';
	my $file_uri = URI::file->new_abs($file);

	my $dcs = RDF::DOAP::ChangeSets->new(
		    $file_uri, undef, undef, 'RDFXML');
	print $dcs->to_string;

DESCRIPTION

       This module takes software changelogs written in the RDF DOAP Change Sets vocabulary and produces human-readable changelogs.

       "RDF::DOAP::ChangeSets->new($uri, $data, $type, $fmt)"
	   Creates and initialises an object.

	   $uri is a URL for the input data. The URL is used to query the RDF data for the heading of the output changelog. It may be passed as
	   either a string, or a URI object.

	   $data is the RDF data to use as input. It may be passed as a string, or as an RDF::Trine::Model object. If undefined, this module will
	   attempt to read data from the URL using LWP::Simple.

	   $type gives the constructor a hint as to the RDF vocabulary you are using. For DOAP Change Sets, use 'current'; for Aaron Cope's
	   Changefile vocab, use 'legacy'; to autodetect, use 'auto'. By default, performs autodetection. This module may crash and burn if you
	   try to mix both vocabs!!

	   $fmt provides a hint as to what RDF format you're using. By default, Turtle is assumed. Valid values are whatever
	   RDF::Trine::Parser->new accepts.

       "$changeset->is_legacy"
	   Boolean, indicating if a legacy vocab is being used.

       "$changeset->is_current"
	   Boolean, indicating if the current vocab is being used.

       "$changeset->model"
	   RDF::Trine::Model object representing the changelog data.

       "$changeset->uri"
	   String representing the changelog URI.

       "$changeset->to_string"
	   Creates a human-readable representation of the changelog.

       "$changeset->to_file($filename)"
	   Same as "to_string", but outputs to a file.

BUGS

       Please report any bugs to <http://rt.cpan.org/>.

SEE ALSO

       RDF::Trine, CPAN::Changes::Spec, Module::Install::DOAPChangeSets.

       <http://www.perlrdf.org/>.

AUTHOR

       Toby Inkster <tobyink@cpan.org>.

COPYRIGHT

       Copyright 2010-2011 Toby Inkster

       This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

perl v5.14.2							    2012-01-18						RDF::DOAP::ChangeSets(3pm)

RDF::iCalendar::Exporter(3pm)				User Contributed Perl Documentation			     RDF::iCalendar::Exporter(3pm)

NAME

       RDF::iCalendar::Exporter - export RDF data to iCalendar format

SYNOPSIS

	use RDF::iCalendar;

	my $input    = "http://example.com/calendar-data.ics";
	my $exporter = RDF::iCalendar::Exporter->new;

	print $_ foreach $exporter->export_calendars($input);

DESCRIPTION

       This module reads RDF and writes iCalendar files.

       This is a subclass of RDF::vCard::Exporter, so it can also export vCards.

   Constructor
       o   "new(%options)"

	   Returns a new RDF::iCalendar::Exporter object.

	   There are no valid options at the moment - the hash is reserved for future use.

   Methods
       o   "export_calendars($input, %options)"

	   Returns a list of iCalendars found in the input, in no particular order.

	   The input may be a URI, file name, RDF::Trine::Model or anything else that can be handled by the "rdf_parse" method of
	   RDF::TrineShortcuts.

	   Each item in the list returned is an RDF::iCalendar::Entity, though that class overloads stringification, so you can just treat each
	   item as a string mostly.

       o   "export_calendar($input, $subject, %options)"

	   As per "export_calendars" but exports just a single calendar.

	   The subject provided must be an RDF::Trine::Node::Blank or RDF::Trine::Node::Resource of type icaltzd:Vcalendar.

       o   "export_component($input, $subject, %options)"

	   Exports a component from a calendar - e.g. a single VEVENT

	   The subject provided must be an RDF::Trine::Node::Blank or RDF::Trine::Node::Resource of type icaltzd:Vevent, icaltzd:Vtodo or similar.

       o   "export_cards($input, %options)"

	   See RDF::vCard::Exporter.

       o   "export_card($input, $subject, %options)"

	   See RDF::vCard::Exporter.

   RDF Input
       Input is expected to use the newer of the 2005 revision of the W3C's vCard vocabulary <http://www.w3.org/TR/rdfcal/>. (Note that even
       though this was revised in 2005, the term URIs include "2002" in them.)

       Some extensions from the namespace <http://buzzword.org.uk/rdf/icaltzdx#> are also supported.

   iCalendar Output
       The output of this module aims at iCalendar (RFC 2445) compliance.  In the face of weird input data though, (e.g. an DTSTART property that
       is a URI instead of a literal) it can pretty easily descend into exporting junk, non-compliant iCalendars.

       The output has barely been tested in any iCalendar-supporting software, so beware.

SEE ALSO

       RDF::iCalendar.

       RDF::vCard, HTML::Microformats, RDF::TrineShortcuts.

       <http://www.w3.org/TR/rdfcal/>.

       <http://www.perlrdf.org/>.

AUTHOR

       Toby Inkster <tobyink@cpan.org>.

COPYRIGHT

       Copyright 2011 Toby Inkster

       This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

perl v5.14.2							    2012-06-23					     RDF::iCalendar::Exporter(3pm)