Rename SwzDeviceFeed to DeviceFeed

usdot-jpo-ode / wzdx

The Work Zone Data Exchange (WZDx) Specification aims to make harmonized work zone data provided by infrastructure owners and operators (IOOs) available for third party use, making travel on public roads safer and more efficient through ubiquitous access to data on work zone activity.

Creative Commons Zero v1.0 Universal

89 stars 62 forks source link

Rename SwzDeviceFeed to DeviceFeed #242

Closed j-d-b closed 2 years ago

j-d-b commented 2 years ago

Rename SwzDeviceFeed to WorkZoneDeviceFeed

WZDx defines a SwzDeviceFeed for describing deployed connected ITS devices in work zones such as message signs, cameras, and traffic sensors.

I want to propose reconsidering the name of the feed for the following reasons:

Reasoning

Clarity; no acronyms.
Shorter when written out.
The devices in a SwzDeviceFeed don't have to be in a smart work zone.
The term "smart" will become outdated because eventually all devices will be connected.
No changes to the specification content or structure, just a documentation change.
Better to make the change sooner before it is widely implemented.

Next Steps

Discuss the pros and cons of renaming the feed.
Discuss other possible names, such as DeviceFeed and RoadDeviceFeed

sergebeaudry commented 2 years ago

Agree, Smart Work zone is usually a place where intelligent devices exchange information, process and automaticaly produce come output. EX: sensor data used to trigger Slow/stop message on a PCMS. This feeds includes others elements. EX: PCMS messages that are currently displayed. The mode on an arrowboard to indicate a lane closure. Changing the name now makes sense as the adoption is low

sknick-iastate commented 2 years ago

I would lean towards renaming to the more generic "DeviceFeed". With the WZDx being more generalized to other road events I think this better positions this portion of the WZDx for the future. As noted in the smart work zone device subgroup meeting, the WZDx SwzDeviceFeed has nothing explicitly mentioning the device has to be included in a work zone. I know there are situations outside of work zones where PDMS, sensors or other devices are used that could still benefit data consumers to use the SwzDeviceFeed.

j-d-b commented 2 years ago

I want to add for discussion the option of "RoadDeviceFeed":

Pros

More clear than just "device"—the devices in the feed are on a road.
Allows for devices that are not in work zones.

Cons

RoadDevice is not a term I have heard before

I'm still thinking through which I prefer. I like the simplicity of "DeviceFeed", but out of context "device" is far too general, which is my major concern and why I proposed "RoadDeviceFeed".

j-d-b commented 2 years ago

Based on a WZDx subgroups co-chairs coordination on 2022-03-30, DeviceFeed (fully, the WZDx DeviceFeed) was the preferred name.

j-d-b commented 2 years ago

Completed in #334.