Protocol of URI without authority not correctly idenfied

I am currently developing a fsspec driver for a filesystem protocol that does not need/have an authority, such that:

URI = protocol ":" path

is a valid URI.

However, fsspec's split_protocol function seems to assume that an authority is always given, i.e.:

URI = protocol ":" "//" authority path

https://github.com/fsspec/filesystem_spec/blob/6b85a471733124de6e30edf4e16425ee8d30291d/fsspec/core.py#L548-L558

The only exceptions are data (see above) and indirectly file (see here) which are handled specifically.

Are there any issues with supporting also protocols without //authority? E.g. could we just change split_protocol to something like:

def split_protocol(urlpath):
    """Return protocol, path pair"""
    urlpath = stringify_path(urlpath)
    if "://" in urlpath:
        protocol, path = urlpath.split("://", 1)
        if len(protocol) > 1:
            # excludes Windows paths
            return protocol, path
    elif ":/" in urlpath:
        protocol, path = urlpath.split(":/", 1)
        if len(protocol) > 1:
            path = "/" + path
            return protocol, path
    if urlpath.startswith("data:"):
        return urlpath.split(":", 1)
    return None, urlpath

Start at fsspec/core.py around split_protocol, lines 548-558, and compare its handling with the special cases for data and file. Verify the URI forms described in the issue, including protocol:path, authority-based URLs, data URLs, and Windows paths; done means protocol-less-authority URIs are identified without breaking existing cases.