Some potential updates in REST API area

Description

In , there were a couple issues I brought up that were pushed to 2.3.

Here are the two issues:

  1. Do we need to explicitly make clear that all "signals" are actually done using polling when using JSON/REST?

  2. The tables in the 9.10.3 REST API Endpoints section are somewhat ICS-like, in that they define who should implement what, which is something that the XJDF/JDF specs haven't really done in the past. Like, the tables more or less say that Managers never implement support for the Status message, which is a new statement, I believe. I know that there are SHOULDs above, so these tables are only recommendations, but do we need some words to state that in JSON, as in XML, anybody is allowed to implement support for any message they want?

     

Activity

Dennis Carney 
July 18, 2024 at 3:11 PM

7/18/24 call:

For item 1 in the Description: Dennis misunderstood, the signals are sent asynchronously from Device to Controller, so there is no polling for signals.

For item 2 in the Description: The “SHOULD be followed” words are good enough.

Rejected
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Components

Fix versions

Priority

Created May 2, 2024 at 10:22 PM
Updated July 18, 2024 at 3:11 PM
Resolved July 18, 2024 at 3:11 PM