Hi Tony,
;TLDR
Absolutely no offense intended. ... The internet has the same problem and
didn't solve it ... yet.
-----------
This discussion has been going on for ages. A "serial number" has the exact
same problems as the tiddler-title. It only uses a different name.
If you replace "serial number" in your OP with "tiddler title" there would
be no difference, *from a technical point of view*.
tiddler-titles have to be unique within 1 TW file. -> This causes problems,
if you import tiddlers with the same title.
serial number has to be unique within 1 TW file. -> This causes problems,
if you import tiddlers with the same number.
... I think you can see the "differences" ... it's "serial number"
IMHO: Since technically the proposed change/addition suffers the same
problems, it can _not_ be used as a solution.
---------------
To make a data-point unique, there are different approaches (partial
solutions) at the moment.
- We can use an URL link as the origin. eg:
- https://tiddlywiki.com/#HelloThere ... which is different to
- https://example.com/#HelloThere
Using this "origin" would be already better as using a "per tiddler serial
number" ... BUT ... tiddlywiki.com needs to be paid on a yearly basis. So
as soon as nobody pais for it, it will be gone -> and what's *much worse*.
... *It can be reused*, after some time!!
IMO we need something "more unique" and STABLE ..
- We could use an URI
<https://en.wikipedia.org/wiki/Uniform_Resource_Identifier> (Uniform
Resource Identifier) as an origin field.
- URL is an URI ... but it's not useful as we found out already
- URN
<https://en.wikipedia.org/wiki/Uniform_Resource_Identifier#URLs_and_URNs>
may be a better choice.
from wikipedia:
>
> A Uniform Resource Name (URN) is a URI that identifies a resource by name
> in a particular namespace. A URN may be used to talk about a resource
> without implying its location or how to access it. For example, in the
> International
> Standard Book Number (ISBN)
> <https://en.wikipedia.org/wiki/International_Standard_Book_Number>
> system, *ISBN 0-486-27557-4* identifies a specific edition of
> Shakespeare's play *Romeo and Juliet*. The URN for that edition would be
> *urn:isbn:0-486-27557-4*. However, it gives no information as to where to
> find a copy of that book.
>
*So URN is a real solution used in the "isbn" field*. ... *plus *whatever
unique field exists in a TW ...
- THE problem is: .. it *costs *something.
- The ADVANTAGE is: *it doesn't expire
<https://self-publishingschool.com/isbn/#expire>*.
Since TW is similar to an e-book, I do think this a real consideration.
Since the price goes down if I get a 100, or more, of them, I did consider
this possibility. ..
There is an other advantage. ... You can dramatically increase the "reach"
of your TWs if you list them, where it's allowed to list ISBN numbers. ...
In Austria, it would go down to € 0.60 per TW, that gets an isbn number. As
a member of the "Hauptverband" it would be € 0.30
BUT it still costs something :/
That's why I'm so excited about the dat:// protocol. ... The DAT-address is
a universal unique ID and a "public access key"
So if a tiddler contains a "dat" or "origin" field, that contains its
origin, you can walk the chain, even if a tiddler is a clone. (This field
would have "privacy related" challenges, that have to be considered!) ...
see privacy NOT security!
IOM renaming isn't a problem anymore, since a dat-archive contains the full
history. ... Full links like dat://<address>+<version>/#HelloThere don't
expire, since you can be sure, that address + version will know about this
tiddler. ...
TWs won't die, as long as there is 1 party that "seeds" the content. So if
you can't pay for your archive, there may be someone else, who has an
incentive, that your content stays online.
Such a party may be someone that "links" to your content, from their own
content. ... or the Internet Archive <https://archive.org/>.
There is still the problem with renaming tiddler titles.
Yes but now it can be solved using per TW unique aliases or titles that
never change and plugins like "uni-link
<https://wikilabs.github.io/editions/uni-link/>" and "relink-plugin
<https://github.com/flibbles/tw5-relink>" which *create human readable*
links.
-----------------------
Using dat:// we can recreate a TiddlySpace like structure using a P2P (peer
2 peer) architecture and mechanisms that TW already contains. Like: Shadow
tiddlers for archives withOUT write access and normal tiddlers for archives
with write access.
The only thing we need is a browser that knows how to deal with dat
archives. Like beaker-browser or I think even better: Cliqz .. A FireFox
clone, where the latest Developer-Edition can read and probably write to
dat:// (I'm investigating it atm.)
just some thoughts
have fun!
mario
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" 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/tiddlywiki/5ee4ef41-d0c8-43de-9461-91db1fd1969b%40googlegroups.com.
