Hi Tim,
1) Sounds good to me.
2) I do think we want core as lean as possible, so my vote would be for a
separate project/module, similar to what was done with tika-xmp. Perhaps
something like tika-serialization-json to indicate other formats may follow in
the same precedence?
3) Similar to a
Tim
-Original Message-
From: Ray Gauss II [mailto:ray.ga...@alfresco.com]
Sent: Wednesday, May 28, 2014 3:07 PM
To: dev@tika.apache.org; Allison, Timothy B.
Subject: Re: [DISCUSS] Centralizing JSON handling of Metadata
Hi Tim,
1) Sounds good to me.
2) I do think we want core as lean as
t; Best,
>
> Tim
>
> -Original Message-
> From: Ray Gauss II [mailto:ray.ga...@alfresco.com]
> Sent: Wednesday, May 28, 2014 3:07 PM
> To: dev@tika.apache.org; Allison, Timothy B.
> Subject: Re: [DISCUSS] Centralizing JSON handling of Metadata
>
> Hi Tim,
&g
On Wed, 28 May 2014, Ray Gauss II wrote:
However, that sort of modularization is probably a broader discussion
than what we need for this particular issue, so between those two I’d
vote for tika-serialization.
Tika-CLI and Tika-Server will likely want to depend on all of the
serialisation met
