I'm not able to sponsor anything now. My biggest commercial project is coming to an end. I'm working on smaller projects, which means smaller budgets. I'm also working on 2 volunteer gigs, which means no budget at all.

When I hook another big project, that might change.

By the way, I'm using BaseX to transform content in 303 languages and dialects and they all work. I'm impressed. Vive unicode!

I'm using BaseX for as many projects as I can. I really love the product. My shopping list for future feature would be:

Metadata (mostly to handle work processes: status, version, work assignment)
The ability to search for files based on values that are actually provided in the xml schema without having to resolve them in content
I currently keep the authors' files and the files used for transformations in 2 separate databases. That's a lot of duplication and keeping both databases in synch is a headache. Transformations are applied to values provided by the schema, so there is no way around this. I can't have @class in the authoring environment, but I require them for transformations and publishing.
Indexed tokens for better performance, and even when the tokens are values set in the schema (see previous point).
The ability to catch changes from webDAV save operations in xquery.
For example, if I could catch operations performed on the database, I could run a process that adds the schema @class values and synch up the publishing/transformation database with the authors' database with each change. I could also delete files in both databases at once. That would limit the headache from the 2nd point. Currently each webDAV operation leaves me with out of synch databases. And moving away from webDAV isn't possible just yet.

I know that as a non-sponsor, I can't push these through right now, but I thought it'd be useful to explain where I'm coming from. Most of my projects use DITA in an authoring environment where I can't just resolve the schema items at import, so these are recurring issues for me. Maybe at some point I can round up enough DITA users around BaseX to get someone to sponsor the shopping list.

Have a great 2016!

France

On Thu, Dec 31, 2015 at 7:20 AM, Christian Grün <christian.gruen@gmail.com> wrote:

Dear France,

Right now, I cannot give you a fixed timeframe. I guess the
introduction of metadata properties may depend on the availability of
sponsors. However, we could possibly take advantage of its
introduction in one of our own commercial projects as well, so this
could be the reason for tackling it in spring or summer 2016 (but I
cannot promise anything ;).

Christian
________________________________

On Thu, Dec 31, 2015 at 5:28 AM, France Baril
<france.baril@architextus.com> wrote:

> Do you have a timeframe for the metadata properties? I'm very interested
> :-).
>
> On Wed, Dec 23, 2015 at 9:19 AM, Christian Grün <christian.gruen@gmail.com>
> wrote:
>>
>> Hi Laurent,
>>
>> > I discovered BaseX recently and I find it really powerfull.
>> > Unfortunately, I
>> > read that versioning was not supported out of the box in 2014 [1]. Is it
>> > still the case ? Is there no simple workaround ?
>>
>> BaseX does not come with an out-of-the-box solution for versioning XML
>> documents, but there are many ways to realize this via XQuery or the
>> existing commands. You could e.g. attach timestamps in the database
>> file paths or update information in an additional XML meta file with
>> each request. We have also started defining document metadata
>> properties [1], but this is still work in progress.
>>
>> > A simple way to achieve such a behaviour would be to be able to index a
>> > XML
>> > resource in BaseX with some additional meta information such as an ID
>> > and a
>> > timestamp, and then offer the possibility to use these meta information
>> > in
>> > an XQuery to filter resources.
>> >
>> > Is it possible with BaseX 8.3 ?
>>
>> This is absolutely possible. I don’t know how much time you have
>> already spent with XQuery, but could check out our Wiki articles on
>> XQuery Update [2] and the Database Module [3].
>>
>> Hope this helps,
>> Christian
>>
>> [1] https://github.com/BaseXdb/basex/issues/988
>> [2] http://docs.basex.org/wiki/XQuery_Update
>> [3] http://docs.basex.org/wiki/Database_Module
>>
>>
>>
>> On Wed, Dec 23, 2015 at 2:18 PM, Laurent Pellegrino
>> <laurent.pellegrino@activeeon.com> wrote:
>> > Hello all,
>> >
>> > I discovered BaseX recently and I find it really powerfull.
>> > Unfortunately, I
>> > read that versioning was not supported out of the box in 2014 [1]. Is it
>> > still the case ? Is there no simple workaround ?
>> >
>> > My usecase is the following. I have thousands of XML files which are
>> > indexed
>> > using BaseX in a specific database, lets say "mydb". At some point of
>> > time,
>> > a user may want to add a new XML file which is a slightly modified
>> > version
>> > of one already indexed by BaseX.
>> >
>> > I would like to be able to:
>> >
>> > - store this new XML resource in "mydb" database without loosing the
>> > XML
>> > from which it is issued
>> > - to retrieve the latest version or a previous one.
>> > - filter resources based on the latest version
>> >
>> > A simple way to achieve such a behaviour would be to be able to index a
>> > XML
>> > resource in BaseX with some additional meta information such as an ID
>> > and a
>> > timestamp, and then offer the possibility to use these meta information
>> > in
>> > an XQuery to filter resources.
>> >
>> > Is it possible with BaseX 8.3 ?
>> >
>> > I am looking for a solution that does not a require another database.
>> >
>> > [1]
>> >
>> > https://mailman.uni-konstanz.de/pipermail/basex-talk/2014-March/006535.html
>> >
>> > Kind Regards,
>> >
>> > Laurent Pellegrino
>> >
>
>
>
>
> --
> France Baril
> Architecte documentaire / Documentation architect
> france.baril@architextus.com

France Baril
Architecte documentaire / Documentation architect
france.baril@architextus.com