Live-sharing is a matter of BibleSync. .<br><br>I think a common transfer format for complicated book mark trees which is designed well from bottom up and could be published similarly to BibleSync would be brilliant<br><br>Peter<br><br>Sent from my mobile. Please forgive shortness, typos and weird autocorrects.<div class="quote" style="line-height: 1.5"><br><br>-------- Original Message --------<br>Subject: [sword-devel] Shared format / persistence concept for tagged verse lists (originated in thread about Versification Mapping)<br>From: Tobias Klein <contact@tklein.info><br>To: SWORD Developers' Collaboration Forum <sword-devel@crosswire.org><br>CC: <br><br><br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 5/9/20 10:08 AM, Caleb Maclennan
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAP9w9P72CXfN=_3hcV1YNB-+OaXEdL8BcAFQnU_um47QuUAyjg@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sat, May 9, 2020 at 9:45
AM Tobias Klein <<a href="mailto:contact@tklein.info">contact@tklein.info</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div>Something more realistic than a shared storage backend
would be a shared export / import format. This I think may
be worthwhile to pursue. We could simply agree on a
certain json or xml format for this.<br>
@all: Who would be interested in this in general? We could
start with tags / topical verse lists.</div>
</blockquote>
<div><br>
</div>
<div>I would.</div>
<div><br>
</div>
<div>For my tastes and potential use cases something that
split the difference between a complete live persistence and
a static import/export would be much more useful.
Specifically I would like to intervene in the middle of the
import/export process and store the dump format in version
control. If the format were carefully considered with this
use case in mind this would allow merging content from
different sources and basically providing a synchronization
mechanism. Not a live persistent connection perse, but with
a little outside setup it could be used as an
eventually-consistent sync mechanism. How much hand holding
would go into fixing merge conflicts would be dependent on
how well thought out the schema was.</div>
</div>
</div>
</blockquote>
<p><br>
"Intervene" in the middle of the import/export process - can you
eloborate a bit more on this, Caleb?<br>
<br>
To me this simply sounds like "Use Git (or whatever other SCM) as
a storage backend for text-format based tagged verse list files".<br>
<br>
Best regards,<br>
Tobias<br>
</p>
</body>
</html>
</blockquote></div>