On Friday, February 28, 2020 at 5:37:53 AM UTC-5, Marcel Franke wrote:
>
>
> Am Freitag, 28. Februar 2020 02:11:20 UTC+1 schrieb Thomas Passin:
>
> BTW Using "created" instead of "timestamp" would be more 
>>> self-documentating.
>>>
>>
>> That's up in the air for me.  Should it represent the creation time or 
>> the last-modified time? 
>>
>
> Both have value, so add both.
>
>  I don't want to add yet another piece of metadata if it's not needed.  
>>
>
>  It's always better to collect more than neccessary than to some day miss 
> what's needed. Storage is cheap.
>

It's not about storage, it's about reducing visual clutter in the text.
 

> Yet the Leo id does actually include a timestamp for the creation time.  
>>
>
> It's not expliciet, nor portable. You must be aware of it when you decide 
> to change the ID or software some day. 
>

Well, that's a point.  I had pictured running some script over all the 
notes to pick out the time format from the id string when and if you 
decided to change.  So there wouldn't need to be a separate line for the 
creation time. After all, how likely is it that some other system could 
used the exact format of the zettels with no change at all?  But maybe it 
would be good to have that creation string be in the same, more readable 
format as the timestamp date I'm already providing.
 

> And this is something which can be easily move out of sight. Ok, that's my 
> habits as a devloper shining. 
> Non-devs probably see it different. But general experience with those 
> things is that they should be clear. 
>
> I'd like to settle on one specific name for that timestamp, though, and 
>> finalize it soon before I have too many nodes the other way.
>>
>
> Strictly spoken, the name alone is not much of a problem. One can always 
> write a script for mass-changing this. that is the advantage of structured 
> data.
> What it can't do is adding missing data. But of course I only speak from 
> perspektive of a developer, so take it with a grain. 
>

A good developer puts on the hat of a user, and switches back and forth, 
all the time.  Though that user might be the developer's own self because 
the developer wants to use the system once developed.

More important than capturing all the metadata one might ever want, is to 
make the system backwards compatible so that if you add something later, 
the earlier work is still as usable as ever.

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/67a14ad0-e50b-41ad-b22c-9c7daa5533d7%40googlegroups.com.

Reply via email to