There is some need to specify type of object in the triple. Object
relationships are serialized like

<demo:someRelation rdf:resource="info:fedora/demo:targetpid/>

while literal relations are serialized like

<demo:someRelation>Literalvalue</demo:someRelation>

And the format is optional. There need to be some hint to fedora about
which of the two ways a relation should be serialized.

Regards


On Wed, 2009-10-28 at 06:27 +0100, Benjamin Armintor wrote:
> Regarding the relationship methods: Is there a need to specify the
> type of the object in the triple?  I'm presuming that the api should
> support object literals. Maybe elaborating  it as:
> /objects/{pid}/relations/{relationname}/to/{objID}[/as/{format}]
> 
> with the bracketed portion optional (although I don't like some of the
> implications of defaulting to URI as the type).
> 
> I tried looking at Mulgara's docs for guidance
> ( http://www.mulgara.org/trac/wiki/RESTInterface ), but they don't
> specify a rule for distinguishing a URI and a string literal (for
> example) as the object of a relationship.
> 
> - Ben 
> 
> On Tue, Oct 27, 2009 at 4:05 PM, David Kennedy
> <david.kenn...@duke.edu> wrote:
>         Asger, 
>         
>         I like your proposal.  I also like the approach you are
>         taking, starting with identifying the resources, and their
>         resource urls.  The resource URLs and http methods all seem
>         appropriate to me. 
>         
>         Nice work. 
>         
>         As you get farther along with this, I do agree with Elliot
>         that it will be important to document status codes, headers
>         and representations where appropriate.   
>         
>         Dave 
>         
>         -----
>         David Kennedy
>         Application Developer
>         Perkins Library, Duke University
>         (919) 613-6831
>         david.kenn...@duke.edu 
>         
>         
>         
>         From:
>         Asger Askov Blekinge
>         <a...@statsbiblioteket.dk>
>         To:
>         Peter Cliff
>         <peter.cl...@ouls.ox.ac.uk>
>         Cc:
>         "Schwichtenberg, Frank"
>         <frank.schwichtenb...@fiz-karlsruhe.de>, 
> "fedora-commons-developers@lists.sourceforge.net" 
> <fedora-commons-developers@lists.sourceforge.net>
>         Date:
>         10/27/2009 01:41 PM
>         Subject:
>         Re: [Fedora-commons-developers]
>         Fedora REST interface, a
>         proposal for methods
>         
>         
>         ______________________________________________________________
>         
>         
>         
>         
>         Hi Guys
>         
>         I created a wiki page with my proposal.
>         http://fedora-commons.org/confluence/display/DEV/Alternative
>         +REST+API
>         
>         I would appreciate it, if you would give it a look, and tell
>         me what you
>         think of the idea?
>         
>         Regards
>         
>         On Tue, 2009-10-27 at 17:02 +0100, Peter Cliff wrote:
>         > Surely the best thing to do would have two methods:
>         > 
>         > GET /createNew &
>         > GET /createExisting/{pid}
>         > 
>         > ;-)
>         > 
>         > (I'm joking!!)
>         > 
>         > Pete Cliff
>         > OULS
>         > 
>         > On Tue, 2009-10-27 at 10:32 -0400, Elliot Metsger wrote:
>         > > On Oct 27, 2009, at 10:27 AM, Schwichtenberg, Frank wrote:
>         \
>         > > > If the PID is previously known and can be included in
>         the URL (/ 
>         > > > objects/{pid}) I would say definitely PUT. In case of
>         create without  
>         > > > PID I would agree with POST but would send it
>         to /objects.
>         > > > Appended with create seems to mean calling the
>         create-method.
>         > > 
>         > > I agree with Frank and David on just using /objects... no
>         need for  
>         > > "create"
>         > > 
>         > >
>         
> ------------------------------------------------------------------------------
>         > > Come build with us! The BlackBerry(R) Developer Conference
>         in SF, CA
>         > > is the only developer event you need to attend this year.
>         Jumpstart your
>         > > developing skills, take BlackBerry mobile applications to
>         market and stay 
>         > > ahead of the curve. Join us from November 9 - 12, 2009.
>         Register now!
>         > > http://p.sf.net/sfu/devconference
>         > > _______________________________________________
>         > > Fedora-commons-developers mailing list
>         > > Fedora-commons-developers@lists.sourceforge.net
>         > >
>         https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
>         > 
>         >
>         
> ------------------------------------------------------------------------------
>         > Come build with us! The BlackBerry(R) Developer Conference
>         in SF, CA
>         > is the only developer event you need to attend this year.
>         Jumpstart your
>         > developing skills, take BlackBerry mobile applications to
>         market and stay 
>         > ahead of the curve. Join us from November 9 - 12, 2009.
>         Register now!
>         > http://p.sf.net/sfu/devconference
>         > _______________________________________________
>         > Fedora-commons-developers mailing list
>         > Fedora-commons-developers@lists.sourceforge.net
>         >
>         https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
>         
>         
>         
> ------------------------------------------------------------------------------
>         Come build with us! The BlackBerry(R) Developer Conference in
>         SF, CA
>         is the only developer event you need to attend this year.
>         Jumpstart your
>         developing skills, take BlackBerry mobile applications to
>         market and stay 
>         ahead of the curve. Join us from November 9 - 12, 2009.
>         Register now!
>         http://p.sf.net/sfu/devconference
>         _______________________________________________
>         Fedora-commons-developers mailing list
>         Fedora-commons-developers@lists.sourceforge.net
>         https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
>         
>         
>         
>         
>         
> ------------------------------------------------------------------------------
>         Come build with us! The BlackBerry(R) Developer Conference in
>         SF, CA
>         is the only developer event you need to attend this year.
>         Jumpstart your
>         developing skills, take BlackBerry mobile applications to
>         market and stay
>         ahead of the curve. Join us from November 9 - 12, 2009.
>         Register now!
>         http://p.sf.net/sfu/devconference
>         _______________________________________________
>         Fedora-commons-developers mailing list
>         Fedora-commons-developers@lists.sourceforge.net
>         https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
>         
> 


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Fedora-commons-developers mailing list
Fedora-commons-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers

Reply via email to