Issues and imports

Achim Berndzen <achim.berndzen@xml-project.com> writes:
> I am currently having the same troubles. 
> @Norm: Is it possible and would it help to raise the issues from
> https://github.com/xproc/1.0-specification/tree/xproc20/langspec/xproc20
> to xproc/1.1-specification? To my reading the two versions are almost
> identical, so the issues on A should also be issues on B.

I raised some issues (per my action to make issues from the September
minutes “pain points”). I don’t see a convenient way of moving the
issues from the 1.0-specification repository to the 1.1 repo. :-(

>>From my memory the biggest point with regard to the core specs is
> interoperability of „p:import". The two processors may know the same
> step/libraries, but use different uris to access them. I think we
> should fix this, but currently I have different ideas how to do this.
> Promise to come up with a proposal in Prague!

Would the problem be solved if we created a document, say,

  http://exproc.org/current/library.xpl

That contained the declarations for all the EXProc steps? Then
pipeline authors could import that and all implementations would get
the same declarations?

Implementations could go further and say that the /current/ URI is
magic. An implementation, when it encounters that URI, can simply take
as read that the current EXProc steps that it understands are
declared. It wouldn’t have to hit the network at all.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh
Lead Engineer
MarkLogic Corporation
Phone: +1 512 761 6676
www.marklogic.com