Re: URI Scheme for git object ids?
- From
- Ed Warnicke <hagbard@gmail.com>
- Date
- Mar 1, 2022, 17:43 UTC
- Message-ID
- <CAFVSqg2GEs7QXQvHmhxgxFAy35yN5GgDGwAZ1bPm-gfmCPzqRA@mail.gmail.com>
- In-Reply-To
- <xmqqy21tr2pg.fsf@gitster.g>
Junio,
That's the kind of feedback (and pointers) I was hoping for :)
So is it fair to say you are suggesting:
1. Talk to 'torrent or something' folks to see if they have a scheme in use
and
2. If not, 'gitoid:${hashtype}:${hashvalue} - like:
gitoid:sha1:261eeb9e9f8b2b4b0d119366dda99c6fd7d35c64
would be a better choiceEd
On Tue, Mar 1, 2022 at 11:40 AM Junio C Hamano <gitster@pobox.com> wrote:
Show 30 quoted lines
>
> Ed Warnicke <hagbard@gmail.com> writes:
>
> > Has there been any discussion of how one might represent a git object
> > id as a urn or uri?
> >
> > It's clear that 'git:' is registered with IANA as a URI prefix for
> > locations of git repos.
> >
> > I was wondering if there was any existing use of something like:
> >
> > 'gitoid:${type}:${hash type}:${hash of git object}' ?
> >
> > So for example:
> >
> > gitoid:blob:sha1:261eeb9e9f8b2b4b0d119366dda99c6fd7d35c64
> >
> > which could be used to communicate generic git object ids.
> >
> > Ed
>
> I do not see why the object type should be there. Once you locate
> the object whose object name (in sha1) is 261eeb..., the object
> should be able to identify itself as a blob (or whatever type it
> is).
>
> Aren't there already folks who are exchanging git objects over
> torrent or something? What do they use to identify what each node
> offers and what participants want?
>