This HTML5 document contains 4 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

Prefix	IRI
n2	http://data.openlinksw.com/oplweb/faq/UDA/HowDoIInterpretNameOfTazFilesAnswer#
wdrs	http://www.w3.org/2007/05/powder-s#
schema	http://schema.org/
n4	https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/DAV/data/turtle/general/
n5	https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/data/turtle/general/
rdf	http://www.w3.org/1999/02/22-rdf-syntax-ns#
xsdh	http://www.w3.org/2001/XMLSchema#

Statements

Subject Item

n2:this

wdrs:describedby

n4:uda-faq.ttl n5:uda-faq.ttl

rdf:type

schema:Answer

schema:answerExplanation

.taz file names are useful for detecting product and operating system incompatibilities. (Failure to install, core dumps, segmentation faults, signals, and blatant incompatibility errors are all possible side effects of product and OS mismatch.) If you suspect an incompatibility, obtain the name of the .taz file and a uname -a from the affected machine. Decode the .taz file name to see if it was intended for the user's operating system.