-
Notifications
You must be signed in to change notification settings - Fork 93
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
Looking up users by W3C ID #104
Comments
AFAIR, these aren't hashes but unguessable strings to prevent from harvesting data on users that are not expected to be exposed - IIRC, the rule is we only expose data about participants in groups. The path that is used in the IPR checker and should be usable in ReSpec as well is to walk through the list of participants via (it may also be that the privacy design of the API should be revisited) |
That is correct. (For some history see #46 (comment) and #55)
I'm not opposed to revisiting this. |
Ok, but if we can basically go through What might be better is restricting what one could get from For example, this is all public https://www.w3.org/groups/wg/eowg/participants ... the W3C API could return the same data:
|
For the
/users/
path, the W3C API relies on a "hash" to represent a user, but it's unclear how the hash is derived. In specs, we usually provide the "w3c_id".... Question: is the "hash" a hash of the W3C ID? (tried md5 and sha-1)If not, would be be possible to add support for looking up users by their w3c id? This would be great in ReSpec, as we could just provide a list of W3C IDs, and the W3C API could provide all the relevant details (e.g., affiliation).
Alternatively, if I knew how to derive the hash, I could do that via ReSpec to get Editors names and other details.
The text was updated successfully, but these errors were encountered: