Closed dajbelshaw closed 9 years ago
Worth also noting that on the call we also briefly touched on whether we should call this Web Mechanics or something else? Basically, we're interested in teaching people the nuts and bolts of how the Web works.
There seems to be a clear dilineation between the two being understanding the Web and understanding the Internet.
This will need to be rectified first. We have to encapsulate both the web and the intenet skills under web mechanics. I will play around for a bit. How does that work? Can I just leave comments here or does that mean doing a "pull request?"
Web Mechanics Understand how the Web and internet Work
\ Move **
\ Delete **
Scratch the move of moving the places where your data is hosted. That is clearly necessary for an understanding of web mechanics. My final list:
Web Mechanics Understand how the Web and internet Work
Awesome, thanks @jgmac1106 - look forward to getting additional ideas!
Oh, and pro tip - you can go back and edit comments ad infinitum...
On this week's community call we hacked on the skills underpinning this competency. We ended up with the following:
What's people's thoughts on this?
We really bumped up the complexity of this issue. I would lead with the URLs.
Yep, that's because it's merged with Infrastructure!
Agree that it's (had to) become more complex, though overall it looks a good step in the right direction for 1.5. Nice deft suggestion @jgmac1106 to put the URL's bullet at the top, really eases the flow. Unsure about the lack of reference to the practicalities of 'governance' http://en.wikipedia.org/wiki/Internet_governance. (Interestingly there's no wiki for 'Web Mechanics'!)
Does it make more sense to revise the first one to: Explaining the role algorithms play in creating, managing, etc content on the web.
This way it feeds right into the next skill.
Is it technically true? Are all bots really algorithms? I think we should capture how shaped the information space is for readers.
OK, great work so far. We've got:
I'm not sure about the at rest / in motion part of this at the moment. I like the idea of knowing where your data resides - indeed in the multiple places it could reside - but the 'motion' part feels problematic.
Thanks @jgmac1106 & @jamiea for your help so far! :)
Closing this in favour of issue #19
We decided on the 29th January community call to merge Infrastructure and Web Mechanics. This has been reflected in the repo (#10). Now we need to come up with the skills for this new, re-scoped Web Mechanics competency.
For reference, v1.1: