Seems to me there's overlaps but so many differences it's not clear
there's much impact either way.
LDA predates the LDP and was mentioned as one of the inputs to it,
though I'm not sure LDP really benefited from the LDA lessons. LDP
provides a read/write API around collections. LDA provides a read-only
API covering collections and items with delivery in multiple formats. I
don't think LDP has any of the notions of filtering and customizable
views and renders that are central to most of our uses of LDA.
Link Data Registry (LDR) is different. That was developed as LDP was
just starting so in designing LDR we tried to follow the LDP submission
including all the weird mix of naming conventions. Of course, LDR was
complete and in use rather before LDP finalized (advantage of a
committee of two!). The final LDP standard was a bit different from the
starting point, which left us with the question of whether to change LDR
to match. We decided not - due to a mix of legacy and lack of funding.
It would be reasonable for someone to look at what a second generation
LDR based on the LDP standard might look like. However, it would need
the myriad extensions we've found necessary for the registry use cases.
In the end I think it would be too different LDR to be a straight
evolution of the design and too different from LDP to be a straight
extension of Marmotta.
> You received this message because you are subscribed to the Google
> Groups "linked-data-api-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to linked-data-api-d...@googlegroups.com
> For more options, visit https://groups.google.com/d/optout