You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
this feature can be used e.g. to rename all occurrences of
myns:Knows
tofoaf:knows
.The text was updated successfully, but these errors were encountered: