Return-Path: Delivered-To: apmail-incubator-clerezza-dev-archive@minotaur.apache.org Received: (qmail 4842 invoked from network); 3 Nov 2010 15:24:53 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 3 Nov 2010 15:24:53 -0000 Received: (qmail 74326 invoked by uid 500); 3 Nov 2010 15:25:24 -0000 Delivered-To: apmail-incubator-clerezza-dev-archive@incubator.apache.org Received: (qmail 73323 invoked by uid 500); 3 Nov 2010 15:25:23 -0000 Mailing-List: contact clerezza-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: clerezza-dev@incubator.apache.org Delivered-To: mailing list clerezza-dev@incubator.apache.org Received: (qmail 73315 invoked by uid 99); 3 Nov 2010 15:25:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Nov 2010 15:25:22 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of christ.fabian@googlemail.com designates 209.85.161.47 as permitted sender) Received: from [209.85.161.47] (HELO mail-fx0-f47.google.com) (209.85.161.47) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Nov 2010 15:25:17 +0000 Received: by fxm3 with SMTP id 3so537722fxm.6 for ; Wed, 03 Nov 2010 08:24:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:content-type :date:message-id:mime-version:x-mailer:content-transfer-encoding; bh=H+U7laIP6T5r7nF1itTu9hj71NhC4k/BW2bgNeGaeD0=; b=nAiMgVOHMbfok+cuIDThjiAP0ZHfrTO23DGIANSZF0XPr3Nisrx9w0pulHmKU/r8qE p3cd/R1a25mgSSiGC6WwVDacBAc6gTn3/HzSZmTMKxbpTPQsnUXHzHw/mBWUn+KGrW+X LUbakUjE6nvIAkbp36igyY2pP0XZaWWM+PwqM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=subject:from:to:content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; b=SCuWHdaqOfkwNZZVu1NgKJ85QT7uP6SjkdrjO2fcJJB6f1b2hd2onl5/bO0jzQqNuZ xp8vmidQ6tfUROrOG2SQYIYHmfI5J3N2XiBX23syevCHO+t/QmsvzyUqYqmN30TV4Djd tZFSXZE+nfA/qpgilY7JJMb2UBHsHek091b7w= Received: by 10.223.86.197 with SMTP id t5mr9259286fal.38.1288797895463; Wed, 03 Nov 2010 08:24:55 -0700 (PDT) Received: from [10.0.2.15] (pc-eng10.cs.uni-paderborn.de [131.234.21.108]) by mx.google.com with ESMTPS id d20sm3737911fav.38.2010.11.03.08.24.52 (version=SSLv3 cipher=RC4-MD5); Wed, 03 Nov 2010 08:24:53 -0700 (PDT) Subject: Namespace handling in Clerezza and JSON-LD serialization From: Fabian Christ To: Clerezza Dev Mailingliste , IKS FISE Mailinglist Content-Type: text/plain; charset="UTF-8" Date: Wed, 03 Nov 2010 16:24:58 +0100 Message-ID: <1288797898.5000.27.camel@pc-eng10-ubuntu> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 7bit Hi, as one part of the EU funded project "Interactive Knowledge Stack" IKS [1] and by this part of the Apache FOO incubation proposal we currently use Clerezza as one underlying framework. Currently, I'm implementing a JSON-LD [2] serializer as part of the FISE component [3]. This serializer implements the Clerezza SerializingProvider interface. So this serializer is basically a Clerezza serializer. The JSON-LD format supports namespaces, so we need some way to manage known namespaces and their prefixes within the whole system. An example of a JSON-LD output looks like this: { "#": { "dbpedia": "http:\/\/dbpedia.org\/ontology\/", "dcterms": "http:\/\/purl.org\/dc\/terms", "fise": "http:\/\/fise.iks-project.eu\/ontology\/", "xmlns": "http:\/\/www.w3.org\/2001\/XMLSchema#" }, "@": "", "a": [ "", "" ], "dcterms:\/created": "\"2010-10-27\"^^", "dcterms:\/creator": "urn:iks-project:fise:test:dummyEngine", "dcterms:\/type": "dbpedia:Person", "fise:end": "\"20\"^^", "fise:selected-text": "\"Patrick Marshall\"^^", "fise:selection-context": "\"Dr. Patrick ..\"^^", "fise:start": "\"4\"^^" } This brings us to two questions: 1) How does Clerezza handle the namespaces and prefixes? Is there some centralized service that FOO could use? If there is no namespace handling yet, what are the Clerezza plans here? Maybe we could find a solution that is useful for both projects. 2) Is the Clerezza community interested in the JSON-LD serializer? We would be happy to commit the code to Clerezza instead of our own code base and support Clerezza. Best regards, - Fabian [1] http://www.iks-project.eu [2] http://json-ld.org/spec/ [3] http://code.google.com/p/iks-project/source/browse/sandbox/fise/trunk/jersey/src/main/java/eu/iksproject/fise/jersey/writers/JsonLdSerializerProvider.java