From: Markus Elfring <Markus.Elfring@web.de>
To: Yuval Adam <yuv.adm@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Maintaining historical outlines
Date: Tue, 03 Apr 2012 21:45:11 +0200 [thread overview]
Message-ID: <4F7B5347.3010701@web.de> (raw)
In-Reply-To: <CA+P+rLcWT0SZQjW2LtFXXCDRwjMp8daJ2hVup=7cnsRGbKw7xw@mail.gmail.com>
> Our use case for this is like so:
> "ok, this is how the law is today, and we're not quite sure how it got
> to this point"
> But then some X time later:
> "so we found out that clauses (1), (e) and (X) were changed on March
> 30, 1957, and we want to know this for future reference"
I imagine that technical challenges come from a different view for your use
case. Content management systems can eventually show differences for
line-oriented text files easily. But I guess that you are also interested in the
maintenance of higher level semantic data structures that are usually contained
in outlines.
How would you like to build relationships between commit logs and changes to
items like chapters, sections, paragraphs and sentences?
Do you need to combine several information sources to generate a document query
and result representation you desire?
Regards,
Markus
next prev parent reply other threads:[~2012-04-03 19:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 13:34 Maintaining historical data in a git repo Yuval Adam
2012-03-30 15:10 ` Seth Robertson
2012-03-30 15:55 ` Yuval Adam
2012-03-30 16:18 ` Seth Robertson
2012-03-30 16:32 ` Jakub Narebski
2012-03-30 16:52 ` Junio C Hamano
2012-03-30 20:39 ` Yuval Adam
2012-03-30 22:29 ` david
2012-03-31 1:04 ` Mark Lodato
2012-04-01 4:14 ` Holding, Lawrence
2012-04-02 11:38 ` Ævar Arnfjörð Bjarmason
2012-04-03 19:45 ` Markus Elfring [this message]
2012-04-03 9:25 ` Andreas Stricker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F7B5347.3010701@web.de \
--to=markus.elfring@web.de \
--cc=git@vger.kernel.org \
--cc=yuv.adm@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).