Export EmptyResult dfn for cross-spec referencing#1116
Merged
Conversation
Add an exported <dfn> for EmptyResult so other specs can reference it via xref (e.g., [=EmptyResult=] with data-cite="webdriver-bidi"). Needed by w3c-fedid/digital-credentials#381 which defines a WebDriver BiDi extension command whose result type uses EmptyResult.
OrKoN
approved these changes
May 11, 2026
OrKoN
left a comment
OrKoN
left a comment
Contributor
There was a problem hiding this comment.
LGTM. Although I wonder if if it useful since in the CDDL section you would not be able to import EmptyResult. Perhaps just using an extensible empty object in external specs would be sufficient. I think we also had a discussion about exporting CDDL definitions directly but I do not recall what we end up with. cc @tidoust @jgraham @mohamedamir
Member
|
The Browser Testing and Tools Working Group just discussed The full IRC log of that discussion<jgraham> Topic: Export EmptyResult dfn for cross-spec referencing<jgraham> github: https://github.com//pull/1116 <tidoust> orkon: exporting EmptyResult is kind of separated from the CDDL. Should we accept this PR or is there something we may do for the CDDL. <tidoust> q+ <jgraham> ScribeNick: jgraham <jgraham> ack next <jgraham> tidoust: Right now the CDDL definitions aren't exported by default because in theory there could be mutliple specs defining different bits of CDDL. There are already some that define CDDL and they aren't in common and shouldn't be in the same namespace. Totally fine to export one. `EmptyResult` is a very generic name so another spec might have a <jgraham> slightly different version with the same name. What's missing is a way to export the definition for a specific set of specifications. One way that might work is to namespace the definitions. I think it's fine. <jgraham> jgraham: Seems like we could accept the PR, but look for a more generic solution in the future. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
<dfn>forEmptyResultso other specs can reference it via xref.Motivation
Needed by w3c-fedid/digital-credentials#381 which defines a WebDriver BiDi extension command (
digitalCredentials.setVirtualWalletBehavior) whose result type referencesEmptyResult.Currently, the CDDL rule is defined but has no corresponding exported dfn, so cross-spec tooling (ReSpec xref, Bikeshed cross-refs) cannot resolve it.
Verification
Ran
bikeshed speclocally — clean build.Preview | Diff