Re: [teiid-dev] VDB Data Policy structure
On Jul 19, 2010, at 7:23 AM, Barry Lafond wrote:
<permission>
<resource-name>HROracleAllView.Management.Payroll</resource-name>
<allow-create>FALSE</allow-create>
<allow-read>TRUE</allow-read>
<allow-update>FALSE</allow-update>
<allow-delete>FALSE</allow-delete>
</permission>
<xs:element name="permission" minOccurs="1"
maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="resource-name"
type="xs:string"/>
<xs:element name="allow-create"
type="xs:boolean" minOccurs="0"/>
<xs:element name="allow-read"
type="xs:boolean" minOccurs="0"/>
<xs:element name="allow-update"
type="xs:boolean" minOccurs="0"/>
<xs:element name="allow-delete"
type="xs:boolean" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:element>
One minor thing I'd point out: Since these are Boolean values (and the schema has
already defined them as optional), the schema should also provide a default value for each
of the "allow" elements, and the vdb.xml should therefore not include entries
that match the default.
JPAV
Attachments:
- attachment.html (text/html — 5.5 KB)