NO I completely forgot to post a JIRA entry on that! Just got it in though: https://jira.secondlife.com/browse/VWR-23451
Any useful counter-arguments/expansions can go there. :) Ricky Cron Stardust On Fri, Oct 15, 2010 at 5:46 PM, Marc Adored <m...@inworlddesigns.com> wrote: > Woops forgot to reply to all so it went to the list :P > > > I think your post here: > > https://lists.secondlife.com/pipermail/opensource-dev/2010-September/003167.html > > Was a very good one explaining what the advantages could be. A true > xml format like that would be easy to read and easy to parse. Of > course its not a line by line conversation like you read in the viewer > but it is in an order and all information would be provided in an easy > to read format provided the viewer exports the xml with proper line > endings and tab spacing :P > > Did a jira ever get posted about that? > > On Fri, Oct 15, 2010 at 8:32 PM, Ricky <kf6...@gmail.com> wrote: >> I'd have to say that future proof and archival safe are two separate >> qualities. Logs might need to be archived, but 90% (guessing) of the >> content is fluff only useful for a couple of months to a year at the >> most. However, the tools that read them (such as converters / >> archivers) have a much longer lifespan. If you do want 50+ year >> archival quality, then use a trivial exporter to convert to the ASCII >> format of your choice when you run your archival process and send it >> to paper punch tape. (I'm not being insulting here: paper punch tape >> is THE most long-lived digital format I've ever met.) >> >> As to the stylesheet: I propose that it be installed with the viewer >> and be located in the same folder as the logs. This way it can be >> archived along with the files by your favorite archival/storage tools. >> >> And viewing the file is likewise not an issue. Every modern computer >> already has a browser installed and in use. And if you still needed >> to read the log from a GUI-less computer, the logs are still ASCII. >> The tags surrounding the data are just helpful to the computer. This >> isn't a binary format we are discussing; it's a formatted text file. >> Formatted in a way that makes it easier for a computer to read while >> still being useful to the humans involved. >> >> On Fri, Oct 15, 2010 at 5:11 PM, Jamey Fletcher <ja...@beau.org> wrote: >>> Marc Adored wrote: >>> >>>> Download a stylesheet? The file would contain a link directly to the >>>> stylesheet and would be automatically loaded. Also I'm not sure about >>>> your operating system but I'm pretty sure the file extension already >>>> opens in your default browser and once the stylesheet is specified it >>>> will look just like a plain text log file just loaded in your browser >>>> through the same process and opening a text file. The only fear here >>>> is change and the unknown. It's not going to be any harder to read the >>>> logs just different. Sorry like Ricky said its more future proof and >>>> thats all there is too it the only mistake was not setting this up >>>> earlier so the change didn't frighten so many people >>> >>> Let's see... Future Proof. >>> >>> Program to read and process a text file - anywhere from a few hundred >>> bytes, to a small OS-wannabe like emacs. Program to process LLSD and >>> display it - several hundred K minimum, oh, and *REQUIRED* network >>> connection live so the referenced DTD can be retrieved - more like a >>> program that is ALREADY being considered an OS-replacement, such as >>> Internet Explorer, Mozilla, Safari, or Chrome, each several dozen megabytes. >>> >>> Ok, so let's look at a project that's *GOT* a nice long history already >>> (some 30+ years) and is *VERY* interested in future-proofing. Minor >>> project, really, called Project Gutenberg. Here's what *they* have to >>> say on the subject: >>> http://www.gutenberg.org/wiki/Gutenberg:General_FAQ#G.17._Why_is_Project_Gutenberg_so_set_on_using_Plain_Vanilla_ASCII.3F >>> >>> When you really, really, *REALLY* want it to be readable - ASCII >>> plaintext is the way to go. >>> _______________________________________________ >>> Policies and (un)subscribe information available here: >>> http://wiki.secondlife.com/wiki/OpenSource-Dev >>> Please read the policies before posting to keep unmoderated posting >>> privileges >>> >> _______________________________________________ >> Policies and (un)subscribe information available here: >> http://wiki.secondlife.com/wiki/OpenSource-Dev >> Please read the policies before posting to keep unmoderated posting >> privileges >> > _______________________________________________ > Policies and (un)subscribe information available here: > http://wiki.secondlife.com/wiki/OpenSource-Dev > Please read the policies before posting to keep unmoderated posting privileges > _______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
