Skip to content

Commit

Permalink
Update affordance names, split create references
Browse files Browse the repository at this point in the history
  • Loading branch information
@farshidtz
farshidtz committed May 31, 2021
1 parent 1421747 commit 733a634
Showing 1 changed file with 19 additions and 11 deletions.
30 changes: 19 additions & 11 deletions index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -899,9 +899,7 @@ <h4>Creation</h4>
A TD which is identified with an `id` attribute MUST be handled
differently with one that has no identifier (<a>Anonymous TD</a>).
</span>
The create operations are specified as `createTD` action in
[[[#directory-thing-description]]]
and elaborated below:
The create operations are elaborated below:
</p>
<ul>
<li>
Expand All @@ -919,6 +917,10 @@ <h4>Creation</h4>
the request shall instead proceed as an Update operation and respond
the appropriate status code (see Update section).
</p>
<p>
The create operation for <a>TD</a>s that have identifiers is specified
as `createThing` action in [[[#directory-thing-description]]].
</p>
</li>
<li>
<span class="rfc2119-assertion" id="tdd-reg-create-anonymous-td">
Expand All @@ -928,11 +930,15 @@ <h4>Creation</h4>
Upon successful processing, the server MUST respond with 201 (Created) status
and a Location header containing a system-generated identifier for the TD.
</span>
<span class="rfc2119-assertion" id="tdd-reg-create-anonymous-td-generated-id"></span>
<span class="rfc2119-assertion" id="tdd-reg-create-anonymous-td-generated-id">
The identifier SHOULD be a UUID Version 4 [[RFC4122]].
</span>
That is a random or pseudo-random number which does not carry unintended information
about the host or the resource.
<p>
The create operation for <a>Anonymous TD</a>s is specified as `createAnonymousThing` action in
[[[#directory-thing-description]]].
</p>
</li>
</ul>

Expand Down Expand Up @@ -970,8 +976,10 @@ <h4>Retrieval</h4>
A successful response MUST have 200 (OK) status, contain `application/td+json`
Content-Type header, and the requested TD in body.
</span>
The retrieve operation is specified as `retrieveTD` property in
[[[#directory-thing-description]]].
<p>
The retrieve operation is specified as `retrieveThing` property in
[[[#directory-thing-description]]].
</p>
</p>

<p>
Expand Down Expand Up @@ -1109,7 +1117,7 @@ <h4>Update</h4>
</p>

<p>
This operation is specified as `updateTD` property in
This operation is specified as `updateThing` property in
[[[#directory-thing-description]]].
</p>

Expand Down Expand Up @@ -1159,7 +1167,7 @@ <h4>Update</h4>
</p>

<p>
This operation is specified as `updatePartialTD` property in
This operation is specified as `partialUpdateThing` property in
[[[#directory-thing-description]]].
</p>

Expand Down Expand Up @@ -1205,7 +1213,7 @@ <h4>Deletion</h4>
<span class="rfc2119-assertion" id="tdd-reg-delete-resp">
A successful response MUST have 204 (No Content) status.
</span>
The retrieve operation is specified as `deleteTD` property in
The retrieve operation is specified as `deleteThing` property in
[[[#directory-thing-description]]].
</p>

Expand Down Expand Up @@ -1389,7 +1397,7 @@ <h4>Listing</h4>
</p>

<p>
The paginated list operation is specified as `retrieveTDs` property in
The listing operation is specified as `retrieveThings` property in
[[[#directory-thing-description]]].
</p>

Expand Down Expand Up @@ -1485,7 +1493,7 @@ <h4>Notification</h4>
In particular, the server responds to successful requests with 200 (OK) status
and `text/event-stream` Content Type. Re-connecting clients may continue from
the last event by providing the last event ID as `Last-Event-ID` header value.
This API is specified as `registration` event in [[[#directory-thing-description]]].
This API is specified as `thingRegistration` event in [[[#directory-thing-description]]].
</p>

<dl>
Expand Down

0 comments on commit 733a634

Please sign in to comment.