Should we be strict on processing errors?

Path	csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.datemas.de!rt.uk.eu.org!aioe.org!.POSTED!not-for-mail
From	Victor Porton <porton@narod.ru>
Newsgroups	comp.programming
Subject	Should we be strict on processing errors?
Date	Tue, 13 May 2014 19:01:55 +0300
Organization	Aioe.org NNTP Server
Lines	18
Message-ID	<lktflm$160$1@speranza.aioe.org> (permalink)
NNTP-Posting-Host	qr+7Oe/NCpbZDQ54JhCR5g.user.speranza.aioe.org
Mime-Version	1.0
Content-Type	text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding	7Bit
X-Complaints-To	abuse@aioe.org
User-Agent	KNode/4.12.4
X-Notice	Filtered by postfilter v. 0.8.2
Xref	csiph.com comp.programming:4405

Show key headers only | View raw

Suppose we have an RDF file (in XML format) downloaded from the Web.

This RDF contains information about several namespaces.

If it is detected that one of the namespaces is described with a semantic 
error, should we reject the entire RDF file or just the erroneous part?

Or maybe, to have both strict and non-strict mode of processing of errors?

Please give as many as possible arguments both pro and contra strict 
processing of errors. It is a serious noncommercial project and we need to 
take the right decision.

The project homepage currently is:
http://freesoft.portonvictor.org/namespaces.xml

-- 
Victor Porton - http://portonvictor.org

Back to comp.programming | Previous | Next | Find similar | Unroll thread

Thread

Should we be strict on processing errors? Victor Porton <porton@narod.ru> - 2014-05-13 19:01 +0300

csiph-web