Comment 11 for bug 1387294

Maybe we should just go with the "location: Database.ConfigLocation" proposal at this point. It solves the problem sensibly and, so far as I've seen, there's still no real use case for arbitrary path handling in QML. Other APIs like ContentHub are similarly opaque even when files are being passed around.