Re: Proposed changes to DPV to include Non-Personal Data

Hi,

So I just heard about this proposal from Beatriz today, and I like it!

My opinion is YES to question 1 (although I wouldn't advocate changing the
namespace IRI - instead I would suggest all users of DPV (or users of any
vocab!) adopt internal processes to deal with major version changes to the
vocabs they use. A great example of a popular vocab doing this today (and
for a very long time already!) is 'gist <https://www.semanticarts.com/gist/>',
from Semantic Arts. They regularly release new versions, including major
verison bumps (e.g., they just released version 12.0.0!), and do so without
ever changing the Namespace IRI of gist.

On question two, I'd say YES to Option 1 (but again, no namespace IRI
change - users need to adapt to handle vocab version updates - i.e., they
need to process the `<https://w3id.org/dpv> owl:versionInfo "2" .` triple
of the vocab. The sooner they start doing this the better for everyone, as
changes and updates will (hopefully!) continue well belong this proposal).

One point I'd make (or question really), is if there are new terms required
to satisfy non-Personal Data use-cases that are considered purely
applicable in only non-Personal Data use-cases, then rather than put those
terms in the current DPV Core, or in DPV-PD, perhaps just create a new
DPV-NonPD extension vocab, and put them in there. (I'm not sure if there
are such terms, but I assume there might very well be over time...)

Cheers,

Pat.


*Pat McBennett*, Technical Architect

Contact  | patm@inrupt.com

Connect | WebID <http://pmcb55.inrupt.net/profile/card#me>, GitHub
<https://github.com/pmcb55>

Explore  | www.inrupt.com

-- 
This e-mail, and any attachments thereto, is intended only for use by the 
addressee(s) named herein and may contain legally privileged, confidential 
and/or proprietary information. If you are not the intended recipient of 
this e-mail (or the person responsible for delivering this document to the 
intended recipient), please do not disseminate, distribute, print or copy 
this e-mail, or any attachment thereto. If you have received this e-mail in 
error, please respond to the individual sending the message, and 
permanently delete the email.