W3C home > Mailing lists > Public > public-rww@w3.org > December 2017

Re: Announcement: Fedora API Specification Candidate Recommendation

From: Melvin Carvalho <melvincarvalho@gmail.com>
Date: Tue, 5 Dec 2017 17:40:04 +0100
Message-ID: <CAKaEYh+8am2YTx5DiviRD96ZdVm4vpOAHis8y6Xa6US-+=C4qA@mail.gmail.com>
To: "Mark A. Matienzo" <mark.matienzo@gmail.com>
Cc: public-rww <public-rww@w3.org>
On 30 November 2017 at 19:49, Mark A. Matienzo <mark.matienzo@gmail.com>
wrote:

> Hello All,
> In case you have not seen, a specification is coming out of the Fedora
> digital repositories community (http://fedorarepository.org/) which
> extends from the LDP 1.0 Recommendation.
>
> There may be synergistic value in potentially bringing some of the
> elements in the Fedora specification into the LDP effort, such as:
> * Resource Versioning (Memento)
> * Resource Authorization (Web Access Controls)
> * Notifications (Activity Streams)
> * Extended Binary Resource Operations
> ** Fixity (HTTP headers)
> ** Referenced Content via message/external-body Content-Type
>
> Please indicate if you have an interest in incorporating any of the above
> into the LDP-Next effort or creating a more explicit connection between
> these standards.
>

Hi Mark

Thanks for sharing.  I havent read through the whole spec yet.  But I
suspect the Web Access Control part will be of interest to some in this
group.


>
> Regards,
> Andrew Woods
>
> ****** Announcement below ******
>
> The Candidate Recommendation of the Fedora API Specification is now
> available for public review.
>
> https://fedora.info/spec
>
> As described in the charter [1], this specification is designed to:
> 1. Define the characteristics and expectations of how clients interact
> with Fedora implementations
> 2. Define such interactions such that an implementation’s conformance is
> testable
> 3. Enable interoperability by striving to minimize the need for
> modifications to client applications in order to work with different
> implementations of the Fedora API specification
>
> The core HTTP and notification services defined in this specification are
> listed below, along with the associated standards from which they are
> derived:
> * Resource Management (Linked Data Platform)
> * Resource Versioning (Memento)
> * Resource Authorization (Web Access Controls)
> * Notifications (Activity Streams)
> * Extended Binary Resource Operations
> ** Fixity (HTTP headers)
> ** Referenced Content via message/external-body Content-Type
>
> This announcement for public comment on the Candidate Recommendation marks
> the beginning of a projected two-month period within which time we are
> targeting the release of the full Recommendation. Minimum requirements for
> transitioning to releasing the Recommendation include:
> * Specification compliance test suite
> * Two or more implementations of the specification
> * No unresolved, outstanding critical issues, as defined by the
> specification editors [2]
>
> Please contact the Fedora Community [3] or Fedora Specification Editors
> [4] with any general comments. Any comments on details of the
> specification, itself, should be posted as GitHub issues [5].
>
> Regards,
> Andrew Woods (on behalf of the Specification Editors and the Fedora
> Leadership)
>
> [1] https://github.com/fcrepo/fcrepo-specification/wiki/Fedora-A
> PI-Specification-Charter#fedora-api-specification-charter
> [2] https://github.com/fcrepo/fcrepo-specification/wiki/Fedora-A
> PI-Specification-Charter#editorial-team-membership-and-selection
> [3] fedora-community@googlegroups.com
> [4] fedora-specification-editors@googlegroups.com
> [5] https://github.com/fcrepo/fcrepo-specification/issues
>
>
>
Received on Tuesday, 5 December 2017 16:40:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:11:07 UTC