Is it necessary to have the concept of manifest combination?

[iherman]

The current document uses the concept of manifest combination. However, the algorithm is complex, and requires the definition of how to combine each manifest item. This may become very complex. Also, it goes beyond what Web manifests do and may jeopardize reusing the work elsewhere.

[rdeltour]

+1 on the questioning.

As far as I understood, the intent was to describe the situation in the most complete way, so that we're not limited in the solution. That said, I would absolutely vote for a simpler implementation approach with no combination.

[iherman]

On 5 Sep 2016, at 16:41, Romain Deltour notifications@github.com wrote:

+1 on the questioning.

As far as I understood, the intent was to describe the situation in the most complete way, so that we're not limited in the solution. That said, I would absolutely vote for a simpler implementation approach with no combination.

—

The way I propose rewriting the PWP document is:

1. the core text would use a simple approach (first come first served, so to say)
2. move the 'complex' approach (ie, with combination) into an appendix for now, referring back to the corresponding use case), and leave it there for now (essentially, I do not want to 'loose' that part yet…)

WDYT?

[rdeltour]

1. the core text would use a simple approach (first come first served, so to say) 2. move the 'complex' approach (ie, with combination) into an appendix for now, referring back to the corresponding use case), and leave it there for now (essentially, I do not want to 'loose' that part yet…)

SGTM, that would definitely make the core text easier to read.

[iherman]

Done in e8a57c9

[HadrienGardeur]

I don't think that's necessary and achievable.

[iherman]

This is a leftover, actually... we had a separate discussion around the UCR document and we already decided to shy away from this.

(It is actually achievable, just fairly complicated...)

Closing the issue.