in reply to Re^4: Level Proposal
in thread Level Proposal

G'day Rolf,

My aim was not to enumerate all of the better choices; but rather, as stated, to provide a (singular) "better choice". The main thrust of that paragraph was absolute vs. relative links.

Years ago, on a number of occasions, I fell afoul of using [node_name] due to some conflict; e.g. a SoPW page and a Monk's username shared the same "node_name". Since then, I've preferred links which contain a "node_id"; this makes the link unique and I don't have to spend any time checking for, and possibly making adjustments to handle, conflicts.

I will often use both a "node_id" and a "node_name"; e.g. [id://node_id|node_name]. Examples include:

For some years, replies have included a [id://node_id] text; this makes it very easy (via copy-paste) to generate content like:

Refer to my [id://some_id|first] and [id://other_id|third] responses.

There are many ways to provide a link. "What shortcuts can I use for linking to other information?" has details. Here's some examples:

I wouldn't consider [The Hermitage] to be the "second best choice". I'd rank all of those containing a "node_id" as superior.

— Ken

Replies are listed 'Best First'.
Re^6: Level Proposal
by LanX (Saint) on Oct 30, 2022 at 11:18 UTC
    > I wouldn't consider The Hermitage to be the "second best choice". I'd rank all of those containing a "node_id" as superior.

    Semantics ... that depends how one groups and counts. All using node_id are the best choice for me, for the same reasons.

    But often you need to reference a node by name without wanting to look up the ID.

    Hence one types SSCCE or kcott - i.e. [SSCCE] or [kcott] - because experience showed it's unique.

    Cheers Rolf
    (addicted to the 𐍀𐌴𐍂𐌻 Programming Language :)
    Wikisyntax for the Monastery

    edit

    I have to admit that [link://...] is irritating me ... at least it doesn't seem to be documented in What shortcuts can I use for linking to other information?

    update

    ok... according to handlelinks settings it's just an alias to [href://...]

        Yes I saw that immediately, after I knew I had to search for href:// ...

        ... and then waited for this response.

        Point is, it should have better been written as

        > [link://...] is an alias for [href://...]

        in consistence with the conventions of rest of the documentation.

        And of course I tried to commit a patch, but alas can't find out how.

        We definitely have many document-types in this monastery.

        Cheers Rolf
        (addicted to the 𐍀𐌴𐍂𐌻 Programming Language :)
        Wikisyntax for the Monastery