ISSUE-43: hint at naming a resource on creation


hint at naming a resource on creation

Linked Data Platform Spec
Raised by:
Henry Story
Opened on:
There are many cases when creating resources the user
would like to be able to suggest the name
or the final part of the name of the resource created
(excluding the extension). It makes sense for example
that a foaf profile be named by a URI ending in
"card" when created in a collection.

So for example if one POSTs a foaf Profile to a


a client may like it to be called "card" ie have the URL


Or if joe wishes to create an image in a collection that
he names "Family on the Beach" he would like the server
to not just name the resource


but perhaps more something like


Of course the server may not respect this for good reasons
such as the server having a policy of only giving obscure names to
resources for security reasons to avoid information leakage through
names, or in order because strict adherence to the name would create
a name clash with an existing resource.
Related Actions Items:
Related emails:
  1. LDP Rec (from on 2015-02-20)
  2. Re: Question regarding POST versus PUT for creating an LDPC (from on 2013-04-19)
  3. Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (from on 2013-04-05)
  4. Re: naming resources - Slug-Header - ISSUE-43 (from on 2013-01-10)
  5. Re: naming resources - Slug-Header - ISSUE-43 (from on 2013-01-10)
  6. ldp-ISSUE-43 (slug): hint at naming a resource on creation [Linked Data Platform core] (from on 2013-01-08)

Related notes:

One proposal is to simply use the Slug Header from the Atom Protocol

Henry Story, 8 Jan 2013, 12:31:56

Another proposal is for the server to use some relation in the RDF content to guide his naming.

See discussion:

Henry Story, 8 Jan 2013, 12:33:40

Resolution: Use slug.


Arnaud Le Hors, 14 Mar 2013, 04:05:17

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: 43.html,v 1.1 2015/08/17 04:43:09 denis Exp $