-
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
DID Resolver did-url Use Cases: Draft DID did-url ABNF grammar fails for most of the basic use case patterns... #33
Comments
The failures were caused by undocumented changes being made to Appendix A (addition of the "$" and "!" operators) without consulting the larger DID community. PR WebOfTrustInfo/rwot8-barcelona#164 resets the grammar to BB (before Barcelona). A copy of the grammar can be found here: https://github.com/mwherman2000/indy-arm/blob/master/abnf/did-abnf-2019-03-07.abnf |
@mwherman2000 , I think you misunderstand. What was developed in Barcelona is a proposed set of revisions to the ABNF for the DID spec based on the work of the DID Spec team that self-organized there. That's the whole point of the Rebooting the Web of Trust conference—for teams to come together to work on work items to advance the community. The proposed revisions to the ABNF have no standing until they are presented to the CCG. That hasn't even happened yet—the CCG didn't even meet last week—nor is the RWOT DID team finished with the document we started to explain it. So maybe hold your fire until the troops can reach the beach? |
RE: Barcelona @talltree The earth continued to rotate on this axis and the DID Resolution community met on its regular schedule. Most of the meeting was spent reviewing and discussing the 20+ DID Resolver use cases in an open forum: #32 An open discussion - all carefully documented and recorded - with open, public follow-up. p.s. Do you have a complete set of use cases for your grammar? I recommend building a comprehensive set of use cases and samples first before working any further on your grammar ..,a best practice for any software project. IMO, working in the grammar first/in isolation is akin to "pushing rope". |
@mwherman2000 I agree the "after Barcelona" ABNF should be considered just a proposal at this time, not more. Personally, I also have questions about it, e.g. whether there really needs to be an extra At the same time I also want to point out that your own proposals and use cases around the DID syntax (to consider the syntax an "algebra" or "protocol specification") at this time don't necessarily reflect community consensus either - for example, so far I haven't heard anyone other than you promote the idea that DID syntax should support something like Therefore, both topics need more discussion to reach consensus. (As an additional, orthogonal comment, looking at your screenshots it seems you tried to validate against the |
@peacekeeper In an early, early test, I did try validating the ABNF against the
I haven't seen any record of meeting where Drummond's DID ABNF was proposed or discussed and if so, a list of who was present. There's been no visible effort to build trust around Drummond's DID ABNF. It appears to have "just happened".
I agree but, IMO, not as PRs to the did-spec as @dmitrizagidulin suggested. Competing PRs are too difficult to manage. I recommend that Drummond propose his syntax as a I recommend we start with the use case discussions first. Let's not "push the rope". |
First of all, it's not "Drummond's DID ABNF". It was an outcome of the DID Spec group that formed at Rebooting the Web of Trust #8 in Barcelona, which is a community event, and which is about as visible as we can make it, i.e., full documented and reported to the community here and here. Secondly, we haven't had a chance to discuss this on a CCG call yet because there hasn't been one since RWOT. Michael, I would like to understand why in this forum you consistently shoot first and ask questions later. We have longstanding members of the community who are making their best efforts to collaborate in different community events, yet your comments seem to imply that we are trying to work behind closed doors or that we have some secret agenda. Why is that? |
I recommend we (re)start with the use case discussions first. Let's not try to "push the rope". |
@mwherman2000 You clearly have a completely different view of the role of the Rebooting the Web of Trust conference in advancing the work of this community that many of the rest of us do. And how can you charge that "there was no attempt to include remote participation" when in fact you participated remotely one of the three days? (For many reasons it did not turn out to be feasible the other two days—RWOT is a dynamic event with many interruptions.) Secondly, you say "let's start with the use case discussions". Are you somehow suggesting that the CCG has not had two years of use case discussions? Have you read the DID Use Cases document? The only new use case—which is not really new, but a slight variation on the long understood use cases of DIDs for cryptographically-verifiable persistent references to resources—is described in the topic paper called DID Content References than Ken Ebert and I submitted to Rebooting the Web of Trust #8. And the only proposed change to DID ABNF syntax (other than some refactoring to better align it with RFC 3986 syntax) is:
So we are not "pushing any rope"—and we do not need to "restart with the use cases discussions". Please focus on exactly what we are proposing and share why you do or do not support the proposal. |
@talltree We both need to be more precise in our communications to avoid the ongoing counter-punching, saber-rattling, and confudsion that has resulted.
@Tallfree, have you studied the 20+
I'll address the topics in the second half of your comment once I've had a chance to review them. With respect to the DID Object Data References paper, there are 3 issues waiting here for a response: https://github.com/WebOfTrustInfo/rwot8-barcelona/issues Suggested community plan of attack a. The Use Cases for Decentralized Identifiers document is a good input to helping identify additional Thoughts? |
@mwherman2000 in your very first screenshot yes the (I would consider this a small mistake on your part and not really central to the topic at hand.) |
Agreed @peacekeeper. It became irrelevant when I realized I was using the AB (After Barcelona) version of the |
Sidebar: Checkout Giving Grammars Written with ABNF Notation the Respect They Deserve. |
Moving discussion back to here #32. Closing this issue. |
The "after Barcelona" (AB) draft DID ABNF grammar (https://github.com/WebOfTrustInfo/rwot8-barcelona/blob/master/draft-documents/understanding-dids-in-greater-depth.md#appendix-a-anbf-for-dids-and-did-urls) fails for some of the basic DID Resolution use case patterns...
ABNF Validation Tool: http://arran.fi.muni.cz/bnfparser2/
Example: NOTE: Use
did-url
as theSymbol
to validate against.A. DID Document Resolution and Dereferencing Use Cases
2a. FAIL Dereferencing to return a JSON component (fragment) of a DID Doc | did:xyz:1234#key1
2b. FAIL Dereferencing a service-id to return the JSON description (fragment) of the service endpoint. | did:xyz:1234;bops
B. DID Document Service Endpoint Invocation Use Cases
2c. FAIL Dereferencing a
service-id
and invocation of the corresponding service endpoint (with no parameters) | did:xyz:1234;bops?2d. FAIL Dereferencing a
service-id
and invocation of the corresponding service endpoint (with parameters) | did:xyz:1234;bops/foo/bar?a=1#flipC. DID Document Operations Use Cases
4b. FAIL Does this DID Doc contain a service endpoint corresponding to a particular
service-id
resolvable by this DID Resolver | did:xyz:1234;bops?existsD. DID Document Collection Operations Use Cases
4a. FAIL Does this DID Doc fragment exist/is resolvable by this DID Resolver | did:xyz:1234#key1?exists
E. DID Resolver Service Operations Use Cases
F. DID Resolver Service Response Format Use Cases
15a. FAIL Resolution to return an entire DID Doc in JSON format | did:xyz:1234?$format="json"
15b. FAIL Resolution to return an entire DID Doc in ATOM format | did:xyz:1234?$format="atom"
15c. FAIL Resolution to return an entire DID Doc in XML format | did:xyz:1234?$format="xml"
The text was updated successfully, but these errors were encountered: