Skip to content
This repository was archived by the owner on Oct 29, 2019. It is now read-only.

added section on interop - #234

Merged
msporny merged 3 commits into
gh-pagesfrom
interop2
Aug 8, 2019
Merged

added section on interop#234
msporny merged 3 commits into
gh-pagesfrom
interop2

Conversation

@jandrieu

@jandrieu jandrieu commented Jul 8, 2019

Copy link
Copy Markdown
Contributor

@peacekeeper peacekeeper left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added two small comments, but I'm fine with merging and improving later.

Comment thread index.html
</section>

<section>
<h3>Interoperability</h3>

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be called "Conformance" instead of "Interoperability"?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe. Although then I think there should be more text in there. The question of interoperability is about constraint on what "conformance" means and I expect there should be more explaining the full scope of conformance if that's the section heading.

Comment thread index.html Outdated
<li> the specification contains sections describing security and privacy considerations.</li>
</ol>

<p>The working group's test suite will test all normative requirements for DIDs and DID Documents. Human evaluators will need to read DID Method specifications to evaluate conformance.</p>

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Feels a bit strange to have text in the spec that talks about something the WG will do, no?

Comment thread index.html Outdated
Comment thread index.html

<section>
<h3>Interoperability</h3>
<p>Interoperability of implementations for DIDs and DID Documents will be tested by evaluating an implementation's ability to create and parse DIDs and DID Documents that conform to the specification. Interoperability for DID methods will be determined by evaluating each DID method's specification to determine, at a minimum, </p>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The markup indents should be using 2 spaces per level. Also would be nice to wrap paragraphs at ~80 chars like the current format.

@rhiaro rhiaro added intro/overview Pertains to introductory sections of the spec, either main introduction or intros to subsections non-normative Changes to non-normative text that are more substantive than 'editorial' labels Jul 18, 2019
Co-Authored-By: David I. Lehn <dil@lehn.org>

@msporny msporny left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The spec shouldn't say what the WG will and won't do. Conformance statements that a human has to evaluate are typically not useful (not always, but most of the time).

Comment thread index.html Outdated
Co-Authored-By: Dave Longley <dlongley@digitalbazaar.com>
@msporny
msporny merged commit dcb6d4c into gh-pages Aug 8, 2019
@msporny msporny added the merge label Aug 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

intro/overview Pertains to introductory sections of the spec, either main introduction or intros to subsections merge non-normative Changes to non-normative text that are more substantive than 'editorial'

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants