Ah, I wasn't aware of that - I thought that content had to be provided.

> -----Original Message-----
> From: Edwin Shin [mailto:[email protected]] 
> Sent: 17 June 2010 15:45
> To: Fedora Users
> Subject: Re: [Fedora-commons-users] Update Object FOXML
> 
> 
> 
> On 17 Jun 2010, at 4:35 PM, Steve Bayliss wrote:
> <snip>
> > One thing that is lacking from the current APIs is the 
> ability to create an
> > object from scratch without using FOXML (though the FOXML 
> needed to create a
> > "blank" object is pretty minimal).  There's an open issue for this -
> > http://fedora-commons.org/jira/browse/FCREPO-684 (though 
> this is cloning
> > rather than creating a "blank" object).
> 
> sort of. From a client perspective, the REST-API's Ingest 
> method lets you create an empty object (although under the 
> hood the REST API is actually ingesting a new object using a 
> "blank" FOXML template). For example, issue a POST request to 
> http://example.org/fedora/objects/new. The response's 
> location header provides the new "blank" object's URL and the 
> response body returns the pid of the new object.
> --------------------------------------------------------------
> ----------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate 
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
> lucky parental unit.  See the prize list and enter to win: 
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> Fedora-commons-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
> 


------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Fedora-commons-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fedora-commons-users

Reply via email to