Eric, I wonder if you are doing something similar to what I am doing.

I have a bunch of databases found in directories, and I currently use paths that look a lot like my directories. 

declare variable $gnt:Nestle1904.tei := doc("macula/GNT/Nestle1904/tei/nestle1904.xml");
declare variable $gnt:Nestle1904.morph := doc("macula/GNT/Nestle1904/morph/Nestle1904.xml");
declare variable $gnt:Nestle1904.lowfat := doc("macula/GNT/Nestle1904/lowfat/nestle1904lowfat.xml");

If I were writing a function  that opened databases in a particular directory, I might pass the "current directory" to that function.  I suspect that's an application-domain concept, not something that BaseX should model for your application.  After all, someone else might have a rather different notion of a working directory for their application.  And "working directory" at the database level would add state in a way that would be actively unhelpful for stateless APIs.

Jonathan



On Thu, Mar 3, 2022 at 10:39 AM Christian Grün <christian.gruen@gmail.com> wrote:
Hi Eric,

There had been the suggestion that our documentation will provide you
more information on how BaseX works. After you have invested more time
on the status quo, we might be able to get some progress on this
discussion.

Best,
Christian


On Thu, Mar 3, 2022 at 4:31 PM Eric Levy <contact@ericlevy.name> wrote:
>
> Hello. I never had a chance to gain a full understanding of the
> direction of this discussion. Had there been any suggestion that some
> feature enhancement might be considered? I felt the suggestion may have
> been given, but it was never resolved.
>
>
> On Fri, 2022-02-25 at 02:37 -0500, Eric Levy wrote:
> > > > The base case for an embedded database has no user model, and
> > > > supports
> > > > creation of new databases only through the target path. However,
> > > > such
> > > > differences might press the limits of a benign request.
> > > >
> > > > If a target path is needed beyond the database itself, then it
> > > > might be
> > > > passed on the command line. Alternatively, a special directory
> > > > layout
> > > > might be considered […]
> > >
> > > In both cases, we’d rebuild the existing solution step by step. And
> > > if
> > > no such path is specified by the user, we’d need to ensure for all
> > > operations in the system that nothing unexpected happens.
> >
> > Sorry, I don't understand the meaning of the comment.
> >
> >
> > > > Yes, but it doesn't mean I understand quite yet how all the parts
> > > > fit
> > > > together. Does it seem I missed or misunderstood something?
> > >
> > > I guess so. What other parts of our documentation have you read so
> > > far
> > > to get a more comprehensive picture?
> >
> > If you want to suggest a reference that is relevant, I would review
> > it,
> > if I have not done so yet. I don't wish to compile a list of
> > documents
> > or sections I have already reviewed.
> >
>