[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=24894#action_24894 ]
Andrei Shakirin edited comment on SRAMP-1 at 3/20/11 8:36 AM:
--------------------------------------------------------------
I have checked validity of all schemas and tried to generate java code using JAXB 2.0.
Issue 3, 4: import of xlink.xsd in coremodel.xsd causes mixed versions of xml.xsd
Proposed fix: remove xlink.xsd import from coremodel.xsd
Issue 5: Duplicated definition of NCName attribute in OperationInput, BindingOperationInput, BindingOperationOutput types (wsdlmodel.xsd).
Attribute with NCName is already defined in parent type NamedWsdlDerivedArtifactType.
Proposed fix: change attributes name in the same way as for OperationOutput (outputNCName):
a) OperationInput: NCName -> inputNCName
b) BindingOperationInput: NCName -> bindingInputNCName
c) BindingOperationOuput: NCName -> bindingOutputNCName
After these two updates schemas are valid and JAXB compilable.
One more thought: is there any reason to import xml.xsd in coremodel schema? I cannot find any refernece to "http://www.w3.org/XML/1998/namespace";.
All schemas are valid without this import.
was (Author: ashakirin):
I have checked validity of all schemas and tried to generate java code using JAXB 2.0.
Issue 3, 4: import of xlink.xsd in coremodel.xsd causes mixed versions of xml.xsd
Proposed fix: remove xlink.xsd import from coremodel.xsd
Issue 5: Duplicated definition of NCName attribute in OperationInput, BindingOperationInput, BindingOperationOutput types (wsdlmodel.xsd).
Attribute with NCName is already defined in parent type NamedWsdlDerivedArtifactType.
Proposed fix: change attributes name in the same way as for OperationOutput (outputNCName):
a) OperationInput: NCName -> inputNCName
b) BindingOperationInput: NCName -> bindingInputNCName
c) BindingOperationOuput: NCName -> bindingOutputNCName
After this two updates schemas are valid and JAXB compilable.
One more thought: is there any reason to import xml.xsd in coremodel schema? I cannot find any refernece to "http://www.w3.org/XML/1998/namespace";.
All schemas are valid without this import.
> 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]