On 8/7/13 2:33 PM, Hugh Glaser wrote:
Thanks Kingsley. I agree with all that, if a) I have an intention of demystifying or enlightening them; b) they have some even slight interest in demystification or enlightenment.Unfortunately in this case neither a nor b apply. I want to do something like get some data out of them, or (WebID) make some files or a service available on the web; They want to use my service.
So doesn't a basic file create, save, and share pattern work? Leave the tool of choice to the user?
I really don't want to have to talk to them and explain anything. They don't want to spend the time listening.
Yes, as I said, you don't get there at first pass.
So yes, do the below if you have an objective to proselytise, but not if you want to spend the minimum time on the activity so that you can achieve an overall objective that can also be satisfied quickly by conventional means. (e.g. email them a username/password for htaccess and ask them to fill in a wordpress page)
So you friends now what htaccess is? If they do, then this stuff should be easy :-)
Clearly we are talking about different contexts.
Maybe different "friend" profiles, which is natural. Kingsley
Best Hugh On 7 Aug 2013, at 19:10, Kingsley Idehen <[email protected]> wrote:On 8/7/13 1:15 PM, Hugh Glaser wrote:"They" certainly don't care about the implementation - it is just about function.Yes, and function (in this context) is the intention (as Ora explains so well) that we apply to the Data. Folks don't care, but they do care. That's the conundrum. Thus, I look to being very flexible when trying to establish rapport en route to demystifying Linked Data. Note, I hit the problem outlined above, frequently, and I look to using a variety of anecdotes and practical demonstrations to get my point across. Thus far, my conclusion is that folks will read and write turtle if you get them through the following sequence: 1. establish what the acquaintance is interested in -- a must-have en route to rapport 2. describe a key item of interest 3. map the concept of describing things to subject->predicate->object patterns in natural language sentence structure 4. initially use pencil and paper to illustrate the entity relationship graph that represents the description -- I use (#Subject)->(#Predicate)->(#Object) instead of: (#Subject)-- Predictate -->(#Object) notation (which is a problematic oversimplification ) . 1-4 require a delicate combination of patience and persistence, you rarely get to #4 on the first try. IMHO. The world has been generally confused about the concept of Data due to narratives crafted by SQL RDBMS vendors (in particular), over the years :-( -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca handle: @kidehen Google+ Profile: https://plus.google.com/112399767740508618350/about LinkedIn Profile: http://www.linkedin.com/in/kidehen
-- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca handle: @kidehen Google+ Profile: https://plus.google.com/112399767740508618350/about LinkedIn Profile: http://www.linkedin.com/in/kidehen
smime.p7s
Description: S/MIME Cryptographic Signature
