Standardization of socket libraries: low-hanging fruit?

[ParkerJones]

Many of the major Prolog implementations have a socket library (at least Sicstus, SWI, Yap, XSB, gprolog, Ciao, Eclipse). Unfortunately, the interfaces vary and this makes socket-based applications non-portable.

There exists a de facto standard API for sockets: Berkeley (BSD) socket API
http://en.wikipedia.org/wiki/Berkeley_sockets

Because there is already a standard, there shouldn't be any need to create a new standard. I wonder if this isn't low-hanging fruit that prolog implementers could converge on.

Any opinions?
Parker