[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Issue Comment Edited: (SRAMP-1) RepresentingRelationships
[ http://tools.oasis-open.org/issues/browse/SRAMP-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24849#action_24849 ]
Kurt Stam edited comment on SRAMP-1 at 3/16/11 11:06 AM:
----------------------------------------------------------
Random list while I'm working on this:
1. the links in the document: "For convenience, an S-RAMP XSD Model Schema xsd file is also provided at:
http://s-ramp.org/2010/specification/schemas/xsdmodel.xsd"; is not valid. They can be found here instead 'http://www.s-ramp.org/8650766/xsdmodel.xsd'
2. should the license header in the xsds include the current companies involved with s-ramp?
3. the coremodel.xsd imports:
<xsd:import namespace="http://www.w3.org/1999/xlink"; schemaLocation="http://www.w3.org/1999/xlink.xsd"/>
<xsd:import namespace="http://www.w3.org/XML/1998/namespace"; schemaLocation="http://www.w3.org/2009/01/xml.xsd"/>
however xlink.xsd imports:
<xs:import namespace="http://www.w3.org/XML/1998/namespace"; schemaLocation="http://www.w3.org/2001/xml.xsd"/>
So now we have 2 versions of xml.xsd in the mix. This confuses xsd -> code generation tools like xjc. For example xjc coremodel.xsd will output
parsing a schema...
[ERROR] 'lang' is already defined
line 87 of http://www.w3.org/2009/01/xml.xsd
[ERROR] (related to above error) the first definition appears here
line 43 of http://www.w3.org/2001/xml.xsd
[ERROR] 'space' is already defined
line 111 of http://www.w3.org/2009/01/xml.xsd
[ERROR] (related to above error) the first definition appears here
line 89 of http://www.w3.org/2001/xml.xsd
[ERROR] 'base' is already defined
line 133 of http://www.w3.org/2009/01/xml.xsd
[ERROR] (related to above error) the first definition appears here
line 113 of http://www.w3.org/2001/xml.xsd
4. When resolving that, to both using the xml.xsd from 2001, or 2009, I run into the next issue:
parsing a schema...
[ERROR] Property "Title" is already defined. Use <jaxb:property> to resolve this conflict.
line 232 of http://www.w3.org/1999/xlink.xsd
[ERROR] The following location is relevant to the above error
line 219 of http://www.w3.org/1999/xlink.xsd
[ERROR] Property "Title" is already defined. Use <jaxb:property> to resolve this conflict.
line 261 of http://www.w3.org/1999/xlink.xsd
[ERROR] The following location is relevant to the above error
line 246 of http://www.w3.org/1999/xlink.xsd
Do we even need the xlink.xsd import? I don't see it referenced.
5. The xjc wsdlmodel.xsd errors out with
parsing a schema...
[ERROR] ct-props-correct.4: Error for type 'BindingOperationInput'. Duplicate attribute uses with the same name and target namespace are specified. Name of duplicate attribute use is 'NCName'.
line 130 of file:/Users/kstam/osc/jboss/dev/s-ramp/s-ramp-api/src/main/resources/s-ramp/wsdlmodel.xsd
[ERROR] ct-props-correct.4: Error for type 'OperationInput'. Duplicate attribute uses with the same name and target namespace are specified. Name of duplicate attribute use is 'NCName'.
line 156 of file:/Users/kstam/osc/jboss/dev/s-ramp/s-ramp-api/src/main/resources/s-ramp/wsdlmodel.xsd
[ERROR] ct-props-correct.4: Error for type 'BindingOperationOutput'. Duplicate attribute uses with the same name and target namespace are specified. Name of duplicate attribute use is 'NCName'.
line 202 of file:/Users/kstam/osc/jboss/dev/s-ramp/s-ramp-api/src/main/resources/s-ramp/wsdlmodel.xsd
I'm proposing to give these attributes unique names: NCName1, NCName2 and NCName3; or something more descriptive.
After addressing issues 3, 4 and 5 (really just 4 and 5, since 3 goes away with removing the xlink.xsd import) I can generate the java classes using xjc.
was (Author: kstam):
Ramdom list while I'm working on this:
1. the links in the document: "For convenience, an S-RAMP XSD Model Schema xsd file is also provided at:
http://s-ramp.org/2010/specification/schemas/xsdmodel.xsd"; is not valid. They can be found here instead 'http://www.s-ramp.org/8650766/xsdmodel.xsd'
2. should the license header in the xsds include the current companies involved with s-ramp?
3. the coremodel.xsd imports:
<xsd:import namespace="http://www.w3.org/1999/xlink"; schemaLocation="http://www.w3.org/1999/xlink.xsd"/>
<xsd:import namespace="http://www.w3.org/XML/1998/namespace"; schemaLocation="http://www.w3.org/2009/01/xml.xsd"/>
however xlink.xsd imports:
<xs:import namespace="http://www.w3.org/XML/1998/namespace"; schemaLocation="http://www.w3.org/2001/xml.xsd"/>
So now we have 2 versions of xml.xsd in the mix. This confuses xsd -> code generation tools like xjc. For example xjc coremodel.xsd will output
parsing a schema...
[ERROR] 'lang' is already defined
line 87 of http://www.w3.org/2009/01/xml.xsd
[ERROR] (related to above error) the first definition appears here
line 43 of http://www.w3.org/2001/xml.xsd
[ERROR] 'space' is already defined
line 111 of http://www.w3.org/2009/01/xml.xsd
[ERROR] (related to above error) the first definition appears here
line 89 of http://www.w3.org/2001/xml.xsd
[ERROR] 'base' is already defined
line 133 of http://www.w3.org/2009/01/xml.xsd
[ERROR] (related to above error) the first definition appears here
line 113 of http://www.w3.org/2001/xml.xsd
4. When resolving that, to both using the xml.xsd from 2001, or 2009, I run into the next issue:
parsing a schema...
[ERROR] Property "Title" is already defined. Use <jaxb:property> to resolve this conflict.
line 232 of http://www.w3.org/1999/xlink.xsd
[ERROR] The following location is relevant to the above error
line 219 of http://www.w3.org/1999/xlink.xsd
[ERROR] Property "Title" is already defined. Use <jaxb:property> to resolve this conflict.
line 261 of http://www.w3.org/1999/xlink.xsd
[ERROR] The following location is relevant to the above error
line 246 of http://www.w3.org/1999/xlink.xsd
Do we even need the xlink.xsd import? I don't see it referenced.
5. The xjc wsdlmodel.xsd errors out with
parsing a schema...
[ERROR] ct-props-correct.4: Error for type 'BindingOperationInput'. Duplicate attribute uses with the same name and target namespace are specified. Name of duplicate attribute use is 'NCName'.
line 130 of file:/Users/kstam/osc/jboss/dev/s-ramp/s-ramp-api/src/main/resources/s-ramp/wsdlmodel.xsd
[ERROR] ct-props-correct.4: Error for type 'OperationInput'. Duplicate attribute uses with the same name and target namespace are specified. Name of duplicate attribute use is 'NCName'.
line 156 of file:/Users/kstam/osc/jboss/dev/s-ramp/s-ramp-api/src/main/resources/s-ramp/wsdlmodel.xsd
[ERROR] ct-props-correct.4: Error for type 'BindingOperationOutput'. Duplicate attribute uses with the same name and target namespace are specified. Name of duplicate attribute use is 'NCName'.
line 202 of file:/Users/kstam/osc/jboss/dev/s-ramp/s-ramp-api/src/main/resources/s-ramp/wsdlmodel.xsd
I'm proposing to give these attributes unique names: NCName1, NCName2 and NCName3; or something more descriptive.
After addressing issues 3, 4 and 5 (really just 4 and 5, since 3 goes away with removing the xlink.xsd import) I can generate the java classes using xjc.
> Representing Relationships
> --------------------------
>
> Key: SRAMP-1
> URL: http://tools.oasis-open.org/issues/browse/SRAMP-1
> Project: OASIS SOA Repository Artifact Model and Protocol (S-RAMP) TC
> Issue Type: Improvement
> Components: Foundation
> Affects Versions: 1.0
> Environment: N/A
> Reporter: Vincent Brunssen
> Assignee: Kurt Stam
> Fix For: 1.0
>
>
> This was Issue-001 from the contributed issues document.
> The relationships as described in the Foundation Document may or may not be able to be fully represented in schema. The relationships need to be looked in to and evaluated to make sure that all relationships defined in the foundation document and possibly the atom document can be properly described in the XML Schemas. If they can not be properly described then we may need to explore other mechanism to better model these relationships.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]