Re: Fw: Add optional root element to schema to encourage SoC (PR#171)

Hi Guntis,

We will not add a root element to our schema.  One can
simply define one's own envelope element in any namespace except ours,
and that element becomes a mini-host language.

Regards,

Nick Van den Bleeken


> This is a multipart message in MIME format.
> --=_alternative 006D01A788257329_=
> Content-Type: text/plain; charset="US-ASCII"
> 
> John M. Boyer, Ph.D.
> STSM: Lotus Forms Architect and Researcher
> Chair, W3C Forms Working Group
> Workplace, Portal and Collaboration Software
> IBM Victoria Software Lab
> E-Mail: boyerj@ca.ibm.com 
> 
> Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer
> 
> 
> ----- Forwarded by John Boyer/CanWest/IBM on 07/31/2007 12:49 PM -----
> 
> Guntis Ozols <guntiso@latnet.lv> 
> Sent by: www-forms-editor-request@w3.org
> 07/08/2007 04:30 AM
> 
> To
> www-forms-editor@w3.org
> cc
> 
> Subject
> Add optional root element to schema to encourage SoC
> 
> 
> 
> 
> 
> 
> 
> Xml requires root element and xforms schema does not define any,
> thus encouraging to tangle form with host language.
> 
> At the moment, xforms are otherwise quite self sufficient.
> 
> With root element, forms could be built, tested,
> and stored as valid xml without any irrelevant host language,
> then combined with separately managed host language
> representation(s) (styles) for these forms.
> 
> PS. Please refer me to convincing info why keep current
>       restriction if I do not know what I am talking about.
> 
> Guntis
> 
> 
> 
> --=_alternative 006D01A788257329_=
> Content-Type: text/html; charset="US-ASCII"
> 
> 
> <br><font size=2 face="sans-serif">John M. Boyer, Ph.D.<br>
> STSM: Lotus Forms Architect and Researcher<br>
> Chair, W3C Forms Working Group<br>
> Workplace, Portal and Collaboration Software<br>
> IBM Victoria Software Lab<br>
> E-Mail: boyerj@ca.ibm.com  <br>
> <br>
> Blog: </font><a href=http://www.ibm.com/developerworks/blogs/page/JohnBoyer><font
> size=2 face="sans-serif">http://www.ibm.com/developerworks/blogs/page/JohnBoyer</font></a><font
> size=2 face="sans-serif"><br>
> <br>
> </font>
> <br><font size=1 color=#800080 face="sans-serif">----- Forwarded by John
> Boyer/CanWest/IBM on 07/31/2007 12:49 PM -----</font>
> <br>
> <table width=100%>
> <tr valign=top>
> <td width=40%><font size=1 face="sans-serif"><b>Guntis Ozols
> <guntiso@latnet.lv></b>
> </font>
> <br><font size=1 face="sans-serif">Sent by:
> www-forms-editor-request@w3.org</font>
> <p><font size=1 face="sans-serif">07/08/2007 04:30 AM</font>
> <td width=59%>
> <table width=100%>
> <tr valign=top>
> <td>
> <div align=right><font size=1 face="sans-serif">To</font></div>
> <td><font size=1 face="sans-serif">www-forms-editor@w3.org</font>
> <tr valign=top>
> <td>
> <div align=right><font size=1 face="sans-serif">cc</font></div>
> <td>
> <tr valign=top>
> <td>
> <div align=right><font size=1 face="sans-serif">Subject</font></div>
> <td><font size=1 face="sans-serif">Add optional root element to schema
> to encourage SoC</font></table>
> <br>
> <table>
> <tr valign=top>
> <td>
> <td></table>
> <br></table>
> <br>
> <br>
> <br><tt><font size=2><br>
> Xml requires root element and xforms schema does not define any,<br>
> thus encouraging to tangle form with host language.<br>
> <br>
> At the moment, xforms are otherwise quite self sufficient.<br>
> <br>
> With root element, forms could be built, tested,<br>
> and stored as valid xml without any irrelevant host language,<br>
> then combined with separately managed host language<br>
> representation(s) (styles) for these forms.<br>
> <br>
> PS. Please refer me to convincing info why keep current<br>
>       restriction if I do not know what I am talking about.<br>
> <br>
> Guntis<br>
> <br>
> <br>
> </font></tt>
> --=_alternative 006D01A788257329_=--
> 
>

Received on Wednesday, 12 September 2007 11:10:21 UTC