Return-Path: Delivered-To: apmail-incubator-jena-dev-archive@minotaur.apache.org Received: (qmail 78136 invoked from network); 22 Jan 2011 13:22:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 22 Jan 2011 13:22:05 -0000 Received: (qmail 14358 invoked by uid 500); 22 Jan 2011 13:22:05 -0000 Delivered-To: apmail-incubator-jena-dev-archive@incubator.apache.org Received: (qmail 14322 invoked by uid 500); 22 Jan 2011 13:22:03 -0000 Mailing-List: contact jena-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jena-dev@incubator.apache.org Delivered-To: mailing list jena-dev@incubator.apache.org Delivered-To: moderator for jena-dev@incubator.apache.org Received: (qmail 62059 invoked by uid 99); 22 Jan 2011 12:34:07 -0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Message-ID: <23524260.124711295699623282.JavaMail.jira@thor> Date: Sat, 22 Jan 2011 07:33:43 -0500 (EST) From: =?utf-8?Q?Reto_Bachmann-Gm=C3=BCr_=28JIRA=29?= To: jena-dev@incubator.apache.org Subject: [jira] Commented: (JENA-31) Add possibility to connect serializers to prefix service In-Reply-To: <15633126.83601295538943227.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/JENA-31?page=3Dcom.atlassian.ji= ra.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1298509= 8#action_12985098 ]=20 Reto Bachmann-Gm=C3=BCr commented on JENA-31: ---------------------------------------- "The application can analysis the data, make choices of prefixes, set the p= refix map appropriately and call the writer. " I see that this is a possible work-around, howverrequiring the application = to iterate over the data and determine the prefixed part for every uri seem= s highly inefficient. "Pretty printing RDF/XML requires all the prefixes to be available at the s= tart. * Then the pretty-printer has to look at the data and find-out which prefixes= are needed, as uris in predicated position need a prefix this step is nece= ssary even if all prefixes in the map would be put in the prefix-mapping in= the XML header. For huge turtle seralization it might be ausefull setting, to limit the num= ber of triples that are evaluated as possible prefixes, once this number ha= s been reach subsequent triples never cause a yet unused prefix to be added= . > Add possibility to connect serializers to prefix service > -------------------------------------------------------- > > Key: JENA-31 > URL: https://issues.apache.org/jira/browse/JENA-31 > Project: Jena > Issue Type: Improvement > Components: Jena > Reporter: Reto Bachmann-Gm=C3=BCr > > Currently the serializers want to access the whole set of available prefi= mappings, instead they shold only ask for a prefix suggestion for uris actu= ally in the model, that way it is possible to connect services which can su= ggest prefixes for a huge number of uris which is not reasonably feasible n= ow. --=20 This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.