W3C home > Mailing lists > Public > public-ldp-wg@w3.org > November 2012

Re: Documenting an an explicit URI to be used for representing POSTed new LDPC members

From: <steve.battle@sysemia.co.uk>
Date: Thu, 1 Nov 2012 08:26:51 +0000
Message-Id: <CD116318-921B-4FF0-A3B5-54147E3B7AA1@sysemia.co.uk>
To: "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
I like David Wood's criteria that we shouldn't need to introspect POSTed RDF. This proposal would require the server to introspect the RDF looking for occurrences of '#_new' , potentially slowing down processing.


On 30 Oct 2012, at 17:40, Olivier Berger <olivier.berger@it-sudparis.eu> wrote:

> Hi.
> I'm not sure I've been able to read all the discussions about the (base)
> URI of newly created LDPC members, when using POST to create
> them. Here's another proposal which I hope is not redundant. Pardon me
> in advance as I'm a novice in SemWeb compared to the eminent members of
> the WG.
> Let's say I want to add new members (reusing Example 2's URIs) to
> <http://example.org/netWorth/nw1>'s (sub-)container(s).
> So, let's say I should be POSTing to a its "factory"/POST enpoint
> <http://example.org/netWorth/nw1/assetContainer> a resource looking like
> the following :
> @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
> @prefix ldp: <http://www.w3.org/ns/ldp#>.
> @prefix o: <http://example.org/ontology/>.
> <http://example.org/netWorth/nw1/assetContainer#_new>
>   a o:Stock;
>   o:value 10000.
> So, this factory_URI + '#_new' could be mandated by the specs to
> represent the URI in the posted resource, by convention (it's very
> unlikely to have a confusion between that one and other URIs of
> predicates or values.
> Would such a convention on a special fragment for representing the
> POSTed resource help solve the base URI discussions ?
> We could also make it less a convention, but an explicit URI, provided
> by the container/factory.
> So we could even render this '#_new' relative fragment explicit, as
> provided in a "ldp:newResourceUri" property of the Container(Factory)
> (which would be an optional property, and if provided, SHOULD be
> different from the Container(Factory)'s URI, otherwise it doesn't bring
> anything new to the current specs ;) :
> (Reusing the class names and example I provided in my other post
> Message-ID: <871ugfj37a.fsf@inf-8657.int-evry.fr>), that'd make (if you
> prefer "#_tobecreated" to "#_new":
> @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
> @prefix ldp: <http://www.w3.org/ns/ldp#>.
> @prefix o: <http://example.org/ontology/>.
> <http://example.org/netWorth/nw1/assetContainer>
>   ldp:ContainerFactory;
>   ldp:newResourceUri <http://example.org/netWorth/nw1/assetContainer#_tobecreated>;
>   ldp:membershipSubject <http://example.org/netWorth/nw1>;
>   ldp:membershipPredicate o:asset.
> <http://example.org/netWorth/nw1>
>   a o:NetWorth, ldp:IndirectContainer;
>   ldp:creationFactory <http://example.org/netWorth/nw1/assetContainer>;
>   o:asset
>      <http://example.org/netWorth/nw1/assetContainer/a1>,
>      <http://example.org/netWorth/nw1/assetContainer/a2>.
> Again, hoping that it makes sense and helps.
> Best regards,
> -- 
> Olivier BERGER 
> http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
> Ingenieur Recherche - Dept INF
> Institut Mines-Telecom, Telecom SudParis, Evry (France)

Steve Battle

Steve Battle
Semantic Engineer

E-mail: steve.battle@sysemia.co.uk
Web: www.sysemia.com

Sysemia Limited
The Innovation Centre, Bristol&  Bath Science Park, Dirac Crescent, Emerson's Green, Bristol BS16 7FR
Registered in England and Wales. Company Number: 7555456


Information contained in this e-mail is intended for the use of the addressee only, and is confidential and may also be privileged. If you receive this message in error, please advise us immediately. If you are not the intended recipient(s), please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. Attachments to this e-mail may contain software viruses which may damage your systems. Sysemia Ltd have taken reasonable steps to minimise this risk, but we advise that any attachments are virus checked before they are opened.
Received on Thursday, 1 November 2012 08:27:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:17:33 UTC