When a user drags text from the web page, it will usually happen that the
instance name contains characters not normally accepted by URIs.
Now, no check is performed by Semantic Turkey on this, and currently
distributed persistence library is Sesame2, which accepts IRIs (accepts,
spaces, unicode chars etc...). This will prevent the ontology to be reused with
other editing tools such as Protege.
I'm thinking about an option for letting ST do a sanitization of strings
prompted for local names of resources being created. This sanitization should
embrace:
1. silent replacement of specific chars with other ones (like spaces with
underscores, or accented chars with their simple equivalents )
2. throw an exception for unicode chars
Original issue reported on code.google.com by stell...@info.uniroma2.it on 25 Jun 2010 at 10:08
Original issue reported on code.google.com by
stell...@info.uniroma2.iton 25 Jun 2010 at 10:08