WebProtege sometimes generates IRIs that require custom prefix generation when saving to RDF/XML

[matthewhorridge]

Consider the following IRI as a property IRI

http://webprotege.stanford.edu/8gQAvsFVAjAj7tQR77pJGi
�
If this IRI is used in a property assertion then an RDF/XML serializer has to generate a QName from it (so it's possible to have an XML element name that gets expanded to the IRI on parsing). Because this IRI contains a number directly after the last forward slash a render will have to generate something like http://webprotege.stanford.edu/8 as a prefix (say with the prefix wp) and gQAvsFVAjAj7tQR77pJGi as a non-colonized name so that wp:gQAvsFVAjAj7tQR77pJGi can be generated as a QName. This can get quite yucky and should probably be fixed.