Notes: "Multi" Org + Protocol Suite Name

[jbenet]

We need an org name for the "multi" protocol family:

• multihash
• multiaddr
• multikey
• multicodec
• multistream
• multibase

The possibilities that come to mind:

• multiprotocols
• multis
• multicodes
• multisuite
• multiprotos
• multiformats

This word should fit these sentences:

• Multihash and Multiaddr are both [ part of ] ________ .
• [The] _________ [ is / are ] a collection of formats or protocols that use efficient self description to provide interoperability and cryptographic agility.
• [The] ________ [ is / are ] so useful.
• If you design it as a ______ system, then you're not locked in.
• ________ system
• https://github.com/______
• https://_______.io

Try saying them out loud.

[jbenet]

cc @diasdavid @lgierth @whyrusleeping @dignifiedquire @RichardLitt @nicola @stebalien @kubuxu

[whyrusleeping]

'multis' is a nice option.

[nicola]

I am all for multiprotocols (if you want to be fancy, multiwg, wg is for working group)

[Stebalien]

I also like multiprotocols.

Also, "multis":

(Maltese)

[nicola]

multispecs

[RichardLitt]

Multiprotocols
Multispecs
Multis

In order of preference.

[ghost]

I like multispecs

[ghost]

• Multihash and Multiaddr are both [ part of ] _multispecs_.
• [The] _multispecs_ [ is / are ] a collection of formats or protocols that use efficient self description to provide interoperability and cryptographic agility.
• [The] _multispecs_ [ is / are ] so useful.
• If you design it as a _multispecs_ system, then you're not locked in.
• _multispecs_ system
• https://github.com/multispecs
• https://multispecs.io

None of these really work with "multis" :)

[qxotk]

Fabric

---

james mcfarland
[email protected]
www.jamesmcfarland.com
On Jun 17, 2016 7:34 AM, "Lars Gierth" [email protected] wrote:

• Multihash and Multiaddr are both [ part of ] _multispecs_.
• [The] _multispecs_ [ is / are ] a collection of formats or protocols
  that use efficient self description to provide interoperability and
  cryptographic agility.
• [The] _multispecs_ [ is / are ] so useful.
• If you design it as a _multispecs_ system, then you're not locked in.
• _multispecs_ system
• https://github.com/multispecs
• https://multispecs.io

None of these really work with "multis" :)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ipfs/notes/issues/135#issuecomment-226747125, or mute
the thread
https://github.com/notifications/unsubscribe/ABzw8YKl3DjlmNs5Sm4vqtSJqTsinBPAks5qMoZGgaJpZM4I3862
.

[qxotk]

Hashfabric

---

james mcfarland
[email protected]
www.jamesmcfarland.com
On Jun 17, 2016 7:41 AM, "james mcfarland" [email protected] wrote:

Fabric

---

james mcfarland
[email protected]
www.jamesmcfarland.com
On Jun 17, 2016 7:34 AM, "Lars Gierth" [email protected] wrote:

• Multihash and Multiaddr are both [ part of ] _multispecs_.
• [The] _multispecs_ [ is / are ] a collection of formats or
  protocols that use efficient self description to provide interoperability
  and cryptographic agility.
• [The] _multispecs_ [ is / are ] so useful.
• If you design it as a _multispecs_ system, then you're not locked
  in.
• _multispecs_ system
• https://github.com/multispecs
• https://multispecs.io

None of these really work with "multis" :)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ipfs/notes/issues/135#issuecomment-226747125, or mute
the thread
https://github.com/notifications/unsubscribe/ABzw8YKl3DjlmNs5Sm4vqtSJqTsinBPAks5qMoZGgaJpZM4I3862
.

[Kubuxu]

If we are listing ideas: multispace.

[daviddias]

Self Describable Protocols, with acronym SDP.

"Multihash and Multiaddr are both SDPs"

[nicola]

https://en.wikipedia.org/wiki/Session_Description_Protocol :(

[pbronez]

Multicols = Multiple Protocols

• Multihash and Multiaddr are both Multicols.
• Multicols is a collection of formats or protocols that use efficient self description to provide interoperability and cryptographic agility.
• Multicols are so useful.
• If you design it as a Multicols system, then you're not locked in.
• Multicols system
• https://github.com/multicols
• https://multicols.io

[haadcode]

How many tickles does it take to make a specification laugh?
_Multickles_

I'll get me coat...

[jbenet]

I think so far these are liked the most:

• multiprotocols (5 s)
• multispecs (3 s)
• multis (2 s)

---

multispecs is growing on me.

• @lgierth's plugging into examples makes it very clear that it can be used in sentences where "protocol" and "format" are there without much issue.
• short, sounds nice. ("multiprotocols" is more clear, but it's a mouthful. and 5 syllables)

---

• people dont like "multiformats" ? (4 syllables)

[dignifiedquire]

I really like multicols with multispecs in second place

[RichardLitt]

Multicols sounds to me like multicolumns. I'm not sure it's a good portmanteau.

I like multispecs (more than multiprotocols).

[daviddias]

My favourite is still SDP, but second favourite is multispecs

[jbenet]

@diasdavid i like SDP too, but clashes. And i think "Self Describing Protocols" should include more than these small formats-- ideally stuff around pulling the code and running it in a VM. Stuff that builds on these, but that brings closer to the stuff alan kay and others have worked on (see references in Alan's paper).

[jbenet]

• I think "multispecs" is more popular with the people in this thread.
• I think let's abandon "multiprotocols", it's way too long and hard to say.

Some more plugs for "multiformats"

• I think "multiformats" is easier to say than "multispecs"
• "format" is more accurate. a "format" is also a spec, but specifically describes encodings or representations (these so far all involve encodings and representations).
• after trying it for a bit on people, "multiformat" seems to do better at evoking what these things are. "multispecs" seems to general.

I will be at https://www.w3.org/2016/04/blockchain-workshop/ and try both on people and see how they go.

[dignifiedquire]

:+1: for multiformats

[ghost]

multiformats is just fine!

[jbenet]

I tried both on people, multiformats seemed to give that set of people a much better feel. multispecs was too vague. I think we should go for it. I'll give a few days for anyone to raise concerns

[jbenet]

• @diasdavid got https://github.com/multiformats
• @jbenet got https://github.com/multispecs

The main thing preventing me from settling on "multiformats" is that it _is hard to read_ in writing:

---

• multihash and multiaddr are both multiformats.
• If you design it as a multiformat system, then you're not locked in.
• multihash and multiaddr are both multispecs.
• If you design it as a multispecs system, then you're not locked in.

[jbenet]

• Maybe multiformats could be _camel-capitalized_: MultiFormats
• Maybe multiformats could be _abbreviatged_: MF

eg

• multihash and multiaddr are both MultiFormats.
• If you design it as a MultiFormat system, then you're not locked in.
• multihash and multiaddr are both MFs.
• If you design it as an MF system, then you're not locked in.

Capitalizing may mean:

• people start writing: MultiHash, MultiAddr, MultiCodec, MultiStream.

which may be ok, and may even be better in prose.

Thoughts?

[ghost]

The main thing preventing me from settling on "multiformats" is that it is hard to read in writing:

Because of the "tif" in the middle? I find it okay to read.

people start writing: MultiHash, MultiAddr, MultiCodec, MultiStream

Then we may want to update type names in go and javascript.

[jbenet]

Then we may want to update type names in go and javascript.

indeed. im not sure. :S

[RichardLitt]

I believe that this can be closed now. Please refer to github.com/multiformats.