xml file format
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 4865
XML User Profiles 0.2.3
XML User Profiles is a system that allows for remote and transferable user accounts. more>>
XUP is an attempt to replace static per-site user accounts, which most present dynamic web sites use in absence of an easy to use and open/shared user account system. It allows people to use a single account or profile with many sites, or one of their existing user profiles on multiple other web sites.
It is best suited to so called "community" sites, where the account serves mainly for lax identification of people among each other. It does not stipulate strong authentication (while OpenID or LID can be used) and is therefore only useful for applications with mediocre security and privacy demands.
Chat and discussion sites are the main target, but profiles in different applications can often also be enriched with them. They are meant to get used secondarily (as alternative) to static/local user accounts.
The XML format of user profiles is extremely simple, as is the associated login service API. Both are outlined and explained in the introduction (HTML). The format is basically an XMLified vCard with a few additions targetted at online/web communities. It is easy to parse and generate and therefore also suitable for profile exchange or import.
Theres also a more authoritative RFC-style text version of the current proposal, which provides further hints and explanations for implementors. Future extensions will get listed in the project Wiki however (field names in the XUP format are not regulated).
This effort is quite new, and therefore only very few actual (real-world) implementations are known so far.
Some software, like discussion boards (which mostly suffer from spaghetti code), are of course hard to extent with XML User Profiles. Even those that abstract their internal user database and UI logic reasonably well can often be difficult to adapt. It is however expected that the more professional systems will sooner than later be XUP compatible.
<<lessIt is best suited to so called "community" sites, where the account serves mainly for lax identification of people among each other. It does not stipulate strong authentication (while OpenID or LID can be used) and is therefore only useful for applications with mediocre security and privacy demands.
Chat and discussion sites are the main target, but profiles in different applications can often also be enriched with them. They are meant to get used secondarily (as alternative) to static/local user accounts.
The XML format of user profiles is extremely simple, as is the associated login service API. Both are outlined and explained in the introduction (HTML). The format is basically an XMLified vCard with a few additions targetted at online/web communities. It is easy to parse and generate and therefore also suitable for profile exchange or import.
Theres also a more authoritative RFC-style text version of the current proposal, which provides further hints and explanations for implementors. Future extensions will get listed in the project Wiki however (field names in the XUP format are not regulated).
This effort is quite new, and therefore only very few actual (real-world) implementations are known so far.
Some software, like discussion boards (which mostly suffer from spaghetti code), are of course hard to extent with XML User Profiles. Even those that abstract their internal user database and UI logic reasonably well can often be difficult to adapt. It is however expected that the more professional systems will sooner than later be XUP compatible.
Download (0.23MB)
Added: 2005-07-08 License: GPL (GNU General Public License) Price:
1570 downloads
XMLLiterate 1.0.0.7
XMLLiterate is framework for literate programming using XML. more>>
XMLLiterate is framework for literate programming using XML. XMLLiterate uses the STL and patterns extensively and runs on all platforms supported by Boost.
Most of the current programming systems allow you to use an IDE to generate all of the different parts of your code, and then you generate documentation, re-factor the code etc.
XMLLiterate works differently. In your project directory you have a folder called "literate" which contains all the files necessary to represent your program at a very high level. You are basically working directly on the "story" (or Web) of your program in XML.
When you want to study documentation of your work so far, you "Weave" your story into some type of documentation. We create DocBook XML files, and then from that we also generate HTML files. But you could get all the DocBook stuff and easily make PDFs etc.
When you have some type of design of your program, you can "Tangle" your story into actual program code, build files, data files or whatever.
The story of your program is built using an XML file format that we call "schema" which is simply a bunch of definitions for code in XML format.
Installation:
When you have a good build, you can install the tangle program and the weave script as "tangle" and "weave" by running simple scripts that make aliases in the correct place on your system. You will be asked for your password, so type it.
# sbin/install_weave.sh
# sbin/install_tangle.sh
Although tangle is a real program that we provide (since we have our own scripting tool), weave actually uses XSLT so you wont find a "weave" program. Check sbin/weave.sh to see how we weave.
The last step is to setup the location of your root xmlliterate folder so that you can place other projects in different folders. Edit "files.xml" in the root and change "[change to your cppliterate path]" entry to the full path of your cppliterate folder. On my machine, the entry looks like:
< xmlliterateroot >/usr/src/cppliterate< xmlliterateroot >
Enhancements:
- A huge speed up of tangle by doing delayed loading of files.
- Only needed xi:includes are actually imported.
- This release generates Java code correctly, so you can use this for Java development.
- There are many other bugfixes and changes.
- The project now uses Subversion instead of CVS.
<<lessMost of the current programming systems allow you to use an IDE to generate all of the different parts of your code, and then you generate documentation, re-factor the code etc.
XMLLiterate works differently. In your project directory you have a folder called "literate" which contains all the files necessary to represent your program at a very high level. You are basically working directly on the "story" (or Web) of your program in XML.
When you want to study documentation of your work so far, you "Weave" your story into some type of documentation. We create DocBook XML files, and then from that we also generate HTML files. But you could get all the DocBook stuff and easily make PDFs etc.
When you have some type of design of your program, you can "Tangle" your story into actual program code, build files, data files or whatever.
The story of your program is built using an XML file format that we call "schema" which is simply a bunch of definitions for code in XML format.
Installation:
When you have a good build, you can install the tangle program and the weave script as "tangle" and "weave" by running simple scripts that make aliases in the correct place on your system. You will be asked for your password, so type it.
# sbin/install_weave.sh
# sbin/install_tangle.sh
Although tangle is a real program that we provide (since we have our own scripting tool), weave actually uses XSLT so you wont find a "weave" program. Check sbin/weave.sh to see how we weave.
The last step is to setup the location of your root xmlliterate folder so that you can place other projects in different folders. Edit "files.xml" in the root and change "[change to your cppliterate path]" entry to the full path of your cppliterate folder. On my machine, the entry looks like:
< xmlliterateroot >/usr/src/cppliterate< xmlliterateroot >
Enhancements:
- A huge speed up of tangle by doing delayed loading of files.
- Only needed xi:includes are actually imported.
- This release generates Java code correctly, so you can use this for Java development.
- There are many other bugfixes and changes.
- The project now uses Subversion instead of CVS.
Download (0.14MB)
Added: 2006-04-05 License: Freely Distributable Price:
1298 downloads
Lingua::Phonology::FileFormatPOD 0.32
Lingua::Phonology::FileFormatPOD is a Perl module that contains documentation for the xml file format. more>>
Lingua::Phonology::FileFormatPOD is a Perl module that contains documentation for the xml file format written and read by Lingua::Phonology.
As of v0.3, Lingua::Phonology is able to read and write an XML file that defines a complete Lingua::Phonology object. This file is meant to be human-editable, so you can write a phonology definition in a text file and then load it using Lingua::Phonology. Your perl script itself can be quite minimal, as most of the work of creating your phonology is done in the file.
For example, the following script reads the phonology defined in my_phono.xml, then reads a list of underlying forms from STDIN, applies the rules to them, and writes the surface forms to phono.out.
use Lingua::Phonology;
my $phono = new Lingua::Phonology;
$phono->loadfile(my_phono.xml);
open OUT, >phono.out or die $!;
while (< >) {
chomp $_;
# The following assumes one word per line. It also assumes that all of
# our symbols are one character and that there are no diacritics.
# Implementing this script if any of the preceding are false is left as
# an exercise to the reader.
@word = $phono->symbols->segment(split //, $_);
$phono->rules->apply_all(@word);
print OUT $phono->symbols->spell(@word), "n";
}
Of course, having this be successful depends on my_phono.xml working properly. The rest of this document describes how to do that.
<<lessAs of v0.3, Lingua::Phonology is able to read and write an XML file that defines a complete Lingua::Phonology object. This file is meant to be human-editable, so you can write a phonology definition in a text file and then load it using Lingua::Phonology. Your perl script itself can be quite minimal, as most of the work of creating your phonology is done in the file.
For example, the following script reads the phonology defined in my_phono.xml, then reads a list of underlying forms from STDIN, applies the rules to them, and writes the surface forms to phono.out.
use Lingua::Phonology;
my $phono = new Lingua::Phonology;
$phono->loadfile(my_phono.xml);
open OUT, >phono.out or die $!;
while (< >) {
chomp $_;
# The following assumes one word per line. It also assumes that all of
# our symbols are one character and that there are no diacritics.
# Implementing this script if any of the preceding are false is left as
# an exercise to the reader.
@word = $phono->symbols->segment(split //, $_);
$phono->rules->apply_all(@word);
print OUT $phono->symbols->spell(@word), "n";
}
Of course, having this be successful depends on my_phono.xml working properly. The rest of this document describes how to do that.
Download (0.097MB)
Added: 2006-09-16 License: Perl Artistic License Price:
1134 downloads
LRpt::XMLReport 0.16
LRpt::XMLReport is a Perl module for converting outputs generated by LReport tools to XML format. more>>
LRpt::XMLReport is a Perl module for converting outputs generated by LReport tools to XML format.
SYNOPSIS
lrptxml.pl --selects=selects.txt --keys_file=keys.txt data
lrptxml.pl --diffs --selects=selects.txt --keys_file=rkeys.txt diffs.txt
LRpt::XMLReport is a part of LRpt (LReport) library. It used to convert outputs generated by other tools from LReport suite to XML format. You should not call this class directly from your code. Instead you should use lrptxml.pl tool, which is a simple wrapper around this module. It looks like this:
use strict;
use LRpt::XMLReport;
create_report( @ARGV );
COMMAND LINE SWITCHES
--selects=file
Optional. Name of a selects file (see doc). They are included in the report for a select of corresponding name. If selects are not given, report will not contain selects.
--diffs
Switches working mode to read output of lcsvdiff.pl. If not given the working mode is reading csv files from a directory
--keys_file=keys_file
File name containing row key definitions.
<<lessSYNOPSIS
lrptxml.pl --selects=selects.txt --keys_file=keys.txt data
lrptxml.pl --diffs --selects=selects.txt --keys_file=rkeys.txt diffs.txt
LRpt::XMLReport is a part of LRpt (LReport) library. It used to convert outputs generated by other tools from LReport suite to XML format. You should not call this class directly from your code. Instead you should use lrptxml.pl tool, which is a simple wrapper around this module. It looks like this:
use strict;
use LRpt::XMLReport;
create_report( @ARGV );
COMMAND LINE SWITCHES
--selects=file
Optional. Name of a selects file (see doc). They are included in the report for a select of corresponding name. If selects are not given, report will not contain selects.
--diffs
Switches working mode to read output of lcsvdiff.pl. If not given the working mode is reading csv files from a directory
--keys_file=keys_file
File name containing row key definitions.
Download (0.082MB)
Added: 2007-06-12 License: Perl Artistic License Price:
864 downloads
XML::DifferenceMarkup 1.00
XML::DifferenceMarkup is a XML diff and merge. more>>
XML::DifferenceMarkup is a XML diff and merge.
SYNOPSIS
use XML::DifferenceMarkup qw(make_diff);
$parser = XML::LibXML->new();
$parser->keep_blanks(0);
$d1 = $parser->parse_file($fname1);
$d2 = $parser->parse_file($fname2);
$dom = make_diff($d1, $d2);
print $dom->toString(1);
This module implements an XML diff producing XML output. Both input and output are DOM documents, as implemented by XML::LibXML.
The diff format used by XML::DifferenceMarkup is meant to be human-readable (i.e. simple, as opposed to short) - basically the diff is a subset of the input trees, annotated with instruction element nodes specifying how to convert the source tree to the target by inserting and deleting nodes. To prevent name colisions with input trees, all added elements are in a namespace http://www.locus.cz/diffmark (the diff will fail on input trees which already use that namespace).
<<lessSYNOPSIS
use XML::DifferenceMarkup qw(make_diff);
$parser = XML::LibXML->new();
$parser->keep_blanks(0);
$d1 = $parser->parse_file($fname1);
$d2 = $parser->parse_file($fname2);
$dom = make_diff($d1, $d2);
print $dom->toString(1);
This module implements an XML diff producing XML output. Both input and output are DOM documents, as implemented by XML::LibXML.
The diff format used by XML::DifferenceMarkup is meant to be human-readable (i.e. simple, as opposed to short) - basically the diff is a subset of the input trees, annotated with instruction element nodes specifying how to convert the source tree to the target by inserting and deleting nodes. To prevent name colisions with input trees, all added elements are in a namespace http://www.locus.cz/diffmark (the diff will fail on input trees which already use that namespace).
Download (0.056MB)
Added: 2007-08-17 License: Perl Artistic License Price:
798 downloads
XMLStarlet 1.0.1
XMLStarlet is a command line XML toolkit. more>>
XMLStarlet is a set of command line utilities (tools) which can be used to transform, query, validate, and edit XML documents and files using simple set of shell commands in similar way it is done for plain text files using UNIX grep, sed, awk, diff, patch, join, etc commands.
This set of command line utilities can be used by those who deal with many XML documents on UNIX shell command prompt as well as for automated XML processing with shell scripts.
Main features:
- Check or validate XML files (simple well-formedness check, DTD, XSD, RelaxNG)
- Calculate values of XPath expressions on XML files (such as running sums, etc)
- Search XML files for matches to given XPath expressions
- Apply XSLT stylesheets to XML documents (including EXSLT support, and passing parameters to stylesheets)
- Query XML documents (ex. query for value of some elements of attributes, sorting, etc)
- Modify or edit XML documents (ex. delete some elements)
- Format or "beautify" XML documents (as changing indentation, etc)
- Fetch XML documents using http:// or ftp:// URLs
- Browse tree structure of XML documents (in similar way to ls command for directories)
- Include one XML document into another using XInclude
- XML c14n canonicalization
- Escape/unescape special XML characters in input text
- Print directory as XML document
- Convert XML into PYX format (based on ESIS - ISO 8879), and vice versa
XMLStarlet command line utility is written in C and uses libxml2 and libxslt from http://xmlsoft.org/.
Implementation of extensive choice of options for XMLStarlet utility was only possible because of rich feature set of libxml2 and libxslt (many thanks to the developers of those libraries for great work).
diff and patch options are not currently implemented. Other features need some work too. Please, send an email to the project administrator (see http://sourceforge.net/projects/xmlstar/) if you wish to help.
XMLStarlet is linked statically to both libxml2 and libxslt, so generally all you need to process XML documents is one executable file. To run XmlStarlet utility you can simple type xml on command line and see list of options available.
XMLStarlet is open source freeware under MIT license which allows free use and distribution for both commercial and non-commercial projects.
<<lessThis set of command line utilities can be used by those who deal with many XML documents on UNIX shell command prompt as well as for automated XML processing with shell scripts.
Main features:
- Check or validate XML files (simple well-formedness check, DTD, XSD, RelaxNG)
- Calculate values of XPath expressions on XML files (such as running sums, etc)
- Search XML files for matches to given XPath expressions
- Apply XSLT stylesheets to XML documents (including EXSLT support, and passing parameters to stylesheets)
- Query XML documents (ex. query for value of some elements of attributes, sorting, etc)
- Modify or edit XML documents (ex. delete some elements)
- Format or "beautify" XML documents (as changing indentation, etc)
- Fetch XML documents using http:// or ftp:// URLs
- Browse tree structure of XML documents (in similar way to ls command for directories)
- Include one XML document into another using XInclude
- XML c14n canonicalization
- Escape/unescape special XML characters in input text
- Print directory as XML document
- Convert XML into PYX format (based on ESIS - ISO 8879), and vice versa
XMLStarlet command line utility is written in C and uses libxml2 and libxslt from http://xmlsoft.org/.
Implementation of extensive choice of options for XMLStarlet utility was only possible because of rich feature set of libxml2 and libxslt (many thanks to the developers of those libraries for great work).
diff and patch options are not currently implemented. Other features need some work too. Please, send an email to the project administrator (see http://sourceforge.net/projects/xmlstar/) if you wish to help.
XMLStarlet is linked statically to both libxml2 and libxslt, so generally all you need to process XML documents is one executable file. To run XmlStarlet utility you can simple type xml on command line and see list of options available.
XMLStarlet is open source freeware under MIT license which allows free use and distribution for both commercial and non-commercial projects.
Download (0.50MB)
Added: 2005-04-03 License: Freeware Price:
1666 downloads
XML::DocStats 0.01
XML::DocStats is a Perl module to produce a simple analysis of an XML document. more>>
XML::DocStats is a Perl module to produce a simple analysis of an XML document.
SYNOPSIS
Analyze the xml document on STDIN, the STDOUT output format is html:
use XML::DocStats;
my $parse = XML::DocStats->new;
$parse->analyze;
Analyze in-memory xml document:
use XML::DocStats;
my ($xmldata) = @_;
my $parse = XML::DocStats->new(xmlsource=>{String => $xmldata},
BYTES => length($xmldata));
$parse->analyze;
Analyze xml document IO stream, the output format is plain text:
use XML::DocStats;
use IO::File;
my $xmlsource = IO::File->new("< document.xml");
my $parse = XML::DocStats->new(xmlsource=>{ByteStream => $xmlsource});
$parse->format(text);
$parse->analyze;
XML::DocStats parses an xml document using a SAX handler built using Ken MacLeods XML::Parser::PerlSAX. It produces a listing indented to show the element heirarchy, and collects counts of various xml components along the way. A summary of the counts is produced following the conclusion of the parse. This is useful to visualize the structure and content of an XML document.
The output listing is either in plain text or html.
Each xml thingy is color-coded in the html output for easy reading:
- purple denotes elements.
- blue denotes text (character data). The text itself is black.
- olive denotes attributes and attribute valuesin elements, XML-DCL, DOCTYPE, and PIs.
- fuchsia denotes entity references. The name of the entity is in black. fuchsia is also used to denote the root element, and to mark the start and finish of the parse, as well as to label the statistices at the end.
- teal denotes the XML declaration.
- navy denotes the DOCTYPE declaration.
- maroon denotes PIs (processing instructions).
- green denotes comments. The text of the comment is black.
- red denotes error messages should the xml fail to be well-formed.
<<lessSYNOPSIS
Analyze the xml document on STDIN, the STDOUT output format is html:
use XML::DocStats;
my $parse = XML::DocStats->new;
$parse->analyze;
Analyze in-memory xml document:
use XML::DocStats;
my ($xmldata) = @_;
my $parse = XML::DocStats->new(xmlsource=>{String => $xmldata},
BYTES => length($xmldata));
$parse->analyze;
Analyze xml document IO stream, the output format is plain text:
use XML::DocStats;
use IO::File;
my $xmlsource = IO::File->new("< document.xml");
my $parse = XML::DocStats->new(xmlsource=>{ByteStream => $xmlsource});
$parse->format(text);
$parse->analyze;
XML::DocStats parses an xml document using a SAX handler built using Ken MacLeods XML::Parser::PerlSAX. It produces a listing indented to show the element heirarchy, and collects counts of various xml components along the way. A summary of the counts is produced following the conclusion of the parse. This is useful to visualize the structure and content of an XML document.
The output listing is either in plain text or html.
Each xml thingy is color-coded in the html output for easy reading:
- purple denotes elements.
- blue denotes text (character data). The text itself is black.
- olive denotes attributes and attribute valuesin elements, XML-DCL, DOCTYPE, and PIs.
- fuchsia denotes entity references. The name of the entity is in black. fuchsia is also used to denote the root element, and to mark the start and finish of the parse, as well as to label the statistices at the end.
- teal denotes the XML declaration.
- navy denotes the DOCTYPE declaration.
- maroon denotes PIs (processing instructions).
- green denotes comments. The text of the comment is black.
- red denotes error messages should the xml fail to be well-formed.
Download (0.027MB)
Added: 2006-09-07 License: Perl Artistic License Price:
1143 downloads
XML-CompareML 0.2.0
XML::CompareML is a Perl module for managing multi-system and multi-item comparisons. more>>
The primary use of this module by its author was to manage the Better SCM comparison of version control systems.
The Perl versions can generate either HTML or DocBook/XML. (the latter can be converted into many other formats). Also available is an XSLT stylesheet for transforming the XML markup into HTML.
<<lessThe Perl versions can generate either HTML or DocBook/XML. (the latter can be converted into many other formats). Also available is an XSLT stylesheet for transforming the XML markup into HTML.
Download (0.017MB)
Added: 2007-03-20 License: Perl Artistic License Price:
948 downloads
XML::Atom 0.19
XML::Atom is an Atom feed and API implementation. more>>
XML::Atom is an Atom feed and API implementation.
SYNOPSIS
use XML::Atom;
Atom is a syndication, API, and archiving format for weblogs and other data. XML::Atom implements the feed format as well as a client for the API.
<<lessSYNOPSIS
use XML::Atom;
Atom is a syndication, API, and archiving format for weblogs and other data. XML::Atom implements the feed format as well as a client for the API.
Download (0.058MB)
Added: 2006-06-30 License: Perl Artistic License Price:
1211 downloads
Simple XML Configuration Library 0.3.6
Simple XML Configuration Library an XML library for parsing a simple configuration file format. more>>
Simple XML Configuration Library an XML library for parsing a simple configuration file format.
Simple XML Configuration Library is actively developed for *nix, Mac OS X and *BSD. The goal of the project is to provide a library that can be easily wrapped into other languages such as Python and Java.
Installation:
- run: build.sh
- run: ./configure
- run: make
- run: make install
Enhancements:
- fixed memory leak on name allocations and in Destroy
<<lessSimple XML Configuration Library is actively developed for *nix, Mac OS X and *BSD. The goal of the project is to provide a library that can be easily wrapped into other languages such as Python and Java.
Installation:
- run: build.sh
- run: ./configure
- run: make
- run: make install
Enhancements:
- fixed memory leak on name allocations and in Destroy
Download (0.022MB)
Added: 2006-03-30 License: GPL (GNU General Public License) Price:
1305 downloads
XML::Mini::Element::Comment 1.2.8
XML::Mini::Element::Comment is used internally to represent <!-- comments -->. more>>
XML::Mini::Element::Comment is used internally to represent .
You shouldnt need to use it directly, see XML::Mini::Elements comment() method.
<<lessYou shouldnt need to use it directly, see XML::Mini::Elements comment() method.
Download (0.034MB)
Added: 2007-03-16 License: GPL (GNU General Public License) Price:
953 downloads
FeedCreator 1.7.2
FeedCreator provides a PHP class that builds various XML-based news feed formats. more>>
FeedCreator provides a PHP class that builds various XML-based news feed formats.
FeedCreator (formerly RSSCreator) is a PHP class that provides an easy way to create various mostly XML-based feeds from within PHP.
It is compact, easy to use, and well documented. RSS 0.91, 1.0, and 2.0, ATOM 0.3, OPML 1.0, and Unix mbox are supported.
Main features:
- creates valid feeds according to RSS 0.91, 1.0 or 2.0 as well as PIE 0.1 (deprecated), OPML 1.0, Unix mbox, ATOM 0.3, or customizable HTML or Javascript format.
- configurable feed caching
- very well documented and easy to use
- Feed image
- includes almost all RSS 0.91 attributes
- decide which version to create during runtime
- easy to use and well documented class interface
- intelligently truncates strings when needed
Enhancements:
- changed license to LGPL
<<lessFeedCreator (formerly RSSCreator) is a PHP class that provides an easy way to create various mostly XML-based feeds from within PHP.
It is compact, easy to use, and well documented. RSS 0.91, 1.0, and 2.0, ATOM 0.3, OPML 1.0, and Unix mbox are supported.
Main features:
- creates valid feeds according to RSS 0.91, 1.0 or 2.0 as well as PIE 0.1 (deprecated), OPML 1.0, Unix mbox, ATOM 0.3, or customizable HTML or Javascript format.
- configurable feed caching
- very well documented and easy to use
- Feed image
- includes almost all RSS 0.91 attributes
- decide which version to create during runtime
- easy to use and well documented class interface
- intelligently truncates strings when needed
Enhancements:
- changed license to LGPL
Download (0.22MB)
Added: 2007-02-22 License: LGPL (GNU Lesser General Public License) Price:
979 downloads
XML::Generator::RSS10::dc 0.01
XML::Generator::RSS10::dc adds support for the Dublin Core (dc) RSS 1.0 module. more>>
XML::Generator::RSS10::dc adds support for the Dublin Core (dc) RSS 1.0 module.
SYNOPSIS
use XML::Generator::RSS10;
my $rss = XML::Generator::RSS10->new( Handler => $sax_handler );
$rss->channel( title => Pants,
link => http://pants.example.com/,
description => A fascinating pants site,
content =>
{ items =>
[ { format => http://www.w3.org/1999/xhtml,
content => < b >Axis< /b > Love,
},
{ format => http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional,
about => http://example.com/content-elsewhere,
},
{ format => http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional,
encoding => http://www.w3.org/TR/REC-xml#dt-wellformed,
content => < i >italics< /i >,
},
],
},
);
<<lessSYNOPSIS
use XML::Generator::RSS10;
my $rss = XML::Generator::RSS10->new( Handler => $sax_handler );
$rss->channel( title => Pants,
link => http://pants.example.com/,
description => A fascinating pants site,
content =>
{ items =>
[ { format => http://www.w3.org/1999/xhtml,
content => < b >Axis< /b > Love,
},
{ format => http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional,
about => http://example.com/content-elsewhere,
},
{ format => http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional,
encoding => http://www.w3.org/TR/REC-xml#dt-wellformed,
content => < i >italics< /i >,
},
],
},
);
Download (0.019MB)
Added: 2007-08-17 License: Perl Artistic License Price:
798 downloads
VTD-XML 2.1
VTD-XML is a non-extractive XML processing software API implementing Virtual Token Descriptor. more>>
VTD-XML is a "non-extractive" XML processing software API implementing Virtual Token Descriptor. Currently, VTD-XML only supports built-in entity references (" &s ><<less
Download (0.64MB)
Added: 2007-06-16 License: GPL (GNU General Public License) Price:
863 downloads
AnyData::Format::XML 0.10
AnyData::Format::XML is a Perl module for tiedhash and DBI access to XML. more>>
AnyData::Format::XML is a Perl module for tiedhash and DBI access to XML.
SYNOPSIS
# access XML data via a multi-dimensional tied hash
# see AnyData.pod for full details
#
use AnyData;
my $table = adTie( XML, $file, $mode, $flags );
OR
# convert data to and from XML
# see AnyData.pod for full details
#
use AnyData;
adConvert( XML, $file1, $any_other_format, $file2, $flags );
adConvert( $any_other_format, $file1, XML, $file2, $flags );
OR
# access the data via DBI and SQL
# see DBD::AnyData.pod for full details
#
use DBI;
my $dbh = DBI->connect( dbi:AnyData );
$dbh->func(mytable,XML,$file,$flags,ad_catalog);
See below for a description of the optional flags that apply to all of these examples.
This module allows you to create, search, modify and/or convert XML data and files by treating them as databases without having to actually create separate database files. The data can be accessed via a multi-dimensional tiedhash using AnyData.pm or via DBI and SQL commands using DBD::AnyData.pm. See those modules for complete details of usage.
The module is built on top of Michel Rodriguezs excellent XML::Twig which means that the AnyData interfaces can now include information from DTDs, be smarter about inferring data structure, reduce memory consumption on huge files, and provide access to many powerful features of XML::Twig and XML::Parser on which it is based.
Importing options allow you to import/access/modify XML of almost any length or complexity. This includes the ability to access different subtrees as separate or joined databases.
Exporting and converting options allow you to take data from almost any source (a perl array, any DBI database, etc.) and output it as an XML file. You can control the formating of the resulting XML either by supplying a DTD listing things like nesting of tags and which columns should be output as attributes and/or you can use XML::Twig pretty_print settings to generate half a dozen different levels of compactness or whitespace in how the XML looks.
The documentaion below outlines the special flags that can be used in either of the interfaces to fine-tune how the XML is treated.
The flags listed below define the relationship between tags and attributes in the XML document and columns in the resulting database. In many cases, you can simply accept the defaults and the database will be built automatically. However, you can also fine tune the generation of the database by specifying which tags and attributes you are interested in and their relationship with database columns.
<<lessSYNOPSIS
# access XML data via a multi-dimensional tied hash
# see AnyData.pod for full details
#
use AnyData;
my $table = adTie( XML, $file, $mode, $flags );
OR
# convert data to and from XML
# see AnyData.pod for full details
#
use AnyData;
adConvert( XML, $file1, $any_other_format, $file2, $flags );
adConvert( $any_other_format, $file1, XML, $file2, $flags );
OR
# access the data via DBI and SQL
# see DBD::AnyData.pod for full details
#
use DBI;
my $dbh = DBI->connect( dbi:AnyData );
$dbh->func(mytable,XML,$file,$flags,ad_catalog);
See below for a description of the optional flags that apply to all of these examples.
This module allows you to create, search, modify and/or convert XML data and files by treating them as databases without having to actually create separate database files. The data can be accessed via a multi-dimensional tiedhash using AnyData.pm or via DBI and SQL commands using DBD::AnyData.pm. See those modules for complete details of usage.
The module is built on top of Michel Rodriguezs excellent XML::Twig which means that the AnyData interfaces can now include information from DTDs, be smarter about inferring data structure, reduce memory consumption on huge files, and provide access to many powerful features of XML::Twig and XML::Parser on which it is based.
Importing options allow you to import/access/modify XML of almost any length or complexity. This includes the ability to access different subtrees as separate or joined databases.
Exporting and converting options allow you to take data from almost any source (a perl array, any DBI database, etc.) and output it as an XML file. You can control the formating of the resulting XML either by supplying a DTD listing things like nesting of tags and which columns should be output as attributes and/or you can use XML::Twig pretty_print settings to generate half a dozen different levels of compactness or whitespace in how the XML looks.
The documentaion below outlines the special flags that can be used in either of the interfaces to fine-tune how the XML is treated.
The flags listed below define the relationship between tags and attributes in the XML document and columns in the resulting database. In many cases, you can simply accept the defaults and the database will be built automatically. However, you can also fine tune the generation of the database by specifying which tags and attributes you are interested in and their relationship with database columns.
Download (0.043MB)
Added: 2006-09-13 License: Perl Artistic License Price:
1137 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above xml file format search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
