Skip to content
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

project-wide renaming of resources #37

Open
seebi opened this issue Feb 12, 2013 · 2 comments
Open

project-wide renaming of resources #37

seebi opened this issue Feb 12, 2013 · 2 comments
Milestone

Comments

@seebi
Copy link
Member

seebi commented Feb 12, 2013

this feature can be used e.g. to rename all occurrences of myns:Knows to foaf:knows.

@seebi
Copy link
Member Author

seebi commented Sep 18, 2015

👍

@nittka
Copy link
Contributor

nittka commented Sep 18, 2015

Actually, this is not what I meant with simple framework supported refactoring of local names in our phone call.
myns:Knoffs -> myns:knows would be such a refactoring. Only the name changes, not the namespace. Because internally myns:knows is actually 2 references - to the namespace prefix and to the actual subject.

This wanted refactoring would have to adapt both references at once, so it is not low hanging fruit at all. A two-step refactoring by the user (first prefix then the local name) will not work in general - myns will probably used for other subjects as well - and those are not to be renamed.

Simple text replacement "myns:Knows" to "foaf:knows" and fixing the problems afterwards would be the way to go.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants