- From: Karen Coyle <kcoyle@kcoyle.net>
- Date: Thu, 11 Dec 2014 10:56:53 -0800
- To: public-data-shapes-wg@w3.org
Also, isn't this something that could/should be handled via versioning? If your internal version \= "official version" then you are not in sync, regardless of whether you made a change or your data was modified in some other way. Also, if versioning and provenance are available, you would know that this is your edit of the data. That said, to me this is a clear "just don't do that." If you need something different, create your own extension. kc On 12/11/14 10:48 AM, Arthur Ryman wrote: > Dean/Eric, > > Doesn't this boil down to the question of who you need to interact with? > If it's the rest of the world then you better not change the NAICS codes, > otherwise your app may not work correctly. If it's your own private world, > you can do whatever you want - who could possibly stop you? > _________________________________________________________ > Arthur Ryman > > >>> One of the nice things about RDF is that it is easy to extend one >> of these things without modifying it, which standards like SKOS >> encourage. This mediates the problem in many settings. But what if >> we actually want to change something? Should we be allowed? >> Technically, it is possible, after all, we now have that file behind >> our firewall. >>> >>> My felling is that we should not - what does it mean to call >> something a NAICS code, if you change some of them? That holds >> even more so for things like SKOS and PROV. > > > -- Karen Coyle kcoyle@kcoyle.net http://kcoyle.net m: 1-510-435-8234 skype: kcoylenet/+1-510-984-3600
Received on Thursday, 11 December 2014 18:57:21 UTC