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

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

Namespace Prefixes

PrefixIRI
dctermshttp://purl.org/dc/terms/
yago-reshttp://yago-knowledge.org/resource/
dbohttp://dbpedia.org/ontology/
foafhttp://xmlns.com/foaf/0.1/
n4https://global.dbpedia.org/id/
yagohttp://dbpedia.org/class/yago/
dbthttp://dbpedia.org/resource/Template:
rdfshttp://www.w3.org/2000/01/rdf-schema#
freebasehttp://rdf.freebase.com/ns/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
owlhttp://www.w3.org/2002/07/owl#
wikipedia-enhttp://en.wikipedia.org/wiki/
dbchttp://dbpedia.org/resource/Category:
dbphttp://dbpedia.org/property/
provhttp://www.w3.org/ns/prov#
xsdhhttp://www.w3.org/2001/XMLSchema#
goldhttp://purl.org/linguistics/gold/
wikidatahttp://www.wikidata.org/entity/
dbrhttp://dbpedia.org/resource/

Statements

Subject Item
dbr:OPOS
rdf:type
yago:Whole100003553 yago:Object100002684 yago:Instrumentality103575240 yago:WikicatRetailPOSSystems dbo:Place yago:PhysicalEntity100001930 yago:Artifact100021939 yago:System104377057
rdfs:label
OPOS
rdfs:comment
OPOS, full name OLE for Retail POS, a platform specific implementation of UnifiedPOS, is a point of sale device standard for Microsoft Windows operating systems that was initiated by Microsoft, NCR, Epson, and Fujitsu-ICL and is managed by the Association for Retail Technology Standards. The OPOS API was first published in January 1996. The standard uses component object model and, because of that, all languages that support COM controls (i.e. Visual C++, Visual Basic, and C#) can be used to write applications.
dcterms:subject
dbc:Standards dbc:Microsoft_application_programming_interfaces dbc:Retail_point_of_sale_systems
dbo:wikiPageID
9385791
dbo:wikiPageRevisionID
987151852
dbo:wikiPageWikiLink
dbr:Microsoft_Windows_CE dbr:Point_of_sale dbc:Microsoft_application_programming_interfaces dbr:Microsoft_Windows_8 dbc:Standards dbr:Operating_systems dbr:NCR_Corporation dbr:Visual_Basic dbr:Windows dbr:Visual_C++ dbr:Microsoft_Windows_XP dbr:Microsoft_Windows_7 dbr:Microsoft dbr:Microsoft_Windows_95 dbr:C_Sharp_(programming_language) dbr:Microsoft_Windows_NT dbr:Windows_Embedded dbr:Fujitsu dbc:Retail_point_of_sale_systems dbr:Microsoft_Windows_ME dbr:Object_Linking_and_Embedding dbr:Microsoft_Windows_Vista dbr:Epson dbr:Component_object_model dbr:Microsoft_Windows_98 dbr:Association_for_Retail_Technology_Standards dbr:Microsoft_Windows_2000 dbr:UnifiedPOS dbr:Microsoft_Windows_10
owl:sameAs
n4:4sYL5 freebase:m.0286sqk wikidata:Q7072847 yago-res:OPOS
dbp:wikiPageUsesTemplate
dbt:Use_dmy_dates
dbo:abstract
OPOS, full name OLE for Retail POS, a platform specific implementation of UnifiedPOS, is a point of sale device standard for Microsoft Windows operating systems that was initiated by Microsoft, NCR, Epson, and Fujitsu-ICL and is managed by the Association for Retail Technology Standards. The OPOS API was first published in January 1996. The standard uses component object model and, because of that, all languages that support COM controls (i.e. Visual C++, Visual Basic, and C#) can be used to write applications. The OPOS standard specifies two levels for an OPOS control, the control object which presents an abstract hardware interface to a family of devices such as receipt printer and the service object which handles the interface between the control object and the actual physical device such as a specific model of receipt printer. This division of functionality provides a way for the application development to write to an abstract hardware interface while allowing the application to work with a variety of different hardware. The only requirement is that a hardware vendor supplies an OPOS compatible service object with their particular hardware offering. Typically a manufacturer of point of sale terminals will provide along with a terminal operating system an OPOS control object package with a software utility that is used to configure OPOS settings. Such a utility will specify the settings for an OPOS control object and indicate the service object to be used with a particular OPOS profile. When the point of sale application starts up, it loads the OPOS control object and the OPOS control object in turn loads the service object specified by the current OPOS profile. The Windows Registry is typically used as the persistent store for device settings. The hardware device manufacturer will normally provide a utility for device specific settings used by the service object.
gold:hypernym
dbr:Point
prov:wasDerivedFrom
wikipedia-en:OPOS?oldid=987151852&ns=0
dbo:wikiPageLength
2984
foaf:isPrimaryTopicOf
wikipedia-en:OPOS