-
Notifications
You must be signed in to change notification settings - Fork 9
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
Update webid-profile #117
Update webid-profile #117
Conversation
I think 1.0.0 sends misleading signal about stability of this proposal. Probably should be 0.1 |
I object to this draft being published without my input. If you publish it now, please remove my name from the editor and authors draft and note my official objection. I can submit issues and PRs later this week. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I object to this PR. I will submit suggested changes within a week.
I think 0.1 would be an utterly misleading signal about its stability considering the fact that:
The document is currently versioned 1.0.0, and has been for a long time, which was also based on discussions in the CG (please let me know if I need to pull decisions... but it'd save me a minute or two if I didn't have to bother). I see nothing wrong with CG-DRAFT v1.0.0. It is literally a "draft". It changes absolutely nothing concrete about its implementability going from the current v1.0.0 to CG DRAFT v1.0.0. If the versioning information tagged on is in any way a "misleading signal", then an alternative proposal is to publish it without the versioning information, so just "CG-DRAFT". If you feel that this document is inadequate for a CG-DRAFT, then I'd like to request a clear criteria on what should constitute CG-DRAFT. Here is one stub towards such criteria for the CG document: solid/specification#373 . Once something like that is in place, we can verify all proposals for a CG-DRAFT publication in the same way. |
Looking forward to change suggestions. I don't see why they can't be integrated as long as there is consensus. That aside, in the absence of change suggestions, is there something concrete or conceptual or process related objection? |
Nope, I just want an opportunity to suggest some changes. I mentioned them in #116 , In terms of process I suggest that all future decisions about the WebID Profile Document take pace in STMs of the CG devoted to that topic which will make it easier to follow this document without having to disentangle it from general CG topics which, I simply do not have the time to do. I'd also like some clarity on the difference between the ED-Draft and the CG-Draft. |
What semantic version number do you plan to use 5 versions down the road? If two of those versions have breaking changes will you have CG-DRAFT v3.0.0 ? |
I think that's answered by following Semantic Versioning? Again, if we don't want the version number, we can discuss dropping them altogether for this report; for some reports, or; for all reports. |
Right, again, I see no reason not to get any changes in provided there is consensus. At the same time, we do need to weigh in on whether something is a blocker and what consensus would unblock. For example, CG-DRAFT (with whatever version or no version) can be published and as soon as we have an agreed change, we can update the CG-DRAFT.
I think that's a useful thing to raise to the whole CG.
Again, W3C is not entirely clear on this and I've been requesting feedback on how W3C Team should consider the fact that CGs do need to use an ED of sorts to take care of WIP stuff, alongside make CG-DRAFT releases. So, as I understand it, as it stands, what an ED may be to us (CG) internally for day to day stuff / changes, shouldn't have "W3C" branding / naming / styling / statuses / rights etc. Everything else can remain the same. It is only the CG-DRAFT that can have some "official" W3C stuff in the document. This is part of the reason why we are trying to transition to CG-DRAFT reports so that we can rightfully say that they are CG reports. |
May I ask where the shapes stand in relation to the spec? I had thought we were going to point to the shapes as recommendations for interoperability. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wait - we lost the version number. There must be versionnumber. I suggest 1.1
@timbl we have version number, see: https://htmlpreview.github.io/?https://github.com/solid/webid-profile/blob/54e7242b51646e8ee68f69e09dbdfc9e1e0fde10/index.html
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Withdrawing my objection to publishing, this since most of the things I would have changed hinge on issues we'll be discussing in the special topics.
Updates Solid WebID Profile, Version 1.0.0. Publishes:
"This version" is a request to be published as a CG-DRAFT report of the Solid CG.
Solid WebID Profile has only one document type at the moment. Whereas Solid Protocol, Solid Notifications Protocol, Web Access Control have separate documents for "published" and "editor's drafts".
If the group wants to do something similar, i.e., https://github.com/solid/webid-profile/ as an editor's draft, and https://solidproject.org/TR/webid-profile as a CG-DRAFT, we can do that too.
The Preview below shows the proposed latest state for CG-DRAFT Report. The Diff shows the changes made towards CG-DRAFT. (The rest of the recent changes towards it was made in #116 ).
Preview | Diff