Zotlabs.org | 'cause we've got Zot

Repository

Mon, 01 Jul 2019 15:42:04 +0000

I think it may be useful to have the work on the specification of the Zot protocol in a repository. Should we do that in a separate repository under framagit.org/zot, or just work on the documents in framagit.org/zot/zap/tree/master/spec?
In my opinion, as we probably want to comment on text and in general have this as a work in progress, it would be better to have a separate repository.
Or possibly even something like Authorea, which makes commenting straight forward (on the other hand its kind of bad to spread out the work across too many tools).

zot w3c

h.EAR.t

Mon, 01 Jul 2019 19:36:46 +0000

I'd rather use Hubzilla natively. Though I read that W3C requires the discussion being retrospectively available. That may be an issue.
I am still in the process of familiarising myself with the demands and coming to a conclusion what we actually want to achieve and how to do it. As I believe almost all of us I merely stumbled into this, but that may only mean we will need more time to prepare, before we can actually start the work.

❦ CRIME LICH ❦

Mon, 01 Jul 2019 20:33:36 +0000

i would just use the mailing list if only to simplify things for anyone coming in through w3c. that way there isn’t a registering of a new hz or zap account just to find the conversations in the first place. if we did have our discussions here i would rather not have them as posts, since posts are easily lost and (unlike a mailing list archive) not easily searchable.

Harald Klimach

Tue, 02 Jul 2019 18:12:06 +0000

OK, so https://lists.w3.org/Archives/Public/public-zot/2019Jul/0000.html is a first mail to the list. I don't think it is feasible to work on the overall report solely via mails. We'll want to keep the current status of the specification somewhere. However, running communication about the document through the mailing list is definitely a good idea.

Motivational welcome post

h.EAR.t

Fri, 28 Jun 2019 15:00:47 +0000

We are a great team, I am not sure wether to laugh or run. But ... we won't get any dumber and there is the slight chance to get something done along the way.
So: Let's do it.

zot w3c welcome

Harald Klimach

Mon, 01 Jul 2019 13:53:48 +0000

OK, so the W3C group is at: zot protocol Community Group

To standardize the Zot protocol currently used in Hubzilla and Zap, and to push its adoption for social web.

There are also some hints for Good practices.

In

Francois Carpentier wrote the following post Sat, 15 Jun 2019 06:20:34 -0400

W3C Proposed Zot Protocol Community Group

The zot protocol Community Group has been proposed by Max Elder:

To standardize the Zot protocol currently used in Hubzilla and Zap, and to push its adoption for social web.

You are invited to support the creation of this group. Once the group has a total of five supporters, it will be launched and people can join to begin work. In order to support the group, you will need a W3C account.

Read more, join, or support this W3C Community group at https://www.w3.org/community/blog/2019/03/11/proposed-group-zot-protocol-community-group/

- - - - - - - - -

For those not familiar with W3C, the World Wide Web Consortium (W3C) is the main international standards organization for the World Wide Web (abbreviated WWW or W3)

For those not familiar with W3C Community groups, they are:
• "proposed and run by the community."
• "designed to promote innovation and to lower barriers to individual participation."
• "enable anyone to socialize their ideas for the Web at the W3C for possible future standardization".
Read more at https://www.w3.org/community/about/
- - - - - - - - -

This is one of my first posts on Hubzilla. Your suggestion or questions are always really welcome :)
- - - - - - - - -

Archive W3C Community Group page
- - - - - - - - -

Mentions

!Zotlabs.org | 'cause we've got Zot
@zotlabs.org | Hubzilla Announcements
!zotlabs.org | Hubzilla Development
!Zot universe NEWS
@Andrew
@Mario Vavti
@Max Kostikov

https://start.hubzilla.org/channel/francewhoa/?f=&mid=3eae5a48be78d66deaeb5933d1ce16f89f6f4e9fbefdcf5e1b74fc078ce3a092@start.hubzilla.org

we said we want to keep the communications and work on the Zot specification on the Zot-based platforms as much as possible.

The currently existing specification resides at framagit: Zot / zap.

Mike sees the following points that need to be addressed:

Some deficiencies in the spec that I'm currently aware of are:

- more detail on the existing/deployed permissions. Permissions are extensible and can be somewhat arbitrary but we do use a few of the existing ones in ways that need to be better documented.

- Detail on 2 or 3 extensions we've provided to ActivityStreams to make our life easier. They aren't absolutely necessary but are good to have in a Zot environment.

- Nomadic content is not well documented. It also isn't really being used at the moment but will be important going forward.

However, to me (not a webdeveloper) the specification itself looks rather vague and not very detailed.
I think we could start off with detailing the Transport and Protocol Basics with the details from the reference implementation in Zap.

Impressum/Imprint | Datenschutzerklärung/Privacy Policy