OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-dev message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: [ebxml-dev] Discrepancy between ebRIM v.2.1 schema and specs


Hi all.

I was looking through version 2.1 of the ebRIM, both the rim.xsd schema
(http://www.oasis-open.org/committees/regrep/documents/2.1/schema/rim.xsd)
and the specs
(https://www.oasis-open.org/committees/regrep/documents/2.1/specs/ebrim_v2.1
.pdf). On the UML diagram on page 11 of the spec, it would seem that a
ServiceBinding is required to have at least ONE SpecificationLink
(multiplicity 1..*). However, according to the schema,

<schemaSnippet>

    <complexType name="ServiceBindingType">
        <complexContent>
            <extension base="tns:RegistryObjectType">
                <sequence>
                    <element ref="tns:SpecificationLink" minOccurs="0"
maxOccurs="unbounded" />
                </sequence>
            <attribute name="service" use="optional" type="IDREF" />
            <attribute name="accessURI" use="optional" type="anyURI" />
            <attribute name="targetBinding" use="optional" type="IDREF" />
            </extension>
        </complexContent>
      </complexType>

</schemaSnippet>

the SpecificationLink is not required. Am I reading something wrong, or is
there an error in either the spec or schema?

Thanks.

Wes



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help


Powered by eList eXpress LLC