> On 17 Dec 2019, at 14:10, Mikael Pesonen <[email protected]> wrote: > > Thanks for the link, answer #2 is how we could do it with SPARQL. I'm still > interested in how user should tell in data that service has to create ID. Is > there some standard notation for <INSERT NEW ID HERE> ?
IIRC, the LDP protocol has something along those lines. If you send an HTTP POST with an RDF payload to a URI representing a container of resources, any empty relative URIs (<> in Turtle) will be treated as <INSERT NEW ID HERE>. The container chooses the URI. I haven't looked at LDP in a while, forgive me if I get some details wrong. Richard > > On 17/12/2019 15.56, Richard Cyganiak wrote: >> See here for some (non-Jena-specific) approaches and discussion: >> >> https://stackoverflow.com/questions/55635814/best-approach-to-create-uris-with-sparql-like-auto-increment >> >> >>> On 17 Dec 2019, at 13:44, Mikael Pesonen <[email protected]> wrote: >>> >>> Hi, >>> >>> not directly about Jena/Fuseki but hope someone can help. >>> >>> When posting new metadata into db, for example as turtle, user have to have >>> the resource IDs generated: >>> >>> <http://example.com/1234> a foaf:Document . >>> ... >>> >>> Is there a standard way to have the service, either Jena or some other >>> layer, to generate the ID for the user. >>> So in that case user could send >>> >>> <INSERT NEW ID HERE> a foaf:Document . >>> ... >>> >>> and service would replace <INSERT NEW ID HERE> with >>> <http://example.com/1234> and return the ID for the user. > > -- > Lingsoft - 30 years of Leading Language Management > > www.lingsoft.fi > > Speech Applications - Language Management - Translation - Reader's and > Writer's Tools - Text Tools - E-books and M-books > > Mikael Pesonen > System Engineer > > e-mail: [email protected] > Tel. +358 2 279 3300 > > Time zone: GMT+2 > > Helsinki Office > Eteläranta 10 > FI-00130 Helsinki > FINLAND > > Turku Office > Kauppiaskatu 5 A > FI-20100 Turku > FINLAND >
