Re: LDP Next Community Group Status Update

Hello Adam and All,
Indeed, if we are unable to get updates into the ldp-testsuite, we will
need another way of keeping that valuable resource current. It may make
sense to roll a fork as "ldp-next-testsuite" into the new GitHub repo:
https://github.com/w3c/ldp-next

Andrew

On Thu, Sep 29, 2016 at 12:20 PM, A. Soroka <ajs6f@virginia.edu> wrote:

> I've got one to add right away. {grin}
>
> The LDP Test Suite is a very useful piece of software, but the code base
> has been formally frozen by its maintainers:
>
> https://github.com/w3c/ldp-testsuite/issues/229#issuecomment-249553975
>
> This isn't ideal for a number of reasons. There are several pull requests
> into it now to correct problems or just update dependencies. Like any
> software product, lacking regular maintenance it will become harder and
> harder to integrate or use with "younger" software. The maintainers have
> suggested that LDPNext could play a role here, and that makes a lot of
> sense to me.
>
> Perhaps a discussion point for the next call?
>
> ---
> A. Soroka
> The University of Virginia Library
>
> > On Sep 29, 2016, at 12:09 PM, Cody Burleson <cody.burleson@base22.com>
> wrote:
> >
> > Team,
> >
> > Slowly, but surely, we’re making some progress.
> >
> > In our last meeting, we discussed opening a GitHub repo and we’ve gotten
> that done now (shout out to Sandro for the help). Please watch, star, pin,
> or bookmark the following:
> >
> > https://github.com/w3c/ldp-next
> >
> > We can use that repository for documenting the next specification / and
> or extensions and for issue tracking. I imagine that we can simply use
> markdown for documentation for a little while and avoid wrestling with
> Respec and formal W3C spec styling until we’re closer to having something
> of substance.
> >
> > Following are the top 4 issues that have surfaced for continued
> discussion so far:
> >
> > ·         If-Match and Weak ETags issue
> > o   We’re still trying to determine what’s the desired action/outcome
> for this. What are we to recommend?
> > ·         Inline on GET
> > o   We can start with defining the problem/gap to be solved and possible
> solutions. Then discuss.
> > ·         Inline on POST
> > o   We can start with defining the problem/gap to be solved and possible
> solutions. Then discuss.
> > ·         Paging
> > o   We can start with defining the problem/gap to be solved and possible
> solutions. Then discuss.
> >
> > Please feel free to contribute any thoughts or ideas regarding any of
> these points at any time (via this mailing list or LDPNext on Slack).
> >
> > The next web conference is scheduled for Thursday, October 6 from 2:00 –
> 3:30 PM CST.
> >
> > Thanks,
> >
> > Cody
> >
>
>
>