From susan84@example.org Sat Aug 01 01:46:54 2009 Return-Path: <susan84@example.org> Delivered-To: susan84@example.org Received: (qmail 16878 invoked from network); 1 Aug 2009 01:46:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Aug 2009 01:46:54 -0000 Received: (qmail 10910 invoked by uid 500); 1 Aug 2009 01:20:18 -0000 Delivered-To: susan84@example.org Received: (qmail 10832 invoked by uid 500); 1 Aug 2009 01:20:18 -0000 Mailing-List: contact susan84@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:susan84@example.org> List-Unsubscribe: <mailto:susan84@example.org> List-Post: <mailto:susan84@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: susan84@example.org Delivered-To: mailing list susan84@example.org Received: (qmail 10824 invoked by uid 99); 1 Aug 2009 01:20:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Aug 2009 01:20:18 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of susan84@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mail-yx0-f190.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Aug 2009 01:20:10 +0000 Received: by yxe28 with SMTP id 28so4429392yxe.10 for <susan84@example.org>; Fri, 31 Jul 2009 18:19:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type :content-transfer-encoding; bh=o7Th3edjgx8CxsBgK27vHhEuG3eDRemZz8dFjRNKzAI=; b=i/WHJBEEu87cBcsONAQak6Ptwbu/3aLjAe404JKExutYegFbcX6t2OjegSNf0kwHKz pOiBG5vDR2fK9O7ekw0CGr/LiO0zbrojYVH7yTJOHiGKnf/+MJxuB3aO0zjO9A11M43E jOCx5eVshxAxJK686fFbemBxqgZ/bRgvnKQbI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=FLcYm9WG/jYbrqd0zEmPRKnVRsHHOyH7E6uFSu+jeZ8WnS0BVj97xjYA4A1GnY1JI+ fiPf4dMZMnVzhtnZCDikNtLrYDMrk7QDIDbQAhCFVvi5L+v9m4J17ADLs1nqpdG8mSHp l40whTeALnFEHLG5K6Hsqom/jxywKK0Bzxo8U= MIME-Version: 1.0 Received: by 83.161.120.155 with SMTP id x14mr3218115ank.78.1249089589210; Fri, 31 Jul 2009 18:19:49 -0700 (PDT) In-Reply-To: <susan84@example.org> References: <susan84@example.org> <susan84@example.org> From: Mukul Gandhi <susan84@example.org> Date: Sat, 1 Aug 2009 06:49:29 +0530 Message-ID: <susan84@example.org> Subject: Re: XML Schema 1.1 inheritable attributes, implementation To: susan84@example.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi Michael, It's my pleasure, to work on this. On Fri, Jul 31, 2009 at 11:01 PM, Michael Glavassevich<susan84@example.org> wrote: > Hi Mukul, > > Sounds good. Thanks for taking a susan84@example.org. > > Michael Glavassevich > XML Parser Development > IBM Toronto Lab > E-mail: susan84@example.org > E-mail: susan84@example.org -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: susan84@example.org For additional commands, e-mail: susan84@example.org From susan84@example.org Sat Aug 01 04:02:34 2009 Return-Path: <susan84@example.org> Delivered-To: susan84@example.org Received: (qmail 51012 invoked from network); 1 Aug 2009 04:02:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Aug 2009 04:02:34 -0000 Received: (qmail 79433 invoked by uid 500); 1 Aug 2009 04:02:38 -0000 Delivered-To: susan84@example.org Received: (qmail 79326 invoked by uid 500); 1 Aug 2009 04:02:37 -0000 Mailing-List: contact susan84@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:susan84@example.org> List-Unsubscribe: <mailto:susan84@example.org> List-Post: <mailto:susan84@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: susan84@example.org Delivered-To: mailing list susan84@example.org Received: (qmail 79309 invoked by uid 99); 1 Aug 2009 04:02:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Aug 2009 04:02:37 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Aug 2009 04:02:35 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 00001234C1EF for <susan84@example.org>; Fri, 31 Jul 2009 21:02:14 -0700 (PDT) Message-ID: <1073858006.1249099334999.JavaMail.jira@brutus> Date: Fri, 31 Jul 2009 21:02:14 -0700 (PDT) From: "Michael Glavassevich (JIRA)" <susan84@example.org> To: susan84@example.org Subject: [jira] Updated: (XERCESJ-1388) RegEx matching: when computing backreferences, "\dd" must match group "dd" if group exists In-Reply-To: <1892977589.1249011014838.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/XERCESJ-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-1388: ------------------------------------------ Issue Type: New Feature (was: Bug) > RegEx matching: when computing backreferences, "\dd" must match group "dd" if group exists > ------------------------------------------------------------------------------------------ > > Key: XERCESJ-1388 > URL: https://issues.apache.org/jira/browse/XERCESJ-1388 > Project: Xerces2-J > Issue Type: New Feature > Components: Other > Affects Versions: 2.9.1 > Reporter: Radu Preotiuc-Pietro > > When dealing with back-references to groups >= 10, "\" followed by more than one digit must match the largest number, smaller than the total number of groups, that can be constructed by dropping digits from the right. > So, for instance, \11 must match the 11th capturing group of the expression "^ (#)(a)(b)(c)(d)(e)(f)(g)(h)(i)(j)\11", because there are 11 capturing groups; it must not match the first capturing group ant then the digit "1". -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: susan84@example.org For additional commands, e-mail: susan84@example.org From susan84@example.org Sat Aug 01 04:02:35 2009 Return-Path: <susan84@example.org> Delivered-To: susan84@example.org Received: (qmail 51011 invoked from network); 1 Aug 2009 04:02:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Aug 2009 04:02:34 -0000 Received: (qmail 79417 invoked by uid 500); 1 Aug 2009 04:02:38 -0000 Delivered-To: susan84@example.org Received: (qmail 79325 invoked by uid 500); 1 Aug 2009 04:02:37 -0000 Mailing-List: contact susan84@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:susan84@example.org> List-Unsubscribe: <mailto:susan84@example.org> List-Post: <mailto:susan84@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: susan84@example.org Delivered-To: mailing list susan84@example.org Received: (qmail 79312 invoked by uid 99); 1 Aug 2009 04:02:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Aug 2009 04:02:37 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Aug 2009 04:02:35 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id EFA30234C053 for <susan84@example.org>; Fri, 31 Jul 2009 21:02:14 -0700 (PDT) Message-ID: <1433001007.1249099334980.JavaMail.jira@brutus> Date: Fri, 31 Jul 2009 21:02:14 -0700 (PDT) From: "Michael Glavassevich (JIRA)" <susan84@example.org> To: susan84@example.org Subject: [jira] Commented: (XERCESJ-1388) RegEx matching: when computing backreferences, "\dd" must match group "dd" if group exists In-Reply-To: <1892977589.1249011014838.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/XERCESJ-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737826#action_12737826 ] Michael Glavassevich commented on XERCESJ-1388: ----------------------------------------------- I could guess but I'd probably be wrong. When the next release might be is still TBD. > RegEx matching: when computing backreferences, "\dd" must match group "dd" if group exists > ------------------------------------------------------------------------------------------ > > Key: XERCESJ-1388 > URL: https://issues.apache.org/jira/browse/XERCESJ-1388 > Project: Xerces2-J > Issue Type: Bug > Components: Other > Affects Versions: 2.9.1 > Reporter: Radu Preotiuc-Pietro > > When dealing with back-references to groups >= 10, "\" followed by more than one digit must match the largest number, smaller than the total number of groups, that can be constructed by dropping digits from the right. > So, for instance, \11 must match the 11th capturing group of the expression "^ (#)(a)(b)(c)(d)(e)(f)(g)(h)(i)(j)\11", because there are 11 capturing groups; it must not match the first capturing group ant then the digit "1". -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: susan84@example.org For additional commands, e-mail: susan84@example.org From susan84@example.org Sat Aug 01 04:04:35 2009 Return-Path: <susan84@example.org> Delivered-To: susan84@example.org Received: (qmail 51432 invoked from network); 1 Aug 2009 04:04:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Aug 2009 04:04:35 -0000 Received: (qmail 80899 invoked by uid 500); 1 Aug 2009 04:04:39 -0000 Delivered-To: susan84@example.org Received: (qmail 80818 invoked by uid 500); 1 Aug 2009 04:04:39 -0000 Mailing-List: contact susan84@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:susan84@example.org> List-Unsubscribe: <mailto:susan84@example.org> List-Post: <mailto:susan84@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: susan84@example.org Delivered-To: mailing list susan84@example.org Received: (qmail 80798 invoked by uid 99); 1 Aug 2009 04:04:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Aug 2009 04:04:39 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Aug 2009 04:04:35 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id E1566234C053 for <susan84@example.org>; Fri, 31 Jul 2009 21:04:14 -0700 (PDT) Message-ID: <1729879000.1249099454922.JavaMail.jira@brutus> Date: Fri, 31 Jul 2009 21:04:14 -0700 (PDT) From: "Michael Glavassevich (JIRA)" <susan84@example.org> To: susan84@example.org Subject: [jira] Resolved: (XERCESJ-1388) RegEx matching: when computing backreferences, "\dd" must match group "dd" if group exists In-Reply-To: <1892977589.1249011014838.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/XERCESJ-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich resolved XERCESJ-1388. ------------------------------------------- Resolution: Fixed Khaled has already implemented this enhancement. See SVN rev 799450: http://svn.apache.org/viewvc?view=rev&revision=799450. > RegEx matching: when computing backreferences, "\dd" must match group "dd" if group exists > ------------------------------------------------------------------------------------------ > > Key: XERCESJ-1388 > URL: https://issues.apache.org/jira/browse/XERCESJ-1388 > Project: Xerces2-J > Issue Type: New Feature > Components: Other > Affects Versions: 2.9.1 > Reporter: Radu Preotiuc-Pietro > > When dealing with back-references to groups >= 10, "\" followed by more than one digit must match the largest number, smaller than the total number of groups, that can be constructed by dropping digits from the right. > So, for instance, \11 must match the 11th capturing group of the expression "^ (#)(a)(b)(c)(d)(e)(f)(g)(h)(i)(j)\11", because there are 11 capturing groups; it must not match the first capturing group ant then the digit "1". -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: susan84@example.org For additional commands, e-mail: susan84@example.org From susan84@example.org Sat Aug 01 04:08:35 2009 Return-Path: <susan84@example.org> Delivered-To: susan84@example.org Received: (qmail 51944 invoked from network); 1 Aug 2009 04:08:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Aug 2009 04:08:35 -0000 Received: (qmail 82133 invoked by uid 500); 1 Aug 2009 04:08:39 -0000 Delivered-To: susan84@example.org Received: (qmail 82075 invoked by uid 500); 1 Aug 2009 04:08:39 -0000 Mailing-List: contact susan84@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:susan84@example.org> List-Unsubscribe: <mailto:susan84@example.org> List-Post: <mailto:susan84@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: susan84@example.org Delivered-To: mailing list susan84@example.org Received: (qmail 82065 invoked by uid 99); 1 Aug 2009 04:08:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Aug 2009 04:08:39 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Aug 2009 04:08:35 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id E002C234C1EB for <susan84@example.org>; Fri, 31 Jul 2009 21:08:14 -0700 (PDT) Message-ID: <2002117558.1249099694916.JavaMail.jira@brutus> Date: Fri, 31 Jul 2009 21:08:14 -0700 (PDT) From: "Michael Glavassevich (JIRA)" <susan84@example.org> To: susan84@example.org Subject: [jira] Assigned: (XERCESJ-1388) RegEx matching: when computing backreferences, "\dd" must match group "dd" if group exists In-Reply-To: <1892977589.1249011014838.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/XERCESJ-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich reassigned XERCESJ-1388: --------------------------------------------- Assignee: Khaled Noaman > RegEx matching: when computing backreferences, "\dd" must match group "dd" if group exists > ------------------------------------------------------------------------------------------ > > Key: XERCESJ-1388 > URL: https://issues.apache.org/jira/browse/XERCESJ-1388 > Project: Xerces2-J > Issue Type: New Feature > Components: Other > Affects Versions: 2.9.1 > Reporter: Radu Preotiuc-Pietro > Assignee: Khaled Noaman > > When dealing with back-references to groups >= 10, "\" followed by more than one digit must match the largest number, smaller than the total number of groups, that can be constructed by dropping digits from the right. > So, for instance, \11 must match the 11th capturing group of the expression "^ (#)(a)(b)(c)(d)(e)(f)(g)(h)(i)(j)\11", because there are 11 capturing groups; it must not match the first capturing group ant then the digit "1". -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: susan84@example.org For additional commands, e-mail: susan84@example.org From susan84@example.org Sat Aug 01 13:05:59 2009 Return-Path: <susan84@example.org> Delivered-To: susan84@example.org Received: (qmail 69067 invoked from network); 1 Aug 2009 13:05:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Aug 2009 13:05:59 -0000 Received: (qmail 82771 invoked by uid 500); 1 Aug 2009 13:06:02 -0000 Delivered-To: susan84@example.org Received: (qmail 82718 invoked by uid 500); 1 Aug 2009 13:06:02 -0000 Mailing-List: contact susan84@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:susan84@example.org> List-Unsubscribe: <mailto:susan84@example.org> List-Post: <mailto:susan84@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: susan84@example.org Delivered-To: mailing list susan84@example.org Received: (qmail 82710 invoked by uid 99); 1 Aug 2009 13:06:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Aug 2009 13:06:02 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of susan84@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mail-pz0-f190.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Aug 2009 13:05:54 +0000 Received: by pzk28 with SMTP id 28so1904337pzk.11 for <susan84@example.org>; Sat, 01 Aug 2009 06:05:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=Ga6okSjEF3H1VfpSs0i352OlLa2uKrJN+VtszP4vwLs=; b=SO7g/3HSs/THiKnCpVDbgOZEItl3KKSxrIRI78y6W/YVjoLRjHV5awTnjm35ZHF5dX P0z86d0anA37VrD3MhOFtiX0seDHdVbEXO2tpYY34taX6HhbJJ4Fey2Fn3yjR9ujdP0m hz1Jpql0jdYt1f4u63BwqClySaTl07EvIVHRQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=smuCK1JQvKsYraJpeTpK/F93UfeJ/OeXCwq5JdaxsOb/GsXes8vatE+kGV+WdqiX5M 7IN/01VsYA6dxHOePJSrwDp69AD0W3lkYsXEWOxIOHc7aUhuCi//LDLlqPefFWQL8VFD fA10EipTO/IXfaerZN13uQouBWmyqz0Ec8zic= MIME-Version: 1.0 Received: by 83.161.120.155 with SMTP id b2mr278646wff.276.1249131934267; Sat, 01 Aug 2009 06:05:34 -0700 (PDT) In-Reply-To: <susan84@example.org> References: <susan84@example.org> <susan84@example.org> Date: Sat, 1 Aug 2009 23:05:34 +1000 Message-ID: <susan84@example.org> Subject: Re: GSoC Update From: Richard Kelly <susan84@example.org> To: susan84@example.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi again, First of all, apologies for the late update, my new semester has started here and it's been quite busy. However I've still been working away on my code and I think the functionality is mostly complete at this stage, but I still have some bugs to fix and a lot of testing to do. I have a few more questions: I've added some code to normalize() functions in various Node subclasses. Do I need to generate a new serialization version for these classes (I didn't change any data members)? If so, how do i do that? Another question I had that I want to find out the name of the element currently being processed. Is there a generic way to get this information from within the pipeline or do I need to keep track of the current element within my component? Thanks, Richard --------------------------------------------------------------------- To unsubscribe, e-mail: susan84@example.org For additional commands, e-mail: susan84@example.org From susan84@example.org Sat Aug 01 16:13:35 2009 Return-Path: <susan84@example.org> Delivered-To: susan84@example.org Received: (qmail 27370 invoked from network); 1 Aug 2009 16:13:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Aug 2009 16:13:35 -0000 Received: (qmail 74924 invoked by uid 500); 1 Aug 2009 16:13:39 -0000 Delivered-To: susan84@example.org Received: (qmail 74848 invoked by uid 500); 1 Aug 2009 16:13:38 -0000 Mailing-List: contact susan84@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:susan84@example.org> List-Unsubscribe: <mailto:susan84@example.org> List-Post: <mailto:susan84@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: susan84@example.org Delivered-To: mailing list susan84@example.org Received: (qmail 74840 invoked by uid 99); 1 Aug 2009 16:13:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Aug 2009 16:13:38 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of susan84@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO qw-out-1920.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Aug 2009 16:13:28 +0000 Received: by qw-out-1920.google.com with SMTP id 5so1336984qwf.44 for <susan84@example.org>; Sat, 01 Aug 2009 09:13:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:references:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:x-mailer :mime-version:subject:date:cc; bh=2TfdZPPAkrGm0xoKL86L0g6wEf5XdLMVIjp0sEB0FIc=; b=bR+pN0a37NBONQlaJFANs6YgwFA5x3K9MH6OxM7rzrhIJr+1TURHMS41io4E3p77l4 QFSF5HXlpV1pgd8cyzrHcDBTx/wKIxFnp/KJO0Zxus8yNLEKRmrlpDqWVJ2/qzzLhK7N KTF9P3dkzb6iWbN0K9tAWgyzV9xAMw1WRZrwk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:x-mailer:mime-version:subject:date:cc; b=spNjYgzsbmlHjE51MxoS+/ks6jQW0dAdl3Sd/zz/NRW7H2GXV9MZQMJWg6tjD4yczK ByySbIoULd/MlmFakVIJICQzprS2uM+RUFB/E7pFv9H7RALeblEOXpUIMJvxp1ojW5uk VtyCfVbw0SETCmSEpV1EGHYqONRyICI0IheY0= Received: by 83.161.120.155 with SMTP id q14mr3163641qaj.40.1249143187298; Sat, 01 Aug 2009 09:13:07 -0700 (PDT) Received: from ?83.161.120.155? (mobile-166-137-133-039.mycingular.net [83.161.120.155]) by mx.google.com with ESMTPS id 6sm8757697qwk.4.283.161.120.155.13.05 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 01 Aug 2009 09:13:06 -0700 (PDT) References: <susan84@example.org> <susan84@example.org> <susan84@example.org> Message-Id: <susan84@example.org> From: Nathan Beyer <susan84@example.org> To: "susan84@example.org" <susan84@example.org> In-Reply-To: <susan84@example.org> Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Mailer: iPhone Mail (7A400) Mime-Version: 1.0 (iPhone Mail 7A400) Subject: Re: GSoC Update Date: Sat, 1 Aug 2009 11:12:56 -0500 Cc: "susan84@example.org" <susan84@example.org> X-Virus-Checked: Checked by ClamAV on apache.org On Aug 1, 2009, at 8:05 AM, Richard Kelly <susan84@example.org> wrote: > Hi again, > > First of all, apologies for the late update, my new semester has > started here and it's been quite busy. > However I've still been working away on my code and I think the > functionality is mostly complete at > this stage, but I still have some bugs to fix and a lot of testing > to do. > > I have a few more questions: > > I've added some code to normalize() functions in various Node > subclasses. Do I need to generate a new > serialization version for these classes (I didn't change any data > members)? If so, how do i do that? You probably don't need to generate a new one if none of the instance variables changed, but I'd have to see the code to know for sure. However it's probably desirable to NOT change the ID and implement custom serialization to make any changes passive. -Nathan > > Another question I had that I want to find out the name of the element > currently being processed. Is there > a generic way to get this information from within the pipeline or do I > need to keep track of the current > element within my component? > > > Thanks, > Richard > > --------------------------------------------------------------------- > To unsubscribe, e-mail: susan84@example.org > For additional commands, e-mail: susan84@example.org > --------------------------------------------------------------------- To unsubscribe, e-mail: susan84@example.org For additional commands, e-mail: susan84@example.org From susan84@example.org Thu Aug 06 03:36:22 2009 Return-Path: <susan84@example.org> Delivered-To: susan84@example.org Received: (qmail 64415 invoked from network); 6 Aug 2009 03:36:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 6 Aug 2009 03:36:22 -0000 Received: (qmail 50232 invoked by uid 500); 6 Aug 2009 03:36:29 -0000 Delivered-To: susan84@example.org Received: (qmail 50175 invoked by uid 500); 6 Aug 2009 03:36:29 -0000 Mailing-List: contact susan84@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:susan84@example.org> List-Unsubscribe: <mailto:susan84@example.org> List-Post: <mailto:susan84@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: susan84@example.org Delivered-To: mailing list susan84@example.org Received: (qmail 50167 invoked by uid 99); 6 Aug 2009 03:36:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Aug 2009 03:36:28 +0000 X-ASF-Spam-Status: No, hits=-1.8 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of susan84@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO e1.ny.us.ibm.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Aug 2009 03:36:16 +0000 Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [83.161.120.155]) by e1.ny.us.ibm.com (8.14.3/8.13.1) with ESMTP id n763UOur030569 for <susan84@example.org>; Wed, 5 Aug 2009 23:30:24 -0400 Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [83.161.120.155]) by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id n763ZpB3248994 for <susan84@example.org>; Wed, 5 Aug 2009 23:35:51 -0400 Received: from d01av04.pok.ibm.com (loopback [83.161.120.155]) by d01av04.pok.ibm.com (83.161.120.15560308/8.13.3) with ESMTP id n763Zpvw004172 for <susan84@example.org>; Wed, 5 Aug 2009 23:35:51 -0400 Received: from d25ml03.torolab.ibm.com (d25ml03.torolab.ibm.com [83.161.120.155]) by d01av04.pok.ibm.com (83.161.120.15560308/8.12.11) with ESMTP id n763Zplh004164; Wed, 5 Aug 2009 23:35:51 -0400 In-Reply-To: <susan84@example.org> Subject: Re: GSoC Update To: susan84@example.org Cc: susan84@example.org X-Mailer: Lotus Notes Release 7.0 HF277 June 21, 2006 Message-ID: <susan84@example.org> From: Michael Glavassevich <susan84@example.org> Date: Wed, 5 Aug 2009 23:35:50 -0400 X-MIMETrack: Serialize by Router on D25ML03/25/M/IBM(Release 8.0.1|February 07, 2008) at 08/05/2009 23:35:50 MIME-Version: 1.0 Content-type: multipart/alternative; Boundary="0__=0ABBFC99DF8226E18f9e8a93df938690918c0ABBFC99DF8226E1" Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org --0__=0ABBFC99DF8226E18f9e8a93df938690918c0ABBFC99DF8226E1 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: quoted-printable Hi Richard, Richard Kelly <susan84@example.org> wrote on 08/01/2009 09:05:34 AM: > Hi again, > > First of all, apologies for the late update, my new semester has > started here and it's been quite busy. No worries. University was still recent enough that I can still remembe= r how crazy busy it can get. > However I've still been working away on my code and I think the > functionality is mostly complete at > this stage, but I still have some bugs to fix and a lot of testing t= o do. > > I have a few more questions: > > I've added some code to normalize() functions in various Node > subclasses. Do I need to generate a new > serialization version for these classes (I didn't change any data > members)? If so, how do i do that? I assume this is for normalizing the characters in text nodes if the "normalize-characters" parameter is set to true. I expect that would on= ly mutate the values of existing fields. We've been trying to keep DOM serialization compatible with earlier releases. Changing the values of serialVersionUIDs would bust that. Some users actually depend on this s= o need to be careful with the changes we make, but since you said "I didn= 't change any data members" it sounds like your changes are safe. > Another question I had that I want to find out the name of the elemen= t > currently being processed. Is there > a generic way to get this information from within the pipeline or do = I > need to keep track of the current > element within my component? Aside from the startElement(), emptyElement() and endElement() methods = on XMLDocumentHandler there isn't anything else. If you need to keep track= of where you are in between these events, pushing (in startElement()) and popping (in endElement()) the names on a stack works well. > Thanks, > Richard > > ---------------------------------------------------------------------= > To unsubscribe, e-mail: susan84@example.org > For additional commands, e-mail: susan84@example.org Thanks. Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: susan84@example.org E-mail: susan84@example.org= --0__=0ABBFC99DF8226E18f9e8a93df938690918c0ABBFC99DF8226E1 Content-type: text/html; charset=US-ASCII Content-Disposition: inline Content-transfer-encoding: quoted-printable <html><body> <p><tt>Hi Richard,</tt><br> <br> <tt>Richard Kelly &lt;susan84@example.org&gt; wrote on 08/01/2009 09:05:34= AM:<br> <br> &gt; Hi again,<br> &gt; <br> &gt; First of all, apologies for the late update, my new semester has<b= r> &gt; started here and it's been quite busy.</tt><br> <br> <tt>No worries. University was still recent enough that I can still rem= ember how crazy busy it can get.</tt><br> <tt><br> &gt; However I've still been working away on my code and I think the<br= > &gt; functionality is mostly complete at<br> &gt; this stage, &nbsp;but I still have some bugs to fix and a lot of t= esting to do.<br> &gt; <br> &gt; I have a few more questions:<br> &gt; <br> &gt; I've added some code to normalize() functions in various Node<br> &gt; subclasses. &nbsp;Do I need to generate a new<br> &gt; serialization version for these classes (I didn't change any data<= br> &gt; members)? &nbsp;If so, how do i do that?<br> </tt><br> <tt>I assume this is for normalizing the characters in text nodes if th= e &quot;normalize-characters&quot; parameter is set to true. I expect t= hat would only mutate the values of existing fields. We've been trying = to keep DOM serialization compatible with earlier releases. Changing th= e values of serialVersionUIDs would bust that. Some users actually depe= nd on this so need to be careful with the changes we make, but since yo= u said &quot;I didn't change any data members&quot; it sounds like your= changes are safe.</tt><br> <tt><br> &gt; Another question I had that I want to find out the name of the ele= ment<br> &gt; currently being processed. &nbsp;Is there<br> &gt; a generic way to get this information from within the pipeline or = do I<br> &gt; need to keep track of the current<br> &gt; element within my component?<br> </tt><br> <tt>Aside from the startElement(), emptyElement() and endElement() meth= ods on XMLDocumentHandler there isn't anything else. If you need to kee= p track of where you are in between these events, pushing (in startElem= ent()) and popping (in endElement()) the names on a stack works well.</= tt><br> <tt><br> &gt; Thanks,<br> &gt; Richard<br> &gt; <br> &gt; ------------------------------------------------------------------= ---<br> &gt; To unsubscribe, e-mail: susan84@example.org<br> &gt; For additional commands, e-mail: susan84@example.org</tt>= <br> <br> <tt>Thanks.</tt><br> <br> <tt>Michael Glavassevich<br> XML Parser Development<br> IBM Toronto Lab<br> E-mail: susan84@example.org</tt><br> <tt>E-mail: susan84@example.org</tt></body></html>= --0__=0ABBFC99DF8226E18f9e8a93df938690918c0ABBFC99DF8226E1-- From susan84@example.org Thu Aug 06 05:34:30 2009 Return-Path: <susan84@example.org> Delivered-To: susan84@example.org Received: (qmail 87238 invoked from network); 6 Aug 2009 05:34:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 6 Aug 2009 05:34:30 -0000 Received: (qmail 22409 invoked by uid 500); 6 Aug 2009 05:34:37 -0000 Delivered-To: susan84@example.org Received: (qmail 22344 invoked by uid 500); 6 Aug 2009 05:34:37 -0000 Mailing-List: contact susan84@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:susan84@example.org> List-Unsubscribe: <mailto:susan84@example.org> List-Post: <mailto:susan84@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: susan84@example.org Delivered-To: mailing list susan84@example.org Received: (qmail 22336 invoked by uid 99); 6 Aug 2009 05:34:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Aug 2009 05:34:37 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Aug 2009 05:34:34 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id D7FE629A0013 for <susan84@example.org>; Wed, 5 Aug 2009 22:34:14 -0700 (PDT) Message-ID: <238362964.1249536854883.JavaMail.jira@brutus> Date: Wed, 5 Aug 2009 22:34:14 -0700 (PDT) From: "Mukul Gandhi (JIRA)" <susan84@example.org> To: susan84@example.org Subject: [jira] Created: (XERCESJ-1391) XML Schema 1.1, inheritable attributes implementation MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org XML Schema 1.1, inheritable attributes implementation ----------------------------------------------------- Key: XERCESJ-1391 URL: https://issues.apache.org/jira/browse/XERCESJ-1391 Project: Xerces2-J Issue Type: New Feature Components: XML Schema 1.1 Structures Affects Versions: 2.9.1 Reporter: Mukul Gandhi Hi all, I have written an implementation, for XML Schema 1.1 inheritable attributes. I am creating this JIRA issue for inheritable attributes, with a patch. I think, that a review of these changes would be good before we commit these changes to SVN server. This will help to ensure the correctness of implementation, and better quality of the code. I request, that this JIRA issue be assigned to the appropriate reviewer. Below are some implementation details, and a bit of design thinking I have in mind, for inherited attributes implementation. This patch has all the implementation for attribute traversal changes, and also some changes in XMLSchemaValidator.java (which are currently not finalized, but I plan to use these changes in CTA and assertions enhancements, for inheritable attributes). I am also attaching a dummy XML and XSD files, which I used to verify the attribute traversal changes. The attached XML is valid, for the given XSD, using the current XML Schema 1.1 code in SVN, plus this patch that I have written. As mentioned above, apart from attribute traversal changes (which are working fine, and tested at my end), the following code has been written in XMLSchemaValidator.java, which I plan to use to enhance CTA and assertions implementation, for inherited attributes: I have written a new method, saveInheritableAttributes(..) in XMLSchemaValidator.java, which I am invoking from, handleStartElement method. [1] CTA (conditional type assignment) changes I plan to enhance CTA implementation as following, to be able to use inherited attributes: In XMLSchemaValidator.java, I plan to modify the code fragment for CTA (the fragment, //process type alternatives). I'll add inherited attributes from the list, fInheritableAttrMap (using the element level information, which is the key to this map object) to the "attributes (of type XMLAttributes)" list. Rest of the code for CTA will remain same. The statement, if (test != null && test.evaluateTest(element, attributes)) { would use the new list of attributes (attributes, which are physically present on this element, plus the inherited attributes). After the CTA processing is complete (i.e after a type from CTA is assigned to the element), I'll remove the inherited attributes from the "attributes" list, so the original set of attributes is used by code after CTA processing. I think, these are all the changes that are required to enhance CTA implementation, to be able to use inherited attributes. [2] Assertion enhancements I plan to enhance assertions implementation as following, to be able to use inherited attributes: In the, handleStartElement method, I'll pass the inherited attributes as well to the assertions interface. To do this, I think following: addAssertsForEvaluation(element, attributes); would change to something like, addAssertsForEvaluation(element, attributes, inheritedattributes); In XMLAssertPsychopathImpl.java, I'll add the inherited attributes as well in the XDM tree to all descendant elements. I think, these changes would be sufficient, to implement inherited attributes, on assertions. I have just outlined the logic to enhance CTA and assertions, for inherited attributes. The final code, might look a bit different, than the specifics I have mentioned here. I would be thankful, if you could send me the feedback to this patch, and confirmation (and feedback) that CTA and assertions design changes, look ok. After I recieve the feedback to this patch, and to CTA and assertions design changes, I'll do the suggested modifications. I would appreciate, feedback from any member of the xerces-dev community, as well. Regards, Mukul -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: susan84@example.org For additional commands, e-mail: susan84@example.org From susan84@example.org Thu Aug 06 05:38:30 2009 Return-Path: <susan84@example.org> Delivered-To: susan84@example.org Received: (qmail 89263 invoked from network); 6 Aug 2009 05:38:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 6 Aug 2009 05:38:30 -0000 Received: (qmail 23575 invoked by uid 500); 6 Aug 2009 05:38:37 -0000 Delivered-To: susan84@example.org Received: (qmail 23483 invoked by uid 500); 6 Aug 2009 05:38:37 -0000 Mailing-List: contact susan84@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:susan84@example.org> List-Unsubscribe: <mailto:susan84@example.org> List-Post: <mailto:susan84@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: susan84@example.org Delivered-To: mailing list susan84@example.org Received: (qmail 23475 invoked by uid 99); 6 Aug 2009 05:38:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Aug 2009 05:38:37 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Aug 2009 05:38:35 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 3064C29A0013 for <susan84@example.org>; Wed, 5 Aug 2009 22:38:15 -0700 (PDT) Message-ID: <1558287928.1249537095197.JavaMail.jira@brutus> Date: Wed, 5 Aug 2009 22:38:15 -0700 (PDT) From: "Mukul Gandhi (JIRA)" <susan84@example.org> To: susan84@example.org Subject: [jira] Updated: (XERCESJ-1391) XML Schema 1.1, inheritable attributes implementation In-Reply-To: <238362964.1249536854883.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/XERCESJ-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Gandhi updated XERCESJ-1391: ---------------------------------- Attachment: test.xsd test.xml inhr_attr_patch.txt attaching the patch file, and the sample XML and XSD files. > XML Schema 1.1, inheritable attributes implementation > ----------------------------------------------------- > > Key: XERCESJ-1391 > URL: https://issues.apache.org/jira/browse/XERCESJ-1391 > Project: Xerces2-J > Issue Type: New Feature > Components: XML Schema 1.1 Structures > Affects Versions: 2.9.1 > Reporter: Mukul Gandhi > Attachments: inhr_attr_patch.txt, test.xml, test.xsd > > > Hi all, > I have written an implementation, for XML Schema 1.1 inheritable attributes. I am creating this JIRA issue for inheritable > attributes, with a patch. > I think, that a review of these changes would be good before we commit these changes to SVN server. This will help to ensure the correctness of implementation, and better quality of the code. > I request, that this JIRA issue be assigned to the appropriate reviewer. > Below are some implementation details, and a bit of design thinking I have in mind, for inherited attributes implementation. > This patch has all the implementation for attribute traversal changes, and also some changes in XMLSchemaValidator.java > (which are currently not finalized, but I plan to use these changes in CTA and assertions enhancements, for inheritable > attributes). > I am also attaching a dummy XML and XSD files, which I used to verify the attribute traversal changes. The attached XML is > valid, for the given XSD, using the current XML Schema 1.1 code in SVN, plus this patch that I have written. > As mentioned above, apart from attribute traversal changes (which are working fine, and tested at my end), the following code has been written in XMLSchemaValidator.java, which I plan to use to enhance CTA and assertions implementation, for inherited attributes: > I have written a new method, saveInheritableAttributes(..) in XMLSchemaValidator.java, which I am invoking from, > handleStartElement method. > [1] CTA (conditional type assignment) changes > I plan to enhance CTA implementation as following, to be able to use inherited attributes: > In XMLSchemaValidator.java, I plan to modify the code fragment for CTA (the fragment, //process type alternatives). I'll add > inherited attributes from the list, fInheritableAttrMap (using the element level information, which is the key to this map > object) to the "attributes (of type XMLAttributes)" list. > Rest of the code for CTA will remain same. The statement, > if (test != null && test.evaluateTest(element, attributes)) { > would use the new list of attributes (attributes, which are physically present on this element, plus the inherited attributes). > After the CTA processing is complete (i.e after a type from CTA is assigned to the element), I'll remove the inherited > attributes from the "attributes" list, so the original set of attributes is used by code after CTA processing. > I think, these are all the changes that are required to enhance CTA implementation, to be able to use inherited attributes. > [2] Assertion enhancements > I plan to enhance assertions implementation as following, to be able to use inherited attributes: > In the, handleStartElement method, I'll pass the inherited attributes as well to the assertions interface. > To do this, I think following: > addAssertsForEvaluation(element, attributes); > would change to something like, > addAssertsForEvaluation(element, attributes, inheritedattributes); > In XMLAssertPsychopathImpl.java, I'll add the inherited attributes as well in the XDM tree to all descendant elements. > I think, these changes would be sufficient, to implement inherited attributes, on assertions. > I have just outlined the logic to enhance CTA and assertions, for inherited attributes. The final code, might look a bit > different, than the specifics I have mentioned here. > I would be thankful, if you could send me the feedback to this patch, and confirmation (and feedback) that CTA and assertions design changes, look ok. > After I recieve the feedback to this patch, and to CTA and assertions design changes, I'll do the suggested modifications. > I would appreciate, feedback from any member of the xerces-dev community, as well. > Regards, > Mukul -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: susan84@example.org For additional commands, e-mail: susan84@example.org From susan84@example.org Thu Aug 06 21:56:06 2009 Return-Path: <susan84@example.org> Delivered-To: susan84@example.org Received: (qmail 9085 invoked from network); 6 Aug 2009 21:56:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 6 Aug 2009 21:56:06 -0000 Received: (qmail 77493 invoked by uid 500); 6 Aug 2009 21:56:13 -0000 Delivered-To: susan84@example.org Received: (qmail 77431 invoked by uid 500); 6 Aug 2009 21:56:13 -0000 Mailing-List: contact susan84@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:susan84@example.org> List-Unsubscribe: <mailto:susan84@example.org> List-Post: <mailto:susan84@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: susan84@example.org Delivered-To: mailing list susan84@example.org Received: (qmail 77423 invoked by uid 99); 6 Aug 2009 21:56:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Aug 2009 21:56:13 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of susan84@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mail01.websulting.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Aug 2009 21:56:03 +0000 Received: from localhost (localhost.localdomain [83.161.120.155]) by mail01.websulting.com (Postfix) with ESMTP id 42B7571C023 for <susan84@example.org>; Thu, 6 Aug 2009 17:55:41 -0400 (EDT) Received: from mail01.websulting.com ([83.161.120.155]) by localhost (mail01.websulting.com [83.161.120.155]) (amavisd-new, port 10024) with LMTP id 27174-01-14 for <susan84@example.org>; Thu, 6 Aug 2009 17:55:41 -0400 (EDT) Received: from [83.161.120.155] (gw2.dc.gov [83.161.120.155]) by mail01.websulting.com (Postfix) with ESMTP id 1748771C022 for <susan84@example.org>; Thu, 6 Aug 2009 17:55:41 -0400 (EDT) Message-ID: <susan84@example.org> Date: Thu, 06 Aug 2009 17:55:42 -0400 From: SGSWeb <susan84@example.org> User-Agent: Thunderbird 83.161.120.155 (Windows/20090605) MIME-Version: 1.0 To: susan84@example.org Subject: Restrict getElementsByTagName to Top Level Content-Type: multipart/alternative; boundary="------------030404040106060003000303" X-Virus-Scanned: susan84@example.org X-Virus-Checked: Checked by ClamAV on apache.org --------------030404040106060003000303 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I have an XML file as follows: |<rootNode> <link>http://rootlink/</link> <image> <link>http://imagelink/</link> <title>This is the title</title> </image> </rootNode> | The XML Java code using DOM is as follows: |NodeList rootNodeList = element.getElementsByTagName("link"); | This will give me all of the "link" elements including the top level and the one inside the "image" node. Is there a way to just get the "link" tags for rootNode within one level and not two such as is the case for the image link? That is, I just want the http://rootlink/ "link". thanks, sgs. --------------030404040106060003000303 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> </head> <body bgcolor="#ffffff" text="#000000"> <p>I have an XML file as follows:</p> <pre class="prettyprint" jquery1249595642133="25"><code><span class="pun">&lt;</span><span class="tag">rootNode</span><span class="pun">&gt;</span><span class="pln"> &nbsp; &nbsp; </span><span class="pun">&lt;</span><span class="tag">link</span><span class="pun">&gt;</span><span class="pln"><a class="moz-txt-link-freetext" href="http://rootlink/">http://rootlink/</a></span><span class="pun">&lt;/</span><span class="tag">link</span><span class="pun">&gt;</span><span class="pln"> &nbsp; &nbsp; </span><span class="pun">&lt;</span><span class="tag">image</span><span class="pun">&gt;</span><span class="pln"> &nbsp; &nbsp; &nbsp; &nbsp; </span><span class="pun">&lt;</span><span class="tag">link</span><span class="pun">&gt;</span><span class="pln"><a class="moz-txt-link-freetext" href="http://imagelink/">http://imagelink/</a></span><span class="pun">&lt;/</span><span class="tag">link</span><span class="pun">&gt;</span><span class="pln"> &nbsp; &nbsp; &nbsp; &nbsp; </span><span class="pun">&lt;</span><span class="tag">title</span><span class="pun">&gt;</span><span class="pln">This is the title</span><span class="pun">&lt;/</span><span class="tag">title</span><span class="pun">&gt;</span><span class="pln"> &nbsp; &nbsp; </span><span class="pun">&lt;/</span><span class="tag">image</span><span class="pun">&gt;</span><span class="pln"> </span><span class="pun">&lt;/</span><span class="tag">rootNode</span><span class="pun">&gt;</span><span class="pln"> </span></code></pre> <p>The XML Java code using DOM is as follows:</p> <pre class="prettyprint" jquery1249595642133="26"><code><span class="typ">NodeList</span><span class="pln"> rootNodeList </span><span class="pun">=</span><span class="pln"> element</span><span class="pun">.</span><span class="pln">getElementsByTagName</span><span class="pun">(</span><span class="str">"link"</span><span class="pun">);</span><span class="pln"> </span></code></pre> <p>This will give me all of the "link" elements including the top level and the one inside the "image" node.</p> <p>Is there a way to just get the "link" tags for rootNode within one level and not two such as is the case for the image link? That is, I just want the <a href="http://rootlink/" rel="nofollow">http://rootlink/</a> "link".<br> </p> <p>thanks,<br> sgs.<br> </p> </body> </html> --------------030404040106060003000303-- From susan84@example.org Fri Aug 07 01:46:41 2009 Return-Path: <susan84@example.org> Delivered-To: susan84@example.org Received: (qmail 81912 invoked from network); 7 Aug 2009 01:46:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 7 Aug 2009 01:46:41 -0000 Received: (qmail 74674 invoked by uid 500); 7 Aug 2009 01:46:48 -0000 Delivered-To: susan84@example.org Received: (qmail 74618 invoked by uid 500); 7 Aug 2009 01:46:48 -0000 Mailing-List: contact susan84@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:susan84@example.org> List-Unsubscribe: <mailto:susan84@example.org> List-Post: <mailto:susan84@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: susan84@example.org Delivered-To: mailing list susan84@example.org Received: (qmail 74610 invoked by uid 99); 7 Aug 2009 01:46:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Aug 2009 01:46:48 +0000 X-ASF-Spam-Status: No, hits=-1.8 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of susan84@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO e6.ny.us.ibm.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Aug 2009 01:46:38 +0000 Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [83.161.120.155]) by e6.ny.us.ibm.com (8.14.3/8.13.1) with ESMTP id n771nttQ019555 for <susan84@example.org>; Thu, 6 Aug 2009 21:49:55 -0400 Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [83.161.120.155]) by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id n771k7b9257986 for <susan84@example.org>; Thu, 6 Aug 2009 21:46:07 -0400 Received: from d01av01.pok.ibm.com (loopback [83.161.120.155]) by d01av01.pok.ibm.com (83.161.120.15560308/8.13.3) with ESMTP id n771k66Y025464 for <susan84@example.org>; Thu, 6 Aug 2009 21:46:07 -0400 Received: from d25ml04.torolab.ibm.com (d25ml04.torolab.ibm.com [83.161.120.155]) by d01av01.pok.ibm.com (83.161.120.15560308/8.12.11) with ESMTP id n771k6Mj025455 for <susan84@example.org>; Thu, 6 Aug 2009 21:46:06 -0400 In-Reply-To: <susan84@example.org> To: susan84@example.org MIME-Version: 1.0 Subject: Re: Restrict getElementsByTagName to Top Level X-Mailer: Lotus Notes Release 7.0 HF277 June 21, 2006 Message-ID: <susan84@example.org> From: Arthur De Magalhaes <susan84@example.org> Date: Thu, 6 Aug 2009 21:46:07 -0400 X-MIMETrack: Serialize by Router on D25ML04/25/M/IBM(Release 8.0.1|February 07, 2008) at 08/06/2009 21:46:06, Serialize complete at 08/06/2009 21:46:06 Content-Type: multipart/alternative; boundary="=_alternative 0009B8928525760B_=" X-Virus-Checked: Checked by ClamAV on apache.org --=_alternative 0009B8928525760B_= Content-Type: text/plain; charset="US-ASCII" Hi, You could use namespaces to distinguish the two links, and then use the namespace variant of that method: getElementsByTagNameNS [1]. So you could have something like: <rootNode> <a:link xmlns:a="http://rootlink/">http://rootlink/</a:link> <image> <b:link xmlns:b="http://imagelink/">http://imagelink/</b:link> <title>This is the title</title> </image> </rootNode> Then use: getElementsByTagNameNS("http://rootlink/", "link") Thx, [1] http://java.sun.com/j2se/1.4.2/docs/api/org/w3c/dom/Element.html#getElementsByTagNameNS(java.lang.String,%20java.lang.String) Arthur De Magalhaes Software Engineer - XML Parser & XCI Development IBM Canada - Toronto Lab Phone: +1-323-288-6857 T/L 313-2993 E-mail: susan84@example.org SGSWeb <susan84@example.org> 08/06/2009 05:55 PM Please respond to susan84@example.org To susan84@example.org cc Subject Restrict getElementsByTagName to Top Level I have an XML file as follows: <rootNode> <link>http://rootlink/</link> <image> <link>http://imagelink/</link> <title>This is the title</title> </image> </rootNode> The XML Java code using DOM is as follows: NodeList rootNodeList = element.getElementsByTagName("link"); This will give me all of the "link" elements including the top level and the one inside the "image" node. Is there a way to just get the "link" tags for rootNode within one level and not two such as is the case for the image link? That is, I just want the http://rootlink/ "link". thanks, sgs. --=_alternative 0009B8928525760B_= Content-Type: text/html; charset="US-ASCII" <br><font size=2 face="sans-serif">Hi,</font> <br> <br><font size=2 face="sans-serif">You could use namespaces to distinguish the two links, and then use the namespace variant of that method: &nbsp;getElementsByTagNameNS [1].</font> <br> <br><font size=2 face="sans-serif">So you could have something like:</font> <br> <br><font size=2 face="sans-serif">&lt;rootNode&gt;</font> <br><font size=2 face="sans-serif">&nbsp; &nbsp; &lt;a:link xmlns:a=&quot;http://rootlink/&quot;&gt;http://rootlink/&lt;/a:link&gt;</font> <br><font size=2 face="sans-serif">&nbsp; &nbsp; &lt;image&gt;</font> <br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &lt;b:link xmlns:b=&quot;http://imagelink/&quot;&gt;http://imagelink/&lt;/b:link&gt;</font> <br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &lt;title&gt;This is the title&lt;/title&gt;</font> <br><font size=2 face="sans-serif">&nbsp; &nbsp; &lt;/image&gt;</font> <br><font size=2 face="sans-serif">&lt;/rootNode&gt;</font> <br> <br> <br><font size=2 face="sans-serif">Then use: &nbsp;</font><font size=2 face="Courier New">getElementsByTagNameNS(</font><font size=2 color=#4200ff face="Courier New">&quot;http://rootlink/&quot;</font><font size=2 face="Courier New">, </font><font size=2 color=#4200ff face="Courier New">&quot;link&quot;</font><font size=2 face="Courier New">)</font> <br> <br><font size=2 face="sans-serif">Thx,</font> <br> <br><font size=2 face="sans-serif">[1] http://java.sun.com/j2se/1.4.2/docs/api/org/w3c/dom/Element.html#getElementsByTagNameNS(java.lang.String,%20java.lang.String)</font> <br><font size=2 face="sans-serif"><br> Arthur De Magalhaes<br> Software Engineer - XML Parser &amp; XCI Development<br> IBM Canada - Toronto Lab<br> Phone: +1-323-288-6857 T/L 313-2993<br> E-mail: susan84@example.org<br> </font> <br> <br> <br> <table width=100%> <tr valign=top> <td width=40%><font size=1 face="sans-serif"><b>SGSWeb &lt;susan84@example.org&gt;</b> </font> <p><font size=1 face="sans-serif">08/06/2009 05:55 PM</font> <table border> <tr valign=top> <td bgcolor=white> <div align=center><font size=1 face="sans-serif">Please respond to<br> susan84@example.org</font></div></table> <br> <td width=59%> <table width=100%> <tr valign=top> <td> <div align=right><font size=1 face="sans-serif">To</font></div> <td><font size=1 face="sans-serif">susan84@example.org</font> <tr valign=top> <td> <div align=right><font size=1 face="sans-serif">cc</font></div> <td> <tr valign=top> <td> <div align=right><font size=1 face="sans-serif">Subject</font></div> <td><font size=1 face="sans-serif">Restrict getElementsByTagName to Top Level</font></table> <br> <table> <tr valign=top> <td> <td></table> <br></table> <br> <br> <br><font size=3>I have an XML file as follows:</font> <p><tt><font size=3>&lt;rootNode&gt;<br> &nbsp; &nbsp;&lt;link&gt;</font></tt><a href=http://rootlink/><tt><font size=3 color=blue><u>http://rootlink/</u></font></tt></a><tt><font size=3>&lt;/link&gt;<br> &nbsp; &nbsp;&lt;image&gt;<br> &nbsp; &nbsp; &nbsp; &nbsp;&lt;link&gt;</font></tt><a href=http://imagelink/><tt><font size=3 color=blue><u>http://imagelink/</u></font></tt></a><tt><font size=3>&lt;/link&gt;<br> &nbsp; &nbsp; &nbsp; &nbsp;&lt;title&gt;This is the title&lt;/title&gt;<br> &nbsp; &nbsp;&lt;/image&gt;<br> &lt;/rootNode&gt;<br> </font></tt> <p><font size=3>The XML Java code using DOM is as follows:</font> <p><tt><font size=3>NodeList rootNodeList = element.getElementsByTagName(&quot;link&quot;);<br> </font></tt> <p><font size=3>This will give me all of the &quot;link&quot; elements including the top level and the one inside the &quot;image&quot; node.</font> <p><font size=3>Is there a way to just get the &quot;link&quot; tags for rootNode within one level and not two such as is the case for the image link? That is, I just want the </font><a href=http://rootlink/><font size=3 color=blue><u>http://rootlink/</u></font></a><font size=3> &quot;link&quot;.</font> <p><font size=3>thanks,<br> sgs.</font> <p> --=_alternative 0009B8928525760B_=-- From susan84@example.org Sat Aug 08 10:24:33 2009 Return-Path: <susan84@example.org> Delivered-To: susan84@example.org Received: (qmail 90258 invoked from network); 8 Aug 2009 10:24:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 8 Aug 2009 10:24:32 -0000 Received: (qmail 54717 invoked by uid 500); 8 Aug 2009 10:24:40 -0000 Delivered-To: susan84@example.org Received: (qmail 54626 invoked by uid 500); 8 Aug 2009 10:24:39 -0000 Mailing-List: contact susan84@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:susan84@example.org> List-Unsubscribe: <mailto:susan84@example.org> List-Post: <mailto:susan84@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: susan84@example.org Delivered-To: mailing list susan84@example.org Received: (qmail 54613 invoked by uid 99); 8 Aug 2009 10:24:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 08 Aug 2009 10:24:39 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 08 Aug 2009 10:24:36 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id ED276234C044 for <susan84@example.org>; Sat, 8 Aug 2009 03:24:14 -0700 (PDT) Message-ID: <82499110.1249727054970.JavaMail.jira@brutus> Date: Sat, 8 Aug 2009 03:24:14 -0700 (PDT) From: "Mukul Gandhi (JIRA)" <susan84@example.org> To: susan84@example.org Subject: [jira] Commented: (XERCESJ-1391) XML Schema 1.1, inheritable attributes implementation In-Reply-To: <238362964.1249536854883.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/XERCESJ-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740868#action_12740868 ] Mukul Gandhi commented on XERCESJ-1391: --------------------------------------- I recently, raised a clarification to the XML Schema WG (after I posted this JIRA issue). I am told, that inheritable attributes are not required for assertions. But they will be needed by CTA. So, we have to modify the XDM construction for CTA to include inheritable attributes. No changes will be required for assertions, for the inherited attributes. I think, I should be able to do the inherited attributes changes for CTA. It shouldn't be much complex, I believe. In case, I need help, I might ask Hiranya (the original author of CTA in Xerces-J) or perhaps other members, of the xerces-dev community. I am looking forward, to some kind of feedback to this patch. Regards, Mukul > XML Schema 1.1, inheritable attributes implementation > ----------------------------------------------------- > > Key: XERCESJ-1391 > URL: https://issues.apache.org/jira/browse/XERCESJ-1391 > Project: Xerces2-J > Issue Type: New Feature > Components: XML Schema 1.1 Structures > Affects Versions: 2.9.1 > Reporter: Mukul Gandhi > Attachments: inhr_attr_patch.txt, test.xml, test.xsd > > > Hi all, > I have written an implementation, for XML Schema 1.1 inheritable attributes. I am creating this JIRA issue for inheritable > attributes, with a patch. > I think, that a review of these changes would be good before we commit these changes to SVN server. This will help to ensure the correctness of implementation, and better quality of the code. > I request, that this JIRA issue be assigned to the appropriate reviewer. > Below are some implementation details, and a bit of design thinking I have in mind, for inherited attributes implementation. > This patch has all the implementation for attribute traversal changes, and also some changes in XMLSchemaValidator.java > (which are currently not finalized, but I plan to use these changes in CTA and assertions enhancements, for inheritable > attributes). > I am also attaching a dummy XML and XSD files, which I used to verify the attribute traversal changes. The attached XML is > valid, for the given XSD, using the current XML Schema 1.1 code in SVN, plus this patch that I have written. > As mentioned above, apart from attribute traversal changes (which are working fine, and tested at my end), the following code has been written in XMLSchemaValidator.java, which I plan to use to enhance CTA and assertions implementation, for inherited attributes: > I have written a new method, saveInheritableAttributes(..) in XMLSchemaValidator.java, which I am invoking from, > handleStartElement method. > [1] CTA (conditional type assignment) changes > I plan to enhance CTA implementation as following, to be able to use inherited attributes: > In XMLSchemaValidator.java, I plan to modify the code fragment for CTA (the fragment, //process type alternatives). I'll add > inherited attributes from the list, fInheritableAttrMap (using the element level information, which is the key to this map > object) to the "attributes (of type XMLAttributes)" list. > Rest of the code for CTA will remain same. The statement, > if (test != null && test.evaluateTest(element, attributes)) { > would use the new list of attributes (attributes, which are physically present on this element, plus the inherited attributes). > After the CTA processing is complete (i.e after a type from CTA is assigned to the element), I'll remove the inherited > attributes from the "attributes" list, so the original set of attributes is used by code after CTA processing. > I think, these are all the changes that are required to enhance CTA implementation, to be able to use inherited attributes. > [2] Assertion enhancements > I plan to enhance assertions implementation as following, to be able to use inherited attributes: > In the, handleStartElement method, I'll pass the inherited attributes as well to the assertions interface. > To do this, I think following: > addAssertsForEvaluation(element, attributes); > would change to something like, > addAssertsForEvaluation(element, attributes, inheritedattributes); > In XMLAssertPsychopathImpl.java, I'll add the inherited attributes as well in the XDM tree to all descendant elements. > I think, these changes would be sufficient, to implement inherited attributes, on assertions. > I have just outlined the logic to enhance CTA and assertions, for inherited attributes. The final code, might look a bit > different, than the specifics I have mentioned here. > I would be thankful, if you could send me the feedback to this patch, and confirmation (and feedback) that CTA and assertions design changes, look ok. > After I recieve the feedback to this patch, and to CTA and assertions design changes, I'll do the suggested modifications. > I would appreciate, feedback from any member of the xerces-dev community, as well. > Regards, > Mukul -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: susan84@example.org For additional commands, e-mail: susan84@example.org From susan84@example.org Sun Aug 09 06:18:33 2009 Return-Path: <susan84@example.org> Delivered-To: susan84@example.org Received: (qmail 26318 invoked from network); 9 Aug 2009 06:18:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 9 Aug 2009 06:18:33 -0000 Received: (qmail 42967 invoked by uid 500); 9 Aug 2009 06:18:40 -0000 Delivered-To: susan84@example.org Received: (qmail 42878 invoked by uid 500); 9 Aug 2009 06:18:40 -0000 Mailing-List: contact susan84@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:susan84@example.org> List-Unsubscribe: <mailto:susan84@example.org> List-Post: <mailto:susan84@example.org> List-Id: <j-dev.xerces.apache.org> Reply-To: susan84@example.org Delivered-To: mailing list susan84@example.org Received: (qmail 42870 invoked by uid 99); 9 Aug 2009 06:18:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 09 Aug 2009 06:18:40 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 09 Aug 2009 06:18:36 +0000 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 2DCBF234C044 for <susan84@example.org>; Sat, 8 Aug 2009 23:18:15 -0700 (PDT) Message-ID: <358270163.1249798695186.JavaMail.jira@brutus> Date: Sat, 8 Aug 2009 23:18:15 -0700 (PDT) From: "Hiranya Jayathilaka (JIRA)" <susan84@example.org> To: susan84@example.org Subject: [jira] Commented: (XERCESJ-1391) XML Schema 1.1, inheritable attributes implementation In-Reply-To: <238362964.1249536854883.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/XERCESJ-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741034#action_12741034 ] Hiranya Jayathilaka commented on XERCESJ-1391: ---------------------------------------------- Yes. CTA is one area that can make use of this enhancement. I think to support this we need to slightly change how XML attributes are passed into the CTA code. > XML Schema 1.1, inheritable attributes implementation > ----------------------------------------------------- > > Key: XERCESJ-1391 > URL: https://issues.apache.org/jira/browse/XERCESJ-1391 > Project: Xerces2-J > Issue Type: New Feature > Components: XML Schema 1.1 Structures > Affects Versions: 2.9.1 > Reporter: Mukul Gandhi > Attachments: inhr_attr_patch.txt, test.xml, test.xsd > > > Hi all, > I have written an implementation, for XML Schema 1.1 inheritable attributes. I am creating this JIRA issue for inheritable > attributes, with a patch. > I think, that a review of these changes would be good before we commit these changes to SVN server. This will help to ensure the correctness of implementation, and better quality
{'source': 'Apache Software Foundation Public Mail Archives'}