-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RDF importer should suggest/require ending namespace with slash or hash #2094
Comments
Another approach is to allow administrators to edit the namespace URI when editing a vocabulary. That way they can correct the trailing character, update the schema (e.g. http:// to https://), and make other minor corrections themselves. Currently the URI is read-only, which requires users to edit it directly in the database should they encounter irregularities. We were probably too cautious in our initial decision to exclude the URI from the form. It would open the door to invalid namespaces, but a warning that explains the consequences of changing it should suffice. |
This fix is part of #2093 |
Both the trailing slash and hash on a namespace URL are easy to omit and will usually still result in the right number of vocab members, but can cause issues down the line with things that do care about the actual namespace URL being correct.
The text was updated successfully, but these errors were encountered: