Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Another multi-field key question

From: Kasimier Buchcik <kbuchcik@---------.-->
To: Jim Stanley <JimS@--------------.--->
Date: 12/14/2004 6:20:00 PM
Hi,

Kasimier Buchcik wrote:
> 
> Hi,
> 
> Jim Stanley wrote:
> 
>> Just when I think I understand all this key/keyref stuff, another
>> conundrum arises:
>>
>> I have "categories" under my root, each with one or more "property
>> definitions" consisting of name-value pairs.   Several of my categories
>> have duplicate property definitions, something like below:
>>

> I don't see a way to do this, since you want only the _first_ 'propDef'
> child element of the 'category' element to be used as a field. This is

Correction: "the _first_ 'propDef' child element of the 'category' 
element to be used in the XPath of the field"

> not expressible by the reduced XPath syntax of the indentity-constraint
> mechanism. In your example the XPath 'propDef/name' resolves to multiple
> nodes, which is not allowed. What you would need, would be
> 'propDef/name[1]' - unfortunately not supported.

Correction: this should be "propDef[1]/name"

Kasimier



From mike@s... Thu Dec 16 00:18:37 2004
Received: from lisa.w3.org ([


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent