RE: [TF-PP] Property Paths use cases

Luke,

The essence seems to be that the path is in the template part of a CONSTRUCT (used in DELETE).  I've added an example to this effect.

	Andy

> -----Original Message-----
> From: Luke Wilson-Mawer [mailto:luke.wilson-mawer@garlik.com]
> Sent: 4 August 2009 14:01
> To: Seaborne, Andy
> Cc: SPARQL Working Group
> Subject: Re: [TF-PP] Property Paths use cases
> 
> Seaborne, Andy wrote:
> > ((To help tracking I've added [TF-PP]  Is there a way to tie email about
> this task force automatically to the wiki?))
> >
> > http://www.w3.org/2009/sparql/wiki/TaskForce:PropertyPaths

> >
> > To start, I'd like to compile some use cases to help us understand the
> problem space, the limitations and requirements.
> >
> > There are a few in the examples on the feature page [1] that include
> subclass and simple cases of just convenient abbreviation so there is a
> starting point there.  I've extracted those to seed the discussion.
> Please add more.  Getting coverage matters so a written description
> without concrete example is just as helpful.
> >
> There is a slightly speculative update/property paths use case here:
> http://www.w3.org/2009/sparql/wiki/EditingFoafData#Use_Case_2.

> > 	Andy
> >
> > [1] http://www.w3.org/2009/sparql/wiki/Feature:PropertyPaths

> >
> >