Not off-topic: Wrong couple divorced after computer error by law firm Vardag's

Fri Apr 19 23:30:33 CEST 2024

@mike
The XML encodes the text (narrative, math, tables) in a way that is format
independent and future proof. It could be JSON too but XML is far more
popular. It is not normally viewed directly and simply used to convert
automatically to other visible formats.

The figures are normally not encoded but kept separate and linked to the
XML.

@Paulo De Souza <pauloney at gmail.com>
The XML is simply to hold the content in a device and format independent
way. To view the content paginated, the XML can be converted to TeX on the
fly and typeset. Conversion between XML and TeX is pretty straightforward.

On Fri, 19 Apr 2024 at 19:13, Paulo Ney de Souza <pauloney at gmail.com> wrote:

> XML is obviously the choice for archival format for journals, where one is
> highly concerned with verification, recreation of experiments, re-use of
> the material, etc. and where there is little concern for fine typography.
> To carry that into situations where typography matters is literally
> impossible or extremely cumbersome and expensive.
>
> You can just open an Elsevier journal to see the most modern example of
> poor typography there is, and this is really the divisor. Archival of TeX,
> in the absolute sense of the word in unachievable, but manageable for low
> volume print that matters.
>
> Paulo Ney
>
>
>
> On Fri, Apr 19, 2024 at 9:25 AM Mike Marchywka <marchywka at hotmail.com>
> wrote:
>
>> The question is if you are archiving images or information.
>> Computer readable is more portable but yo may also want to
>> know what the original audience saw. Unless the author
>> wrote in XML, its not even sure that is what he meant.
>>
>> I hate XML since it is so verbose its not human comprehendable lol.
>> A formatted JSON is probably easier :)
>>
>>  Mike Marchywka
>> 44 Crosscreek Trail
>> Jasper GA 30143
>> was 306 Charles Cox Drive  Canton, GA 30115
>> 470-758-0799
>> 404-788-1216
>>
>>
>>
>>
>> ________________________________________
>> From: Kaveh Bazargan <kaveh at rivervalley.io>
>> Sent: Friday, April 19, 2024 10:36 AM
>> To: Norbert Preining
>> Cc: Mike Marchywka; Jonathan Fine; TeXhax
>> Subject: Re: Not off-topic: Wrong couple divorced after computer error by
>> law firm Vardag's
>>
>> My preference is XML as source. The DTD is not that important. JATS is
>> not perfect but it is well embedded in publishing now so hard to change.
>>
>> For at least 20 years the big publishers have specified "XML first". We
>> took it as automated XML to any other format (inc PDF). It's not easy,
>> especially if you want good pagination. But worth it in the long run.
>>
>> Of course there is good XML and bad XML. e.g. JATS allows "mixed
>> citation" that can be any text as well as "element citation". The latter is
>> fully structured, but harder to format (e.g. automatic formatting on the
>> fly. To get around this some publications have element as well as mixed for
>> each reference. Then you are back to square one, where there is no format
>> of record even within the XML!!!
>>
>> On Fri, 19 Apr 2024 at 15:25, Norbert Preining <norbert at preining.info
>> <mailto:norbert at preining.info>> wrote:
>> Hi Kaveh,
>>
>> On Fri, 19 Apr 2024, Kaveh Bazargan wrote:
>> > Agree. I have suggested <https://rivervalley.io/format-of-record/> XML
>> >
>> > There is an unfortunate trend right now to use HTML. I think it is best
>> for
>> > accessibility but the source should be XML.
>>
>> Agreed here. While HTML is best for accessibility due to the huge amount
>> of support (plugins, screen readers, ...), as core format XML (but then,
>> what, JATS?) is strongly prefered.
>>
>> That is also what some publishing houses are doing.
>>
>> Best regards
>>
>> Norbert
>>
>> --
>> PREINING Norbert                              https://www.preining.info
>> arXiv / Cornell University   +   IFMGA Guide   +   TU Wien  +  TeX Live
>> GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
>>
>>
>> --
>> Kaveh Bazargan PhD
>> Director
>> River Valley Technologies<http://rivervalley.io> ● Twitter<
>> https://twitter.com/rivervalley1000> ● LinkedIn<
>> https://www.linkedin.com/in/bazargankaveh/> ● ORCID<
>> https://orcid.org/0000-0002-1414-9098> ● @kaveh1000 at mastodon.social<
>> https://mastodon.social/@kaveh1000>
>> Accelerating the Communication of Research
>> [
>> https://ci3.googleusercontent.com/mail-sig/AIorK4x6Tw-4HXUOqdFuM6mWVAGySN-mFQEL-30Loo-79MQpz5RCsGp3shdEl0OZ_KhStIgAjuMjf70
>> ]<
>> https://www.linkedin.com/posts/bazargankaveh_ismte-innovation-award-recipient-kaveh-bazargan-activity-7039348552526921728-XAEB/?utm_source=share&utm_medium=member_desktop>
>> [
>> https://rivervalley.io/gigabyte-wins-the-alpsp-scholarly-publishing-innovation-award-using-river-valleys-publishing-technology/]
>> <
>> https://rivervalley.io/gigabyte-wins-the-alpsp-scholarly-publishing-innovation-award-using-river-valleys-publishing-technology/
>> >
>>
>>

-- 
Kaveh Bazargan PhD
Director
River Valley Technologies <http://rivervalley.io> ● Twitter
<https://twitter.com/rivervalley1000> ● LinkedIn
<https://www.linkedin.com/in/bazargankaveh/> ● ORCID
<https://orcid.org/0000-0002-1414-9098> ● @kaveh1000 at mastodon.social
<https://mastodon.social/@kaveh1000>
*Accelerating the Communication of Research*

*
<https://www.linkedin.com/posts/bazargankaveh_ismte-innovation-award-recipient-kaveh-bazargan-activity-7039348552526921728-XAEB/?utm_source=share&utm_medium=member_desktop>
 [image:
https://rivervalley.io/gigabyte-wins-the-alpsp-scholarly-publishing-innovation-award-using-river-valleys-publishing-technology/]
<https://rivervalley.io/gigabyte-wins-the-alpsp-scholarly-publishing-innovation-award-using-river-valleys-publishing-technology/>*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://tug.org/pipermail/texhax/attachments/20240419/5cca204e/attachment.htm>