Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Clarify interaction affordance binding mechanism-2 #860

Closed
wants to merge 1 commit into from
Closed

Clarify interaction affordance binding mechanism-2 #860

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 11 additions & 3 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2553,9 +2553,17 @@ <h3>Hypermedia-driven</h3>
<p>
<span class="rfc2119-assertion" id="arch-hypermedia">
Interaction Affordances MUST include one or more Protocol Bindings.</span>
<span class="rfc2119-assertion" id="arch-hypermedia-protocol-binding">
<a>Protocol Bindings</a> MUST be serialized as <a href="#sec-hypermedia-controls">hypermedia controls</a> to be self-descriptive on how to
activate the <a>Interaction Affordance</a>.</span>

<span class="rfc2119-assertion" id="arch-hypermedia-protocol-binding-1">
<a>Protocol Bindings</a> MUST be serialized in such a way that they are self-descriptive or otherwise
clearly associated with definitions that indicate how to activate the <a>Interaction Affordance</a>.
Copy link
Contributor

Choose a reason for hiding this comment

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

instead "clearly" I would be more stronger here by "unambiguously"

</span>

<span class="rfc2119-assertion" id="arch-hypermedia-protocol-binding-2">
This MAY be achieved by <a href="#sec-hypermedia-controls">hypermedia controls</a>,
by using <a>Profiles</a> or by using protocol specific metadata.
Copy link
Contributor

Choose a reason for hiding this comment

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

When the profiles is not published, we cannot really refer to it right? This is not a normative reference (not using [[my ref]] so it might be ok but it is still NOT clear what a profile can do. If we look at https://w3c.github.io/wot-architecture/#profile-description-methodology , it only says that it can constrain the protocol verbs etc. Thus, a profile cannot define a protocol binding by this definition.

Copy link
Contributor

@sebastiankb sebastiankb Oct 20, 2022 •
edited
Loading

Choose a reason for hiding this comment

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

I think it's fine as long as there is a Profile definition. Using <a>Profiles</a> would expect this otherwise it will emphasize with a curled red line.

Copy link
Member

Choose a reason for hiding this comment

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

Since WoT Profile 1.0 will now be published after WoT Architecture 1.1 and WoT Thing Description 1.1, I have proposed moving the definition of "profile" from the Profile specification to the TD or Architecture specification in order to resolve the dangling reference - see w3c/wot-thing-description#1719.

Also see w3c/wot-thing-description#1674 in which I proposed an updated description of protocol bindings in the TD specification which takes profiles into account. The wording in that issue describes the two different types of protocol bindings and how they are used.

It would be simpler if there were no normative definitions in the WoT Architecture specification at all, but as long as they exist they need to be kept in sync with the other specifications, since they all cross reference each other.

</span>

The authority of the <a>hypermedia controls</a> can be the <a>Thing</a> itself, producing the <a>TD</a> document
at runtime (based on its current state and including network parameters such as its IP address)
or serving it from memory with only the current network parameters inserted.
Expand Down