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

RE: Strong Typing in SGML and XML

  • From: Andrew Layman <andrewl@m...>
  • To: "xml-dev Mailing List (E-mail)" <xml-dev@i...>
  • Date: Thu, 8 May 1997 11:05:50 -0700

strong typing readability
I accidently sent this message before completing it.  The full message
is here:


> Several people have written in recently asking, in effect, "What are
> the
> purposes of this strong typing?  What needs does it solve?"  So I
> asked
> around.  Here are the needs that have been cited:
> 
> 1.	Storage optimization.  Various clients want to be able to
> optimize storage by keeping numbers in a binary format, strings in a
> preallocated structure, etc.
> 
> 2.	Implied semantics.  E.g. numbers can be added together, if you
> know they are numbers. Also, knowing that a number is meant to have a
> fixed versus floating precision affects how operations are performed,
> what kind of precision is retained during calculations, what errors
> are
> reported, etc. Knowing that a string is meant to be a 
> URL gives hints on its use. Etc. 
> 
> 3.	Parsing and formatting rules. Dates are expected to be in some
> standard representation, such as given by ISO 8601 (e.g.).  Floating
> point numbers permit scientific notation. Etc. For example,   
> though the number "0.1234E+20" could have been represented as 
> "<mantissa>1234</mantissa><exponent>20</exponent>", and the date
> "19970508T10:47" could have been similarly broken into year, month,
> etc.,
> and this markup would eliminate the need for special parsers for
> numbers and
> dates, it has obvious readability and bloat problems.
> An explicit data type can signal what the internal elements are and
> how
> to parse for them without tags. 
> 
> 4.	Different data types need different supplementary attributes,
> such as number of digits precision, total size in characters, whether
> time zones are present, etc.  (In Tim's proposal, these all overload a
> single, generic attribute.)
> 
> 5.	Range restrictions. Dates and other kinds of things measured in
> numbers can be limited to a range of values.  All types can be
> potentially limited to a set of descrete values (by enumeration or
> rule). For example, an attribute expressing a color
> in terms of wavelength could be limited to 400..700 (nanometers). An
> attribute listing a US egg size could be limited to be among
> "medium," "large," "extra large" and "jumbo." If represented
> numerically,
> it could be limited to "1," "2," "3" and "4."  
> 
> 6.	Passthrough. Sometimes XML is a carrier syntax between systems
> where some participants need to convey implications not covered in
> points 
> 1 through 5 above. For example, a database may make a distinction 
> between CHAR and VARCHAR even though other readers of a document
> don't.
> 
> 
> 

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


PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.