Mailing-List: contact dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ws.apache.org
Date: Thu, 11 May 2017 00:54:04 +0000 (UTC)
From: "Aron Olsen (JIRA)" <jira@apache.org>
To: dev@ws.apache.org
Message-ID: <JIRA.13071008.1494463467000.182501.1494464044030@Atlassian.JIRA>
In-Reply-To: <JIRA.13071008.1494463467000@Atlassian.JIRA>
References: <JIRA.13071008.1494463467000@Atlassian.JIRA> <JIRA.13071008.1494463467084@jira-lw-us.apache.org>
Subject: [jira] [Updated] (XMLSCHEMA-48) How to inherit attributes down to
 final complex type
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 11 May 2017 00:54:11 -0000


     [ https://issues.apache.org/jira/browse/XMLSCHEMA-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aron Olsen updated XMLSCHEMA-48:
--------------------------------
    Description: 
Hi there,
I am in the scenary of traversing the out-come of reading an XSD.
I am somewhat trying to simplify the output of XMLSchema, in order to have the properties (elements and attributes) mapped to DB-tables (complex types) and DB-table-columns (mayby XSD-complex, geometries for instance or other DB-complex-types or XSD-simple, string, int etc.).
I am bewildered about how attributes are to be inherited down to a complex XSD type when deriving from another XSD-type by restriction. As I have learned so far, all attributes are to be inherited by default, as opposed to element-properties of the base-type.
Is this rightly understood by me?
In my simplified model I keep track of the base-type hierarchy, and how the inheritance is defined (extension, restriction, final). For each level I have tracked all the attributes of each complex type. Do I need to "collect" base-type attributes not referenced in a current complex type, when the current complex type is deriving from a super-type by restriction?
In other words: Do XmlSchema do any automic inheritance derivations "behind the scenes", or do we have to do such on our own behalf?
As you will understand: If XmlSchema is not doing the attribute-inheriting for me, I have to do it my self. This will involve "inherit all attributes from base-type which is not mentioned in current type".
Hope my question is understandable: How to inherit attributes when deriving by restriction.
/Aron


  was:
Hi there,
I am in the scenary of traversing the out-come of reading an XSD.
I am somewhat trying to simplify the output of XMLSchema, in order to have the properties (elements and attributes) mapped to DB-tables (complex types) and DB-table-columns (mayby XSD-complex, geometries for instance or other DB-complex-types or XSD-simple, string, int etc.).
I am bewildered about how attributes are to be inherited down to a complex XSD type when deriving from another XSD-type by restriction. As I have learned so far, all attributes are to be inherited by default, as opposed to element-properties of the base-type.
Is this rightly understood by me?
In my simplified model I keep track of the base-type hierarchy, and how the inheritance is defined (extension, restriction, final). For each level I have tracked all the attributes of each complex type. Do I need to "collect" base-type attributes not referenced in a current complex type, when the current complex type is deriving from a super-type by restriction?
In other words: Do XmlSchema do any automic inheritance derivations "behind the scenes", or do we have to do such on our own behalf?
As you will understand: If XmlSchema is not doing the attribute-inheriting for me, I have to do it my self. This will involve "inherit all attributes from base-type which is not mentioned in current type".
Hope my question is understandable: How to inherit attributes when extending by restriction.
/Aron


> How to inherit attributes down to final complex type
> ----------------------------------------------------
>
>                 Key: XMLSCHEMA-48
>                 URL: https://issues.apache.org/jira/browse/XMLSCHEMA-48
>             Project: XmlSchema
>          Issue Type: Question
>    Affects Versions: 2.2.1
>            Reporter: Aron Olsen
>            Priority: Trivial
>             Fix For: 2.1.1
>
>
> Hi there,
> I am in the scenary of traversing the out-come of reading an XSD.
> I am somewhat trying to simplify the output of XMLSchema, in order to have the properties (elements and attributes) mapped to DB-tables (complex types) and DB-table-columns (mayby XSD-complex, geometries for instance or other DB-complex-types or XSD-simple, string, int etc.).
> I am bewildered about how attributes are to be inherited down to a complex XSD type when deriving from another XSD-type by restriction. As I have learned so far, all attributes are to be inherited by default, as opposed to element-properties of the base-type.
> Is this rightly understood by me?
> In my simplified model I keep track of the base-type hierarchy, and how the inheritance is defined (extension, restriction, final). For each level I have tracked all the attributes of each complex type. Do I need to "collect" base-type attributes not referenced in a current complex type, when the current complex type is deriving from a super-type by restriction?
> In other words: Do XmlSchema do any automic inheritance derivations "behind the scenes", or do we have to do such on our own behalf?
> As you will understand: If XmlSchema is not doing the attribute-inheriting for me, I have to do it my self. This will involve "inherit all attributes from base-type which is not mentioned in current type".
> Hope my question is understandable: How to inherit attributes when deriving by restriction.
> /Aron


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org