Skip to content

Vision should make a positive statement of how the Web should evolve #215

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jyasskin opened this issue Nov 22, 2024 · 13 comments
Open

Vision should make a positive statement of how the Web should evolve #215

jyasskin opened this issue Nov 22, 2024 · 13 comments
Assignees
Labels
Defer Deferred to future work Project Vision Vision and Principles

Comments

@jyasskin
Copy link
Member

The W3C’s Vision for the World Wide Web section contains 4 points that mostly describe ways to "not mess up", with no pointers toward what we should be trying to do.

We should work toward having a W3C-wide positive vision for the web, but I think it's ok to publish this version (consensus on "don't break things" is a step forward), and then develop that direction for the next version.

@tantek tantek added the Project Vision Vision and Principles label Nov 22, 2024
@martinthomson
Copy link
Member

The W3C produces technical standards. It would be a shame to limit the vision to stuff about the how to the detriment of the what. There are a few hooks (like priority of constituencies) but not really a whole lot of substance about what it means to have a technical direction.

I do want to point out that it might be orders of magnitude easier to agree on the how part than the what part. But that's where something like a vision really delivers value. Operational aspirations are great, but exemplary execution is no good without an outcome.

(It seems like many Bond villains appear to have excellent organizational discipline, health care, remuneration, etc...)

@martinthomson
Copy link
Member

I consider this issue a blocker. The TAG has discussed this and does not have consensus either way on that point.

I personally would prefer that this document not be presented as a vision, but as a set of operating principles for the consortium. That is what it is. If it is presented as a Vision, it will do harm to the institution that it is supposed to promote and strengthen. The W3C is a technical standards development body and publishing a vision that does not include any substantive technical component risks undermining the credibility of the institution.

@chrishtr
Copy link

chrishtr commented Dec 9, 2024

We should work toward having a W3C-wide positive vision for the web...

Here's my proposal. The web should be:

  1. The best way to represent all of humanity's information, learning and wisdom.
  2. The best way to easily express any user experience across all modalities, languages and cultures.
  3. Universally available and accessible to all users and all computing devices.
  4. An open system available to all that is better than any proprietary alternative.

@martinthomson
Copy link
Member

martinthomson commented Dec 12, 2024

I don't think that a true vision for the technical future of the web is so brief. I refer to Mozilla's vision, which is a substantial document. I don't think that this (edit: that is, Mozilla's vision) is the right sort of thing for the W3C to advocate for as it is somewhat narrower in scope and maybe less positive than I would personally advocate for in 2024.

However, as I mentioned, the title of the document could more accurately reflect the somewhat internal focus of this document. This is not a vision statement, but a set of guidelines for how we think the consortium should operate.

Hence: "Operating Principles for W3C" is my suggestion as a title.

@chrishtr
Copy link

chrishtr commented Dec 12, 2024

I don't think that a true vision for the technical future of the web is so brief.

Fair. I think it's worth having a brief and bold statement that everyone can get behind, but just my 2c.

@cwilso
Copy link
Collaborator

cwilso commented Jan 3, 2025

The "Vision of the WWW" section was always intended to be a very brief summary. I suggested a long time ago removing this entire section from this Vision of the W3C, but was overruled. I think a longer statement around the technical evolution of the Web would be a good idea; I think that's probably more in the remit of the TAG. I think this is deferrable.

@tantek tantek self-assigned this Jan 9, 2025
@fantasai
Copy link
Contributor

Agree with @cwilso: this is the vision document for W3C, not for the Web. We might consider drawing up such a document (maybe as a joint AB+TAG deliverable?), but it would be a separate document.

@mgendler
Copy link

The editors and chair discussed, editor to discuss with Martin directly to figure out next steps.

@cwilso
Copy link
Collaborator

cwilso commented Mar 7, 2025

@tantek reminder that this is on your plate.

tantek added a commit that referenced this issue Mar 14, 2025
This one word addition ("W3C Core Vision for the World Wide Web" as a replacement for "W3C Vision for the World Wide Web") is an attempt to resolve the "blocker" part of issue #215, in particular this comment: #215 (comment).

This makes sense because it is not the intent of this first version of the Vision to fully define "World Wide Web". I believe this is an improvement in the precision of this heading.

The remaining aspects of of #215 will be addressed in the next version (without objection).
cwilso pushed a commit that referenced this issue Mar 18, 2025
This one word addition ("W3C Core Vision for the World Wide Web" as a replacement for "W3C Vision for the World Wide Web") is an attempt to resolve the "blocker" part of issue #215, in particular this comment: #215 (comment).

This makes sense because it is not the intent of this first version of the Vision to fully define "World Wide Web". I believe this is an improvement in the precision of this heading.

The remaining aspects of of #215 will be addressed in the next version (without objection).
@cwilso
Copy link
Collaborator

cwilso commented Mar 18, 2025

With #254 merged, I believe we are now okay to move this to "defer" to pursue further post-v1. @martinthomson ?

@cwilso cwilso added the Defer Deferred to future work label Mar 20, 2025
@martinthomson
Copy link
Member

After having spoken with @tantek, I was given to understand that more significant changes were afoot. I've been busy with other tasks for a week or so, but #254 doesn't work for me. I think that it needs to be more substantive than that.

@tantek
Copy link
Member

tantek commented Mar 24, 2025

At this point given the depth and breadth of review (and wide approval as tracked in #195) the document has had, more substantial changes like re-organizing sections (or completely rewriting section 3) was deemed out of scope in discussion with VisionTF chair and fellow editor.

Since the TAG as a whole did not label this as a blocker (and there was no evidence that that had changed in any regard since the issue filing) we reduced the scope of section 3 accordingly (which itself had started to succumb to rewriting by committee due to the back/forth in #211) with the expectation that it will get updated for v1.1 of the Vision, and are leaving this issue open and labeled "defer" to address the remaining aspects and help drive that update.

At this point, one escalation path would be to take it back to the TAG to see if you can convince the TAG that this should be a blocker. Otherwise we are not expecting to make any more edits to this section before taking the Vision to an AC vote for Statement (approved by the AB last Thursday).

Lastly, the original issue as filed,

4 points that mostly describe ways to "not mess up", with no pointers toward what we should be trying to do.

is fully resolved as all 4 points have been reworded as positive statements, which are arguably aspirational ("how the Web should evolve" as the issue is titled), since there are many current exceptions.

And subsequent principles in the next section address the what of each of those more specifically.

Any further suggestions for changing section 3, or section 4, or re-ordering beyond the original issue description should be filed as one or more new issues.

@dontcallmedom
Copy link
Member

(I think this issue aligns with what I had tried to convey in #143 for future discussions)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Defer Deferred to future work Project Vision Vision and Principles
Projects
None yet
Development

No branches or pull requests

8 participants