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
wdrs	http://www.w3.org/2007/05/powder-s#
schema	http://schema.org/
n5	https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/DAV/data/turtle/general/
n6	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#
n2	http://data.openlinksw.com/oplweb/faq/UDA/CanyouexplainOpenLinkinstallationfilenamingconventionsAnswer#
xsdh	http://www.w3.org/2001/XMLSchema#

Statements

Subject Item

n2:this

wdrs:describedby

n5:uda-faq.ttl n6:uda-faq.ttl

rdf:type

schema:Answer

schema:answerExplanation

OpenLink's installation archives follow an eight character naming convention. The first two characters represent the operating system, on which the product was compiled. The third and fourth characters represent the component type, i.e., client, database agent, request broker, Single-Tier driver. The remaining characters specify for which database a product is meant to connect. Generic components will contain a series of `x's or `z's in this field.