Cool. Maybe the specification checkers should flag if this doesn't exist then?
On 14 Mar 2011, at 21:28, Richard Jones <rich...@oneoverzero.com> wrote: > > > On 24/02/11 16:22, David Tarrant wrote: >> >> On 24 Feb 2011, at 15:39, Ian Stuart wrote: >> >>> On 23/02/11 11:37, David Tarrant wrote: >>>> In simple terms yes, however because both the repository and client >>>> can be in control of an object then it is actually a lot more >>>> complex! >>>> >>>> Plus you have missed some obvious things, like the fact that people >>>> don't know, and don't care what a sword endpoint in, they just want >>>> to deposit. >>> I agree that **PEOPLE** just want to deposit, however **SYSTEMS** need >>> to work out where that is :) >> >> Indeed, i've solved that problem but no one cares :P >> >> link rel="Sword" href="http://service-doc"; >> link rel="SwordDeposit" href="http://a-deposit-endpoint"; > > FYI, See Section 4 of the SWORD 1.3 spec... > > http://www.swordapp.org/docs/sword-profile-1.3.html > > Cheers, > > Richard > > > > ------------------------------------------------------------------------------ > Colocation vs. Managed Hosting > A question and answer guide to determining the best fit > for your organization - today and in the future. > http://p.sf.net/sfu/internap-sfd2d > _______________________________________________ > Sword-app-techadvisorypanel mailing list > Sword-app-techadvisorypanel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sword-app-techadvisorypanel ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Sword-app-techadvisorypanel mailing list Sword-app-techadvisorypanel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sword-app-techadvisorypanel
