Is there a constraints faq anywhere?

Dear All @www.forms,

We are introducing Xforms into our tooling & have constructed an easy to
use way of doing so via a tomcat/war+ chiba set up.

We would like people in the business (vs us architect types) to be able
to construct Xforms easily etc.

The sole remaining sticking point appears to be wrt constraints on
fields/bindings where there appears to be no real easy examples/FAQ out
on the net anywhere. It takes me quite a while to do & I have had some
complaints wrt others (more business types) doing so.

E.g.

An example:

I have a list of all our current OIDs (Object ID's) which must be
unique. 

I have a backing instance which simply consists of nodes holding these
values e.g.:

<root>
<comp_OID >1.2.826.0.1285.0</comp_OID>
<comp_OID >1.2.826.0.1285.0.1.10</comp_OID>
<comp_OID >1.2.826.0.1285.0.2.0.65</comp_OID>
Etc.etc.
</root>


The field itself in the main instance will be constructed via:

<xforms:bind nodeset="comp_OID"
calculate="concat(../ISO_Root/text(),'.', ../OID_suffix/text())" />

So I want to say in essence "where the calculated comp_OID is not in
instance('All_comp_OID')//comp_OID.text()"


Equally we have another requirement to set readonly attributes dependant
upon values i.e. "if this vocabulary is "live" or has been "live" (by
live date) then it can not be changed & all fields must be marked read
only"


So 
(A) I am wondering if anyone has solutions to the above but 
(B) I am wondering if anywhere there is a wiki/faq for constraints &
other Xforms "tips & tricks" where examples can be placed. I have
noticed that time after time people (including myself) have asked fairly
std questions to which people here can easily & rapidly create solutions
for (e.g. the above constraints) but then the solutions get lost & a
while later someone asks a similar question again e.g. "to set a field
to be read only as a result of the value carried in another
field/node/attribute then......."

TIA


Adam



This e-mail is confidential and privileged. If you are not the intended recipient please accept our apologies; please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Please inform us that this message has gone astray before deleting it. Thank you for your co-operation.

Received on Monday, 19 June 2006 08:43:13 UTC