Re: Update on DID Spec Task Force and final week sprint to prepare the Community Final Draft

Hi all,

It's great to hear how close the new WG is to becoming a reality!

This past week our team looked at what would be required to implement a
basic (yet fully compliant) DID resolver, and we had some trouble answering
the following questions. I believe one or two of them are already being
discussed in open PR's, and hope that others will serve as valuable
feedback on the spec.

   - How should a resolver handle network connectivity issues during
   resolution?
   - Will establishing a Data Model for the DID Document be an early
   priority for the new WG?
   - Is the no-cache input-option always passed by the client, or can it be
   supplied by the resolver?
      - How does the client pass this input option to the resolution
      algorithm when it's not an input option for the dereferencing algorithm?
   - Are steps 3 and 4 in the dereferencing algorithm (matrix parameters
   'service' and 'fragment') mutually exclusive? If not, how should a DID URL
   with both be dereferenced?
   - Section 8 (Resolvers) of the DIDs spec says that a resolver "MAY offer
   the service of returning requested properties of the DID Document." If this
   means dereferencing, should it say MUST, as this is said to be required in
   the resolver spec?

I understand that the current group priority is to close as many open PRs
as possible before the split, but I am more than happy to open issues and
PRs for any of these which the group thinks warrant further discussion.

Thanks very much,
Charlie Haviland

*Charlie Haviland*
Software Developer | SelfKey
Boston, MA
+1-(203)-913-1756
+66-099-380-8383

<https://www.linkedin.com/pub/charlie-haviland/b4/416/11>



On Fri, Aug 2, 2019 at 6:00 PM =Drummond Reed <drummond.reed@evernym.com>
wrote:

> Good news! The DID Spec Task Force met yesterday afternoon and got through
> decisions (merge/defer) *all of the outstanding PRs* on the current draft
> of the DID spec <https://w3c-ccg.github.io/did-spec/>.
>
> Since we have one more week before we need to start the approval process
> to produce a Community Final Draft, we agreed to the following:
>
>    - All CCG members are encouraged to do their own review of the spec
>    and any remaining open issues to see if you feel any are important enough
>    to create a new PR.
>    - *If you do want to see any other revisions to the spec going into
>    the Community Final Draft*, please either create a new PR or talk to
>    one of the other editors or contributors to create one.
>    - At next week's meeting of the DID Spec Task Force (1PM Pacific Time
>    next Thursday August 8), we will consider the new PRs filed and attempt to
>    decide about every one, i.e., merge or defer. The outcome of that meeting *will
>    be* the final draft.
>
> So please do review the spec and the open issues
> <https://github.com/w3c-ccg/did-spec/issues> and let us know if you have
> any further PRs to suggest.
>
> Thanks—we're almost there!
>
> =Drummond, Markus, Manu, & DID Spec Task Force
>