A Model-Based Privacy Compliance Checker

3 More Discussions You Might Find Interesting

1. What is on Your Mind?

UNIX.COM General Data Privacy Regulations (GDPR) Compliance - For Member Comments

Dear All, Please read version Version 0.81 28 May 2018 of our draft UNIX.COM General Data Privacy Regulations (GDPR) Compliance. If you have any data privacy questions or concerns, or would like to see us address any other data privacy topic related to your personal data at UNIX.COM,...

2. OS X (Apple)

POSIX compliance...

Thanks to all you guys about posix compliance I have learnt an enormous amount over the last few days. I have written a program that is an Egg Timer with simple animation. I now realise how sophisticated 'bash' is compared to full posix compliance. The code below has passed all of the tests from...

3. What is on Your Mind?

Small Model Guitars Based on Artist - Have You Seen These?

Today I was in the market place and found this new shop that sells small models of guitars, categorized by the artists who played them. Have you seen these before? What do you think? Is this something anyone would collect?

LEARN ABOUT DEBIAN

xml::dom::valparser

XML::DOM::ValParser(3pm)				User Contributed Perl Documentation				  XML::DOM::ValParser(3pm)

NAME

       XML::DOM::ValParser - an XML::DOM::Parser that validates at parse time

SYNOPSIS

	use XML::DOM::ValParser;

	my %expat_options = (KeepCDATA => 1,
			     Handlers => [ Unparsed => &my_Unparsed_handler ]);
	my $parser = new XML::DOM::ValParser (%expat_options);

	eval {
	    local $XML::Checker::FAIL = &my_fail;
	    my $doc = $parser->parsefile ("fail.xml");
	    ... XML::DOM::Document was created sucessfully ...
	};
	if ($@) {
	    # Either XML::Parser (expat) threw an exception or my_fail() died.
	    ... your error handling code here ...
	    # Note that the XML::DOM::Document is automatically disposed off and
	    # will be garbage collected
	}

	# Throws an exception (with die) when an error is encountered, this
	# will stop the parsing process.
	# Don't die if a warning or info message is encountered, just print a message.
	sub my_fail {
	    my $code = shift;
	    die XML::Checker::error_string ($code, @_) if $code < 200;
	    XML::Checker::print_error ($code, @_);
	}

DESCRIPTION

       Use XML::DOM::ValParser wherever you would use XML::DOM::Parser and your XML will be checked using XML::Checker at parse time.

       See XML::DOM for details on XML::DOM::Parser options.  See XML::Checker for details on setting the fail handler (my_fail.)

       The following handlers are currently supported, just like XML::DOM::Parser: Init, Final, Char, Start, End, Default, Doctype, CdataStart,
       CdataEnd, XMLDecl, Entity, Notation, Proc, Default, Comment, Attlist, Element, Unparsed.

XML
::DOM::ValParser
       XML::DOM::ValParser extends from XML::Checker::Parser. It creates an XML::Checker object and routes all event handlers through the checker,
       before processing the events to create the XML::DOM::Document.

       Just like XML::Checker::Parser, the checker object can be retrieved with the getChecker() method and can be reused later on (provided that
       the DOCTYPE section of the XML::DOM::Document did not change in the mean time.)

       You can control which errors are fatal (and therefore should stop creation of the XML::DOM::Document) by filtering the appropriate error
       codes in the global $XML::Checker::FAIL handler (see "ERROR_HANDLING" in XML::Checker) and calling die or croak appropriately.

       Just like XML::Checker::Parser, XML::DOM::ValParser supports the SkipExternalDTD and SkipInsignifWS options. See XML::Checker::Parser for
       details.

AUTHOR

       Enno Derksen is the original author.

       Send bug reports, hints, tips, suggestions to T.J. Mather at <tjmather@tjmather.com>.

SEE ALSO

       XML::DOM, XML::Checker ("SEE_ALSO" in XML::Checker)

perl v5.10.0							    2001-08-26						  XML::DOM::ValParser(3pm)

UNIX and Linux RSS News