Return-Path: X-Original-To: apmail-any23-user-archive@www.apache.org Delivered-To: apmail-any23-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 023E8DA5D for ; Mon, 18 Feb 2013 21:59:11 +0000 (UTC) Received: (qmail 60010 invoked by uid 500); 18 Feb 2013 21:59:10 -0000 Delivered-To: apmail-any23-user-archive@any23.apache.org Received: (qmail 59968 invoked by uid 500); 18 Feb 2013 21:59:10 -0000 Mailing-List: contact user-help@any23.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@any23.apache.org Delivered-To: mailing list user@any23.apache.org Received: (qmail 59958 invoked by uid 99); 18 Feb 2013 21:59:10 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Feb 2013 21:59:10 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lewis.mcgibbney@gmail.com designates 209.85.215.48 as permitted sender) Received: from [209.85.215.48] (HELO mail-la0-f48.google.com) (209.85.215.48) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Feb 2013 21:59:05 +0000 Received: by mail-la0-f48.google.com with SMTP id fq13so5855586lab.21 for ; Mon, 18 Feb 2013 13:58:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=xhTAaJ4/ZvHfHpav1eGPzvA0+cTNYy7PK5RFWQub5Ck=; b=G4GzMXnEQ/Z0sU/ghdhbt2orj5ZWKq8ffhsU2ph6Uiovve9Yiev18dt37wbR+/ljLA v+Ab/OR3wuMjAiaAVgSmJFf5TwdaTjP3lWf6Vlmb8XWKHw0D+m90grbCup7MPTVg3aFk QJaM2owDwtCzNjj8Zut+1qIS+HWRcfUUzw7OethqrmqA9SLb4CBzEu7iHr1fuig+qPyw TZlELP2r2Fg7/lme2OIyzeawU06FD5YCT/o+OVFyY7k49CTzhq60G7kbk7Ejv/owXLUH wPJjlF1mSGzgr4Pikl71bquEyfSgyXODsXxm/GFecGj5zKI6U2BzYskUpOF3KJkfO5vj 3FPw== MIME-Version: 1.0 X-Received: by 10.152.130.131 with SMTP id oe3mr12040019lab.1.1361224723275; Mon, 18 Feb 2013 13:58:43 -0800 (PST) Received: by 10.112.81.8 with HTTP; Mon, 18 Feb 2013 13:58:43 -0800 (PST) Date: Mon, 18 Feb 2013 13:58:43 -0800 Message-ID: Subject: Re: RDF Format detection From: Lewis John Mcgibbney To: user@any23.apache.org Content-Type: multipart/alternative; boundary=f46d04095bf7171fb904d606d41c X-Virus-Checked: Checked by ClamAV on apache.org --f46d04095bf7171fb904d606d41c Content-Type: text/plain; charset=ISO-8859-1 Hi Jerry, On Sun, Feb 17, 2013 at 11:48 AM, wrote: > > > I am having weird RDF format detection issue. When I use the API, it > detects rdf+n3 where as when I use http://any23.org/ it says turtle. > > > I am actually trying to detect the Turtle format, so the website is * > correct*. Where as the API detects *incorrectly*. I tried excluding the > Tika v0.5 and adding the latest Tika v1.3 as dependency. Still the problem > exists. > So you are using 0.7.0-incubating I take it? Maybe you could try checking out trunk (which we are just about to release) and work with that. You can also pull the dependency from the Apache snapshots repository, this includes the Tika upgrade to 1.2. > > Another question, is regarding the MIME type relation. The MIME type > returned from Tika, which is the first-level of detection in Any23, does > not match the TikeMIMETypeDectector enumeration for RDF formats. Am I doing > something wrong? > I don't really understand this! {bq}...Any23, does not match the TikeMIMETypeDectector enumeration for RDF formats.{bq} Can you explain this with an example please? MIMETypeDetection should be consistent between API usage and the service, there is no doubt about this. Lewis --f46d04095bf7171fb904d606d41c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Jerry,

On Sun, Feb 17, 2013 at 11:48 A= M, <user-digest-help@any23.apache.org> wrot= e:


I am havi= ng=A0weird=A0RDF format detection issue. When I use the API, it detects rdf= +n3 where as when I use=A0http://any23.org/=A0it says turtle.
=A0

I am actually trying to detect the Turtle format, so the website is corr= ect. Where as the API detects incorrectly. I tried excluding the= Tika v0.5=A0and adding the latest Tika v1.3 as dependency. Still the probl= em exists.

So you are using 0.7.0-incubating I take it? Maybe yo= u could try=20 checking out trunk (which we are just about to release) and work with=20 that. You can also pull the dependency from the Apache snapshots=20 repository, this includes the Tika upgrade to 1.2.
=A0

Another question, is regarding the MIME type relation. The MIME type return= ed from Tika, which is the first-level of detection in Any23, does not matc= h the TikeMIMETypeDectector enumeration for RDF formats. Am I doing somethi= ng wrong?

I don't really understand this! {bq}...Any23, does not match the = TikeMIMETypeDectector enumeration for RDF formats.{bq}
Can you explain t= his with an example please?
MIMETypeDetection should be consistent betwe= en API usage and the service, there is no doubt about this.
Lewis
--f46d04095bf7171fb904d606d41c--