[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: An unclear point with W3C XML 1.0 Specification

• To: collin@w...
• Subject: Re: An unclear point with W3C XML 1.0 Specification
• From: david.lyon@c...
• Date: Thu, 6 Jan 2005 15:46:32 +1100
• Cc: xml-dev@l...
• In-reply-to: <20050106042113.CF2B828C04D@m...>
• References: <20050106042113.CF2B828C04D@m...>
• User-agent: Internet Messaging Program (IMP) 3.2.6

Hi Collin,

If you are talking about the traditional xml spec I may
not be the best person to explain it.

However what we do with our string literals is "properly"
escape them. That is, have a scheme to embed double quotations
and other noxious characters in a way that doesn't cause a
problem to the parser.

It happens all the time, especially with power tools. eg:

 <product_item>
   part_description&="3 1/2^" Spanner"
 </product_item>

What we do, is use the ^ character to escape. But there
may be other preferences.

So after reading out the value, what is returned is:

 3 1/2" Spanner

It's pretty simple but works without hiccups.

Best Regards

David
Sydney, Australia

Quoting Collin Hsu <collin@w...>:

> {{ //2.3 Common Syntactic Constructs, XML 1.0 Third Edition
> //http://www.w3.org/TR/2004/REC-xml-20040204/#sec-common-syn
>
> Literal data is any quoted string not containing the quotation mark used as
> a delimiter for that string. Literals are used for specifying the content of
> internal entities (EntityValue), the values of attributes (AttValue), and
> external identifiers (SystemLiteral). ___Note that a SystemLiteral can be
> parsed without scanning for markup.___
>
> }}
>
>
> I wonder what the last sentence really wants to say.
>
> I think I must have missed certain backgroud knowledge about it.
>
> Could you give me some explanation ?
>
> Thank you!
>
>
> Collin
>




----------------------------------------------------------------

• Follow-Ups:
  • Re: An unclear point with W3C XML 1.0 Specification
    • From: Ronald Bourret <rpbourret@r...>

• References:
  • An unclear point with W3C XML 1.0 Specification
    • From: "Collin Hsu" <collin@w...>

• Prev by Date: An unclear point with W3C XML 1.0 Specification
• Next by Date: Re: An unclear point with W3C XML 1.0 Specification
• Previous by thread: An unclear point with W3C XML 1.0 Specification
• Next by thread: Re: An unclear point with W3C XML 1.0 Specification
• Index(es):
  • Date
  • Thread