Keep track of where profile fields come from

[dan-f]

The getProfile function loads a user's solid profile, and defaults to including the extended profile. Some fields in the extended profile may come from the prefs file, which includes private data. If the client wants to update the profile, they may end up either PUTting or PATCHing the public profile endpoint with private fields from the prefs file.

We should come up with an API which keeps track of which fields belong to which resources.

Perhaps we can rename profile.parsedGraph to something like profile.combinedGraph to indicate that the graph has been constituted from several sources.

In addition @dmitrizagidulin and I chatted about adding a profile.updateField(predicate, newObject) method.

[dan-f]

closing this. ended up addressing this in https://github.com/dan-f/modelld