On Thu, 13 Mar 2003 15:33:52 -0800 Ronald Bourret <[EMAIL PROTECTED]> wrote:
> I'm not sure what the procedure is for changing the working draft. A > simple vote is OK with me. Hi Jeroen, Ronald. I don't know the current status in detail but if you think it is necessary to change the WD then go ahead. :o) Any help is welcome and I will assist you guys where I can ... Regards, Lars > Do you need to worry about backwards compatibility with either the > whitespace rules or disallowing insert-before/after with attributes? > > -- Ron > > Jeroen Breedveld wrote: > > || First, I agree with you about not allowing the target of an > > || insert-before or insert-after to be an attribute. This > > || makes a lot of sense. > > > > Ok, let's change it in the WD. Should we vote on that in this > > mailinglist? > > > > || That said, it seems reasonable to use the whitespace rules (section > > || 3.7.3) from XQuery in XUpdate, since both are solving the > > || same problem. These basically state that whether > > || uninterrupted whitespace between constructors is preserved > > || is controlled by an option in the query header. (XUpdate > > || could add an attribute to the modifications element.) > > || Whitespace within constructors is always preserved. > > > > If we disallow attribute elements in insert-before(-after) operations an > > immediate problem with whitespaces is solved but they're still > > cumbersome so introducing a scheme such as the one from XQuery seems > > like a good idea in my opinion. > > > > || In XUpdate terms, whitespace inside the attribute, text, > > || processing-instruction, and comment elements is always > > || preserved. Whitespace in an element constructor is > > || preserved if (a) the option to preserve whitespace is set > > || to true (preserve, etc.) or (b) the whitespace is broken by > > || mixed content. > > > > Seems like a good, straightforward solution to me > > > > || The only difficulty here is how to handle attribute > > || children of an element element. For example, it is not > > || clear what to do with: > > || > > || <xupdate:append select="/addresses" child="last()"> > > || <xupdate:element name="address"> > > || 192 Sylvan Way > > || <xupdate:attribute name="type">street</xupdate:attribute> > > || </xupdate:element> > > || </xupdate:append> > > || > > || The easiest solution is to simply extract the attribute > > || element, leave all the remaining whitespace, and then deal > > || with it according to the above rules. > > > > I agree with that. > ---------------------------------------------------------------------- > Post a message: mailto:[EMAIL PROTECTED] > Unsubscribe: mailto:[EMAIL PROTECTED] > Contact administrator: mailto:[EMAIL PROTECTED] > Read archived messages: http://archive.xmldb.org/ > ---------------------------------------------------------------------- -- ______________________________________________________________________ Lars Martin mailto:[EMAIL PROTECTED] SMB GmbH http://www.smb-tec.com D-04347 Leipzig Rohrteichstrasse 18 Tel: +49-(0)341-699 46 04 Fax: +49-(0)341-699 47 04 Product Management BusinessServer BS1 ---------------------------------------------------------------------- Post a message: mailto:[EMAIL PROTECTED] Unsubscribe: mailto:[EMAIL PROTECTED] Contact administrator: mailto:[EMAIL PROTECTED] Read archived messages: http://archive.xmldb.org/ ----------------------------------------------------------------------
