I'm not saying driveway crossing is not unmarked, my thoughts are highway=crossing probably shouldn't even apply at all.

What I just posted on the Talk page is I guess I see a distinction between crossing a road and crossing a driveway, with a crossing on highway=primary you're crossing the road because you're walking along the sidewalk and need to get to the sidewalk on the other side, but with the intersection of a service=driveway and footway=sidewalk, you're never crossing to the other side of the road, you're staying on the same sidewalk, just you reach a point where vehicles may cross your path, so I don't see this intersection node as the same kind of feature. 

https://wiki.openstreetmap.org/wiki/Tag:crossing%3Dunmarked includes driveways as a tricky case and simply acknowledges that sometimes highway=crossing is being used in OSM (it's just documenting usage "as is" in OSM) and also says "if such place would be considered as taggable with highway=crossing".

It's true, as a data consumer, I can check the highway types of the intersection and drop these out if I don't want them, but I can also ask, if they are always unmarked and always should be highway=crossing, why even bother at all?

The reason I noticed these is they started spamming my StreetComplete quests with all the other crossing tags, none of which should apply.