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

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

Subject Item

n2:id

rdf:type

schema:EntryPoint

schema:httpMethod

GET

schema:contentType

text/xml

n3:isWebServiceOf

n7:this_ODSInstanceModuleAPI

n3:endPointURL

n4:id

schema:shortDescription

<p>Get the id of an ODS app instance. </p>

n3:hasParameter

n6:_instanceName

schema:name

EntryPoint - instance_get_id

schema:description

<p>Each ODS app has a unique numeric id which is required for almost all operations. This method allows to determine that id from the app instance's name (App instance names are oftern something like "foobar's Calendar").</p><p><parameterlist kind="param"><li> <parameternamelist> <parametername>instanceName</parametername> </parameternamelist> <parameterdescription> <p>The name of the app instance.</p></parameterdescription> </li> </ul> <simplesect kind="return"><p>An error code as defined in <ref kindref="member" refid="ods_response_format_1ods_response_format_result_code">ODS Error Result Codes</ref> which in this case matches the instance id.</p></simplesect> <simplesect kind="see"><p><ref kindref="member" refid="group__ods__module__instance_1ods_instance_id">ODS App Instance Ids</ref></p></simplesect> <simplesect kind="par"><title>Authentication</title><p>This function requries authentication via one of the supported authentication methods as described in <ref kindref="compound" refid="ods_authentication">ODS Authentication</ref>.</p></simplesect> <bold>Example:</bold> <pre> $ curl -i "http://www.iodbc.org/ods/api/instance.get.id?instanceName=Demo%20account%27s%20Briefcase&amp;sid=c198c56e675abd9967b2b264d1119ae2" HTTP/1.1 200 OK Server: Virtuoso/05.12.3041 (Solaris) x86_64-sun-solaris2.10-64 VDB Connection: Keep-Alive Date: Tue, 01 Dec 2009 12:39:19 GMT Accept-Ranges: bytes Content-Type: text/xml; charset="ISO-8859-1" Content-Length: 57 &lt;result&gt; &lt;code&gt;6&lt;/code&gt; &lt;message&gt;Success&lt;/message&gt; &lt;/result&gt; </pre> </p>

schema:url

n4:id