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:new

rdf:type

schema:EntryPoint

schema:httpMethod

GET

schema:contentType

text/xml

n3:isWebServiceOf

n6:this_ODSUserModuleAPI

n3:endPointURL

n4:new

schema:shortDescription

<p>Create a new private data graph. </p>

n3:hasParameter

n7:_name

schema:name

EntryPoint - user_dataGraphs_new

schema:description

<p>Each ODS user has a profile with fixed fields. These are managed via <ref kindref="member" refid="group__ods__module__user_1ga777818aa3df3994ecb3fc581e691c18a">user.update.fields()</ref>. In addition to that each user can store custom fields via <ref kindref="member" refid="group__ods__module__user_1ga2bf1904a63e0cda499071b2045488a8e">user.customFields.set()</ref>. If ODS has been configured to allow the creation of data graphs then each ODS user can in addition create an arbitrary number of private data graphs. Private data graphs are simply named graphs in the Virtuoso triple store which are only accessible to the ODS user (unless they define ACL rules to share the graph). This allows to store any kind of information of any complexity in an ODS user profile in a secure way.</p><p>Typically <computeroutput>SPARQL</computeroutput> Update queries (<ref kindref="member" refid="group__ods__module__query_1gaa414cfba762ecd76d5a58755ab7072f5">query.sparql()</ref>) will be used to fill the graphs with information.</p><p>One private data graph is already created when using <ref kindref="member" refid="group__ods__module__user_1ga2bf1904a63e0cda499071b2045488a8e">user.customFields.set()</ref>: <computeroutput><ulink url="http://HOST/dataspace/private/USER/customFields.">http://HOST/dataspace/private/USER/customFields.</ulink></computeroutput> This special graph should not be used to store addition data besides the custom fields, although it is theoretically possible.</p><p>This method allows to create these private data graphs.</p><p><parameterlist kind="param"><li> <parameternamelist> <parametername>name</parametername> </parameternamelist> <parameterdescription> <p>The name of the new graph. This will be incorporated into the graph URI. Ideally it should only contain lower-case letters and no spaces.</p></parameterdescription> </li> </ul> <simplesect kind="return"><p>The newly created graph in a turtle document or as a plain text URI, depending on the requested content type. On error a code as defined in <ref kindref="member" refid="ods_response_format_1ods_response_format_result_code">ODS Error Result Codes</ref> is returned and an appropriate HTTP status code is set:<itemizedlist> <listitem><p><computeroutput>409</computeroutput> - A graph with that name already exists and cannot be reused as a data graph.</p></listitem><listitem><p><computeroutput>405</computeroutput> - The given graph name refers to an already existing data graph.</p></listitem></itemizedlist> </p></simplesect> <simplesect kind="see"><p><ref kindref="member" refid="group__ods__module__user_1gae4a210b40f67d3263a23fc276d5f2ddd">user.dataGraphs.delete()</ref>, <ref kindref="member" refid="group__ods__module__user_1gaa383784d1c31a23a5687ddc25485e4e4">user.dataGraphs.list()</ref>, <ref kindref="member" refid="group__ods__module__user_1ga2bf1904a63e0cda499071b2045488a8e">user.customFields.set()</ref>, <ref kindref="member" refid="group__ods__module__acl_1gab1844fa8dc1ab8360a2117e0c8b0bd8e">acl.rules.new()</ref>, <ref kindref="member" refid="group__ods__module__query_1gaa414cfba762ecd76d5a58755ab7072f5">query.sparql()</ref> </p></simplesect> </p>

schema:url

n4:new