[eml-dev] [Bug 1132] - fix access control rule ambiguities
bugzilla-daemon at ecoinformatics.org
bugzilla-daemon at ecoinformatics.org
Thu Nov 13 17:09:29 PST 2008
http://bugzilla.ecoinformatics.org/show_bug.cgi?id=1132
------- Comment #14 from mob at icess.ucsb.edu 2008-11-13 17:09 -------
The physicalDistributionType should have looked like this (below), so that if
the references element is used, it is the only child of <distribution>. I
wrongly used the sequence model, which meant that <references> could have had
an <access> sibling. This has been checked into cvs as rev 1.75
<xs:complexType name="PhysicalDistributionType">
<xs:annotation>
<xs:appinfo>
<doc:tooltip>this type specifically for physical
connections.</doc:tooltip>
</xs:appinfo>
</xs:annotation>
<xs:choice>
<xs:sequence>
<xs:choice>
<xs:element name="online" type="PhysicalOnlineType"/>
<xs:element name="offline" type="res:OfflineType"/>
<xs:element name="inline" type="res:InlineType"/>
</xs:choice>
<xs:element name="access" type="acc:AccessType" minOccurs="0"/>
</xs:sequence>
<xs:group ref="res:ReferencesGroup"/>
</xs:choice>
<xs:attribute name="id" type="res:IDType" use="optional"/>
<xs:attribute name="system" type="res:SystemType" use="optional"/>
<xs:attribute name="scope" type="res:ScopeType" use="optional"
default="document"/>
</xs:complexType>
More information about the Eml-dev
mailing list