The local names of IRIs generated with the mm:uuidEncode and mm:hashEncode directives should always start with a letter
csnyulas opened this issue · 1 comments
The local names of IRIs generated with the mm:uuidEncode
or mm:hashEncode
directives can start with any hexadecimal digit ([0-9a-f]
) (see some examples at the end). Having the local names start with a number can cause problems for different tools parsing or displaying ontologies. We should follow the solution adopted by WebProtege, and prefix the generated local names with a letter (we could use, for example, an "h" for the IRIs generated by hash encoding and a "u" for UUIDs).
Example local names that can be generated by Cellfie at the moment:
bd273e238dc03056fff93c0e1e8de576
2c5f64ab07ccb3e410aa97fc09687cc3
16908b0605f2645dfcb4c3a8d248cef3
d0bb80aabb8619b6e35113f02e72752b
634c9c14-f278-483e-a9e4-6ac296488a1c
b1bf5d63-c13f-4a33-863a-132457c7c896
1fa03695-ab8e-407a-8777-1ca42574f751
df6db73f-ce98-4442-bdd3-b08f41ca767c
Having the local names start with a number can cause problems for different tools parsing or displaying ontologies.
Is this true? I'm under the impression that names in an ontology can start with either a character or number.