• From: "William Gilreath" <wgilreath@g...>
• To: "Melvin Chin" <mc@s...>, will@w...
• Date: Sun, 15 Oct 2006 02:55:59 -0500

I agree with you that a conversion must be 1:1 for XString to be XML.
In this case, it is a glitch, that in (if any) future release must be
corrected to ensure a complete 1:1 translation.

Thanks for the thought!

Will Gilreath


On 10/8/06, Melvin Chin <mc@s...> wrote:
> At 03:54 AM 2006-10-07 -0500, William Gilreath wrote:
> >The five major points about XString:
> >
> >XString is XML just encoded differently.
>
> Thank you for another attempt at refining XML.  I'm always curious to
> see how others find another aspect to refine XML in different aspects.
> I don't know if I may be "picking bones" from the words, but I'm not
> sure this particular line (above) could be said without qualification.
>
> It would read like XML is an abstract definition, with the actual rendition
> and encoding being arbitrarily decided by possibly one or more other
> specifications, so that XString could be "XML just encoded differently".
>
> Well, that's not really it since we can't run away from all the uses of
> "<", ">" and the many reserved tokens and combinations;  the XML
> spec requires these to be used in order to call a data instance XML.
>
> Second, it would also be, I believe, a necessary condition that XString
> is either a one-to-one mapping of all XML aspects, or at least a superset,
> before "XString is XML" could be said.
>
> In your example (below), had the parsing of the XML original be within
> a mixed element and text environment, then the newlines that were lost
> in translation to XString would make the XString rendition incompatible
> with the original XML instance.
>
> Any thoughts?
>
>
>
>
>
> cheers.
>
>
>
> >Quick-and-dirty example of XML and XString:
> >
> ><?xml version="1.0" encoding="ISO-8859-1"?>
> ><duh:ROOT ATTRIBUTE="VALUE"
> >xmlns:duh="<http://www.w3.org/noduh>http://www.w3.org/noduh">
> >    <duh:CHILD>text</duh:CHILD>
> >    <duh:EMPTY EMPTY_ATTRIBUTE/>
> >    <!--comment-->
> >    <?processing instruction?>
> >    <![CDATA[function nop(){}]]>
> >    <duh:NIL></duh:NIL>
> ></duh:ROOT>
> >
> >XString = /duh:ROOT+7@ATTRIBUTE=VALUE@xmlns:duh=
> >http://www.w3.org/noduh/duh:CHILD+1'text/duh:EMPTY+0@EMPTY_ATTRIBUTE-comment?processing
> >instruction[function nop(){}/duh:NIL+0
> >
> >
> >Cheers! My best,
> >
> >Will Gilreath
> ><mailto:wgilreath@g...>wgilreath@g...
> ><mailto:will@w...>will@w...
>
>
>
> _______________________________________________________________________
>
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@l...
> subscribe: xml-dev-subscribe@l...
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>
>

• References:
  • Re: Announcing a Preview of XString, an XML technology - XML as a String
    • From: Melvin Chin <mc@S...>