[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Separating request and content
When looking at the request schema I could not find a good
place for the existing ResourceContent context element. Adding schema
restrictions for a particular context attribute category seems to be not a very
elegant solution.In any case – existing way to provide an arbitrary XML
context document inside an element of “any” type does not seem to
be optimal. What I want to suggest, and to discuss tomorrow:
i.
In this case you can not use the
AttributeSelector to select individual attribute values, but that would be
redundant to AttributeDesignator anyway. An alternative would be to
have two reserved URI – for the request, and for the submitted document.
So the main point is to replace the
existing ResourceContent with a separate document, and to allow
AttributeSelector to identify document uri, with default behavior remaining the
same it is now. Could this be added to tomorrow’s
agenda? Daniel; _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]