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

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   Re: [xml-dev] Non XML syntaxes

[ Lists Home | Date Index | Thread Index ]

Rick Jelliffe scripsit:

> http://www.idealliance.org/papers/extreme02/html/2002/Rosenblum01/EML2002Rosenblum01.html
> has a survey of technical publishing companies, and how they do
> equations.

I think this passage highly relevant to the Walter Perry vs. Everyone Else
meta-thread:

# 5.5 Transformation Location
# 
# Highwire encourages customers to deliver content in the Highwire DTD,
# but they cannot require publishers who have their own DTD to deliver in
# Highwire format. When a DTD transformation is required, Highwire does the
# transformation, rather than the publisher, for several important reasons:
# 
#    1. Publishers may not want to switch to the Highwire DTD as their
#    primary DTD because they use their SGML for additional purposes.
#    2. Most publishers are not interested in bearing the burden or expense
#    of creating SGML in a second DTD.
#    3. Highwire charges publishers a fee associated with setup of the
#    transformation to the Highwire DTD; however, this fee is less than
#    the cost of having the publisher build or buy a system to convert
#    the SGML themselves. It costs Highwire less than other organizations
#    to build this transformation because:
#        a. They are familiar with their own DTD
#        b. They can reuse pieces of other transformations (e.g., regular
#           expression pattern matching to identify linking elements)
#        c. They know the mission of their transformation intimately, and
#           can create the most efficient transformation to achieve
#           exactly that mission.
#    4. Highwire has greater control over the quality of the transformation
#    if they do it rather than someone else. Highwire uses a small team to
#    create software-driven transformations. By using a small team under
#    one roof, there is likely to be less variance in the SGML created
#    ("fewer hands, fewer errors"), allowing for a smoother flow of the
#    resulting SGML into Highwire's online presentation systems.
# 
# While there are many advantages to converting SGML at Highwire rather than
# at the publisher, there is one significant disadvantage: if a publisher
# significantly upgrades their DTD, a full-fledged parser update, coupled
# with extensive integrity testing, is required at Highwire.
# 
# Communication of DTD upgrades to Highwire, whether major or minor,
# is critical. In many cases, Highwire has only learned of a DTD upgrade
# through the failure of a file to parse, rather than through proactive
# communication from a publisher.

-- 
A mosquito cried out in his pain,               John Cowan
"A chemist has poisoned my brain!"              http://www.ccil.org/~cowan
        The cause of his sorrow                 http://www.reutershealth.com
        Was para-dichloro-                      jcowan@reutershealth.com
Diphenyltrichloroethane.                                (aka DDT)




 

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

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