Allow multiple archives on `create` for p:archive?

[ndw]

According to test ab-p-archive-067, it's an error to provide more than one archive file to p:archive when the create command is used.

I decided to allow create to combine several input archives rather than have to invent a new merge or combine command.

What's the motivation for the restriction on create?

[xml-project]

In the step description I read:

Unless otherwise specified, exactly zero or one ZIP archive can appear on the archive port for the commands described below. If no archive appears, a new archive will be created.

In the specification of the command, only 'delete' has an exception from this rule: There must be exactly one document. So one can read the specification to motivate the error.

On the other hand, on port "archive", I read:

The archive port is used to provide the step with existing archive(s) for operations like update, freshen or merge. Handling of ZIP files supports modifying archives appearing on the archive port (Section 2.3.2, “Handling of ZIP archives”). The list of archive formats that can be modified by p:archive is implementation-defined. For instance an implementation that supports archive merging may accept more than one document on the archive port.

The last sentence seems to say, that it is implementation defined how many documents are allowed on this port. So the error code XC0080 seems to be never reasonable in the test suite as an implementation might do whatever.

I would not object to removing the test. As there are more test, do you thing we should remove them too?

[ndw]

I decided that the limits made sense for update, freshen , and delete. Certainly for delete, exactly one is the right answer. I suppose one could imagine allowing more than one for update and freshen but equally, one could argue that it's a stretch of the semantics.

Allowing create to combine several archives gives a user a way to merge-and-update or merge-and-freshen if they want, in two steps.

If you allow more than one, there's an open question about what to do about duplicates. I made "error" the default and provided a custom parameter to specify keep-first or keep-last behavior.

[xml-project]

@ndw I agree that your decisions make sense. However the spec seems to allow other decisions (e.g. delete from multiple archives in one p:archive). I think there should be no tests forcing OUR decisions, so I would suggest to delete all tests forcing XC0080 to be raised.

[ndw]

Proposal: remove "For instance an implementation that supports archive merging may accept more than one document on the archive port.", allow create to accept more than 1 archive.