OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   RE: Restriction on PI information

[ Lists Home | Date Index | Thread Index ]
  • From: David Seibert <dseibert@sqwest.bc.ca>
  • To: "xml-dev@ic.ac.uk" <xml-dev@ic.ac.uk>, "'Eric Baatz - Sun Microsystems Labs BOS'" <ebaatz@barbaresco.East.Sun.COM>
  • Date: Mon, 24 Mar 1997 10:53:07 -0800

The simplest alternative is to encode your data (with any encoding
that won't produce the character "?"), insert it in a PI, and decode
it at the other end.  This is probably also the most reliable way to
solve this problem.  If there were two ways to terminate a PI,
what would your aplication do with data that contained both
terminators?

Regards,

David

----------
From: 	Eric Baatz - Sun Microsystems Labs BOS
Sent: 	Monday, March 24, 1997 6:55 AM
To: 	xml-dev@ic.ac.uk
Cc: 	ebaatz@barbaresco.East.Sun.COM
Subject: 	Restriction on PI information

My application of XML is to markup text that is to be spoken by
speech synthesizers.  To my naive mind (I'm very new to SGML
and XML), a PI seems to be the right construct for passing
native information to a speech synthesizers, that is, instructions
in their proprietary, already existing, command set.  As I don't
have any control over the syntax of the commands I want to
pass through, I want a PI to allow the widest latitude in
the information it can handle.  The syntax in the draft doesn't
seem to allow that.

What is the rationale for the data that a PI allows?
What mechanisms can be used to make that data as arbitrary
as possible without changing the draft?

My take on the PI syntax is that the data needs to avoid
looking like the end of a PI.  Two different ways of ending
a PI (somewhat like the use of double or single quotes for
quoted data) would allow a way of getting unpalatable data
through (my program would have to generate the appropriate
one depending on what my data looked like).  Allowing a CDATA
section, would also seem to allow quoting of otherwise
unpalatable data.

Clearly, any changes from the draft would complicate the parsing.

Eric Baatz
Sun Microsystems Laboratories
2 Elizabeth Drive, MS UCHL03-207                 (508) 442-0257
Chelmsford, MA 01824                        fax: (508) 250-5067
USA                                    Internet: eric.baatz@east.sun.com


xml-dev: A list for W3C XML Developers
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To unsubscribe, send to majordomo@ic.ac.uk the following message;
unsubscribe xml-dev
List coordinator, Henry Rzepa (rzepa@ic.ac.uk)




xml-dev: A list for W3C XML Developers
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To unsubscribe, send to majordomo@ic.ac.uk the following message;
unsubscribe xml-dev
List coordinator, Henry Rzepa (rzepa@ic.ac.uk)





 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS