You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by "Fernando (JIRA)" <xe...@xml.apache.org> on 2007/10/30 12:09:50 UTC

[jira] Created: (XERCESC-1755) Abstract types in substitution group

Abstract types in substitution group
------------------------------------

                 Key: XERCESC-1755
                 URL: https://issues.apache.org/jira/browse/XERCESC-1755
             Project: Xerces-C++
          Issue Type: Bug
          Components: Validating Parser (Schema) (Xerces 1.5 or up only)
    Affects Versions: 2.7.0
         Environment: Unix - Linux (SUSE)
            Reporter: Fernando


I wish to report a bug that, to my understanding, creates a problem of compatibility with XML 1.0.

Let it be a substitution group, which basic type is an abstract type A. Let it be a member B of that substitution group, which happen to be an abstract type too. Obviously, the second abstract type B is no a final type; this second abstract type B must be substituted by other final valid types.

The reason for including the second abstract B as part of the substituion group for abstract type A is to somehow structure and hierarchise the whole substitution group.

The bug I wish to report is that the second abstract type B produces a problem, since it is not allowed to be part of any substitution group.

According to XML 1.0 recommendation (that Xerces is supposed to be complaiance with), an abstract type present in a substitution group should not be a problem, since there is no restriction for this.

Could someone please check if this problem with Xerces is actually a bug to be solved in next version? Otherwise, could someone please let me know in which part of the XML 1.0 recommendation there is any constrain to abstract types as part of substitution groups?

Thanks a lot.

-- 
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: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org


[jira] Commented: (XERCESC-1755) Abstract types in substitution group

Posted by "Fernando (JIRA)" <xe...@xml.apache.org>.
    [ https://issues.apache.org/jira/browse/XERCESC-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539105 ] 

Fernando commented on XERCESC-1755:
-----------------------------------

This issue was raised from comments from my team, and I did not check this bug myself until now.
When analyzing the issue, I have realized there is no such a problem, and there was a misunderstanding with the schemas.
My apologies. Thanks for your attention anyway. This issue can be closed.

> Abstract types in substitution group
> ------------------------------------
>
>                 Key: XERCESC-1755
>                 URL: https://issues.apache.org/jira/browse/XERCESC-1755
>             Project: Xerces-C++
>          Issue Type: Bug
>          Components: Validating Parser (Schema) (Xerces 1.5 or up only)
>    Affects Versions: 2.7.0
>         Environment: Unix - Linux (SUSE)
>            Reporter: Fernando
>
> I wish to report a bug that, to my understanding, creates a problem of compatibility with XML 1.0.
> Let it be a substitution group, which basic type is an abstract type A. Let it be a member B of that substitution group, which happen to be an abstract type too. Obviously, the second abstract type B is no a final type; this second abstract type B must be substituted by other final valid types.
> The reason for including the second abstract B as part of the substituion group for abstract type A is to somehow structure and hierarchise the whole substitution group.
> The bug I wish to report is that the second abstract type B produces a problem, since it is not allowed to be part of any substitution group.
> According to XML 1.0 recommendation (that Xerces is supposed to be complaiance with), an abstract type present in a substitution group should not be a problem, since there is no restriction for this.
> Could someone please check if this problem with Xerces is actually a bug to be solved in next version? Otherwise, could someone please let me know in which part of the XML 1.0 recommendation there is any constrain to abstract types as part of substitution groups?
> Thanks a lot.

-- 
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: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org


[jira] Commented: (XERCESC-1755) Abstract types in substitution group

Posted by "David Bertoni (JIRA)" <xe...@xml.apache.org>.
    [ https://issues.apache.org/jira/browse/XERCESC-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538836 ] 

David Bertoni commented on XERCESC-1755:
----------------------------------------

Please provide a minimal schema document that illustrates the bug, along with the error message from the parser.  Otherwise, it will be difficult to investigate this.

> Abstract types in substitution group
> ------------------------------------
>
>                 Key: XERCESC-1755
>                 URL: https://issues.apache.org/jira/browse/XERCESC-1755
>             Project: Xerces-C++
>          Issue Type: Bug
>          Components: Validating Parser (Schema) (Xerces 1.5 or up only)
>    Affects Versions: 2.7.0
>         Environment: Unix - Linux (SUSE)
>            Reporter: Fernando
>
> I wish to report a bug that, to my understanding, creates a problem of compatibility with XML 1.0.
> Let it be a substitution group, which basic type is an abstract type A. Let it be a member B of that substitution group, which happen to be an abstract type too. Obviously, the second abstract type B is no a final type; this second abstract type B must be substituted by other final valid types.
> The reason for including the second abstract B as part of the substituion group for abstract type A is to somehow structure and hierarchise the whole substitution group.
> The bug I wish to report is that the second abstract type B produces a problem, since it is not allowed to be part of any substitution group.
> According to XML 1.0 recommendation (that Xerces is supposed to be complaiance with), an abstract type present in a substitution group should not be a problem, since there is no restriction for this.
> Could someone please check if this problem with Xerces is actually a bug to be solved in next version? Otherwise, could someone please let me know in which part of the XML 1.0 recommendation there is any constrain to abstract types as part of substitution groups?
> Thanks a lot.

-- 
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: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org


[jira] Closed: (XERCESC-1755) Abstract types in substitution group

Posted by "Fernando (JIRA)" <xe...@xml.apache.org>.
     [ https://issues.apache.org/jira/browse/XERCESC-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fernando closed XERCESC-1755.
-----------------------------

    Resolution: Won't Fix

MIsunderstanding with schemas. No such a bug.

> Abstract types in substitution group
> ------------------------------------
>
>                 Key: XERCESC-1755
>                 URL: https://issues.apache.org/jira/browse/XERCESC-1755
>             Project: Xerces-C++
>          Issue Type: Bug
>          Components: Validating Parser (Schema) (Xerces 1.5 or up only)
>    Affects Versions: 2.7.0
>         Environment: Unix - Linux (SUSE)
>            Reporter: Fernando
>
> I wish to report a bug that, to my understanding, creates a problem of compatibility with XML 1.0.
> Let it be a substitution group, which basic type is an abstract type A. Let it be a member B of that substitution group, which happen to be an abstract type too. Obviously, the second abstract type B is no a final type; this second abstract type B must be substituted by other final valid types.
> The reason for including the second abstract B as part of the substituion group for abstract type A is to somehow structure and hierarchise the whole substitution group.
> The bug I wish to report is that the second abstract type B produces a problem, since it is not allowed to be part of any substitution group.
> According to XML 1.0 recommendation (that Xerces is supposed to be complaiance with), an abstract type present in a substitution group should not be a problem, since there is no restriction for this.
> Could someone please check if this problem with Xerces is actually a bug to be solved in next version? Otherwise, could someone please let me know in which part of the XML 1.0 recommendation there is any constrain to abstract types as part of substitution groups?
> Thanks a lot.

-- 
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: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org