It is incredible that just today I posted this on github: https://github.com/ipld/ipld/issues/16

Structs/Traits already exist in some form that is not well defined yet, what you are describing is a generalization of what is happening with Ethereum right now, we have eth-block being a IPLD "Format", which is basically a struct with some particular characteristic where the parser instead of being written in a IPFS VM language, it is written and executed as part of the daemon.

The idea that you have described above or a subset of it, it's part of the plan!

Please do participate in the issue that I linked you to!

This is about IPLD (so data linking to each other instead of files, but the concepts are the same): https://github.com/ipfs/pm/blob/master/meeting-notes/2016-09...

Also, you can use relative paths :P

wouldn't a string just be a list of chars?

yes, let me know!

I look forward to see what will happen with bittorrent.

It's very interesting what you said.

I only discussed what matters to the user (control, interoperability and portability) - extending the list with technical perspective will then come soon.

Thanks a lot for sharing your point, I am a strong supporter of ethereum too.

Thanks!

Whoho, this is very great. Keep it up Paul!

We might need namespaces for webcomponents purposes probably