in reply to Re^7: Native newline encoding
in thread Native newline encoding

Note that the passage you quoted does not appear anywhere in the spec.

XML has aspects of a binary format. Specifically, the encoding can't be changed. That's why it must be passed to a parser undecoded and why it has the MIME type of a binary format (application/).

It also has aspects of a text format. Specifically, the ability to be read and edited by humans with nothing but basic tools.

Considering neither "text format" nor "binary format" are actually defined, it's silly to debate without first putting out definitions.

Replies are listed 'Best First'.
Re^9: Native newline encoding
by BrowserUk (Patriarch) on May 30, 2012 at 00:48 UTC
    Note that the passage you quoted does not appear anywhere in the spec.

    Que? If you follow the link behind the quoted passage, the very first line of the very first paragraph is word for word what I quoted.

    it's silly to debate

    Then let's not huh.

    This pointless discussion has gone far enough already due to a rabid dog with a bruised ego. There's no point in your adding to the fray further is there.

    With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.

    The start of some sanity?
[reply]

      Que? If you follow the link behind the quoted passage, the very first line of the very first paragraph is word for word what I quoted.

      I said "the passage you quoted does not appear anywhere in the spec", emphasis added.

      And by "the passage", I really meant any reference to being a text format at all.

[reply]
        I said "the passage you quoted does not appear anywhere in the spec", emphasis added.

        I see. So you just popped up to tell me that the text I quoted from one (linked)document, doesn't appear in some other (unreferenced) document?

        Sound!

        And by "the passage", I really meant any reference to being a text format at all.

        Really? Then I guess you missed section "2.2 Characters" of "the spec": That I both linked and quoted elsewhere. 

        2.2 Characters

[Definition: A parsed entity contains text, a sequence of characters, 
+which may represent markup or character data.] [Definition: A charact
+er is an atomic unit of text as specified by ISO/IEC 10646:2000 [ISO/
+IEC 10646]. Legal characters are tab, carriage return, line feed, and
+ the legal characters of Unicode and ISO/IEC 10646. The versions of t
+hese standards cited in A.1 Normative References were current at the 
+time this document was prepared. New characters may be added to these
+ standards by amendments or new editions. Consequently, XML processor
+s MUST accept any character in the range specified for Char. ]

        [download]
        With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
        Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
        "Science is about questioning the status quo. Questioning authority".
        In the absence of evidence, opinion is indistinguishable from prejudice.

        The start of some sanity?
[reply]
[d/l]

In Section Seekers of Perl Wisdom