ARC SPARQL+ Endpoint (v2011-12-01)

This interface implements SPARQL and SPARQL+ via HTTP Bindings.

Enabled operations: select, construct, ask, describe, dump

Max. number of results : 2600


Output format (if supported by query type):
jsonp/callback (for JSON results)
API key (if required)
Show results inline:
Change HTTP method: GET POST
<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf=""

  <rdf:Description rdf:about="">
    <rdf:type rdf:resource=""/>
    <ns1:sameAs rdf:resource=""/>
    <ns2:label xml:lang="en">Microsoft Animated Cursor Format</ns2:label>
    <ns3:description xml:lang="en">Animated Cursor Format (ANI), also known as Windows NT Animated Cursor, is a chunk-based bitmap format developed by Microsoft, based on the generic Resource Interchange File Format (RIFF) specification developed by Microsoft and IBM. Structurally, an ANI file is composed of a number of chunks, each comprising a four character code chunk identifier, the chunk size, and the chunk data. It comprises a RIFF header with an ANI data type identifier, followed by a series of chunks which contain two or more bitmaps stored in an ANI file. Each bitmap is typically either a Windows cursor or icon data, but may also be raw, uncompressed bitmaps. Additional information stored in the ANI file controls the rate and the sequence in which each frame is displayed. 
Furthe information regarding this and other RIFF formats can be found at</ns3:description>
    <ns0:isDeprecated rdf:datatype="">false</ns0:isDeprecated>
    <ns0:formatType rdf:resource=""/>
    <ns4:hasMagic rdf:datatype="">true</ns4:hasMagic>
    <ns0:hasPRONOMContainerMagic rdf:datatype="">false</ns0:hasPRONOMContainerMagic>
    <ns0:hasPRONOMBinaryMagic rdf:datatype="">true</ns0:hasPRONOMBinaryMagic>
    <ns2:seeAlso rdf:resource=""/>
    <ns5:P1072 rdf:resource=""/>
    <ns5:P1072 rdf:resource=""/>
    <ns5:P1072 rdf:resource=""/>

<!-- query time: 0.0085248947143555 -->