|-<As you say, making attribution explicit via a protocol will encourage
|-<contributors since their work will be recognized, but maintaining text files
|-<is tedious. How can we use computers to automate it or otherwise make it
|-<easier?
|-<
thats exactly the point.
whats needed is file-structures which on their own (structure-implicitly)
maintain chains of over and over contributing authors and ALSO dont
contain whole, or portions of, files/documents by different authors
within themselves, but only references (-> transclusions), so if you follow
the link back to a transcluded document from anywhere out of your own
'work', you ll touch down at the 'original' with its own author/owner
field and which itself might be comprised of various other pieces as well
as 'original' pieces.
but careful 'authoring' implies that anyway.. even without any supporting
software in place ..
for 'original':
most (all?) of 'artistic' work (also programming?) is not
effectively 'creating' anything new but combining and recombining
ideas,things,codesnippets,programs,sound,etc,etc or parts of them
into some (seemingly) 'new' blob of orderedness., this reaching quite far,
especially when building on/requiring more advanced abstractions available
in 'common' (western in our/my case) culture for 'understanding' ...
mrz.
i love quotes.
and i keep repeating myself.
sorry
