junction=circular incorrectly rendered as oneway=yes

[Famlam]

What steps will reproduce the problem?

1. View a junction=circular "roundabout" *without* oneway tag
2. Observe oneway arrows

Unlike junction=roundabout, junction=circular doesn't imply oneway=yes

What is the expected result?

No oneway arrows

What happens instead?

Oneway arrows are shown (falsely giving the impression it's a oneway, while routers will/should treat it as a bi-directional way)

Please provide any additional information below. Attach a screenshot if possible.

Example where it went wrong: ​https://www.openstreetmap.org/changeset/111562217
Shown in JOSM as if it were oneway; in reality a oneway, but tagged as bi-directional way.

URL:https://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2021-09-03 03:12:33 +0200 (Fri, 03 Sep 2021)
Build-Date:2021-09-03 01:31:19
Revision:18193
Relative:URL: ^/trunk

Identification: JOSM/1.5 (18193 nl) Windows 10 64-Bit
OS Build number: Windows 10 Home 2009 (19043)
Memory Usage: 874 MB / 1820 MB (521 MB allocated, but free)
Java version: 1.8.0_301-b09, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM
Look and Feel: com.sun.java.swing.plaf.windows.WindowsLookAndFeel
Screen: \Display0 1920×1080 (scaling 1.00×1.00)
Maximum Screen Size: 1920×1080
Best cursor sizes: 16×16→32×32, 32×32→32×32
System property file.encoding: Cp1252
System property sun.jnu.encoding: Cp1252
Locale info: nl_NL
Numbers with default locale: 1234567890 -> 1234567890
Dataset consistency test: No problems found

Plugins:
+ OpeningHoursEditor (35640)
+ SimplifyArea (35640)
+ imagery_offset_db (35640)
+ pt_assistant (1ff2e15)
+ reverter (35732)
+ tageditor (35640)
+ turnlanes-tagging (288)
+ undelete (35640)
+ utilsplugin2 (35792)

Tagging presets:
+ http://mijndev.openstreetmap.nl/~allroads/JOSM/Presets/NL-Fiets.zip

Map paint styles:
- https://josm.openstreetmap.de/josmfile?page=Styles/Lane_and_Road_Attributes&zip=1
- https://josm.openstreetmap.de/josmfile?page=Styles/PublicTransport&zip=1
- %UserProfile%\Documents\tijdelijke bestanden\josm-eigen.mappaint.mapcss
- https://josm.openstreetmap.de/josmfile?page=Styles/Sidewalks&zip=1

Validator rules:
+ %UserProfile%\Documents\tijdelijke bestanden\josm-eigen.validator.mapcss

Last errors/warnings:
- 00007.334 E: Lokaliseren van afbeelding 'bus.png' mislukt

[Famlam]

Example containing a oneway=yes, oneway=no and oneway untagged junction=circular highway

[taylor.smock]

The wiki page contradicts itself.

​https://wiki.openstreetmap.org/wiki/Tag:junction%3Dcircular

From "Important considerations":

Further, generally rotaries and circular junctions have one-way traffic and should have the tag oneway=yes, however a circular junction with bi-directional traffic can be a valid junction to be tagged with junction=circular.

From "How to map":

Add oneway=yes for clarity. As this is a new value for the junction key, many data consumers might not be able to assume the oneway property implicitly.

"How to map" implies oneway=yes, "Important considerations" also implies oneway=yes but also indicates that it should be added.

If you do encounter a bi-directional circular junction, you should add oneway=no as it isn't common (according to wiki page).

Other than that, I'd recommend clearing up the page (I'd start in the Discussion tab, as some people may already consider oneway=yes to be implicit on junction=circular).

See also #19713.

EDIT:
Please come back to this once the wiki page has been updated to reflect how the junction=circular tag is seen/used. You should communicate with other mappers and data consumers when clarifying the wiki page.