incapable
Not in all cases. There is a valid place and space for objective testing.
incapable
Not in all cases. There is a valid place and space for objective testing.
openness
This is a very untroubled view of open and a very euro-centric view of knowledge and sharing. I would argue that there's a lot more to openness in pedagogy that just CC licenses. There are whole social justice perspectives on open which aren't given consideration here.
legitimate peripheral participation
The Community of Practice model is inherently based on an apprenticeship model of learning, where knowledge is more fixed. What about fields where knowledge is emergent?
learning
Why? What is attractive to you about CoI?
isolated when you would rather be in community
I like how you've phrased this, but I'm going to challenge you a bit on social interaction. Do we privilege it fairly over other forms of scholarly activity: https://www.tandfonline.com/doi/abs/10.1080/13562517.2015.1020784
eclectic
Sounds a bit like a grab-bag. I’d find another word.
Source
this is another comment
probably I would have gone for SPLOTBox otherwise because I think the full screen space for reading the detail is a bit better
I can't get this out of my head - it is the one I really want to base my new SPLOT on. I polled 2 people today for their views and they agreed. So now I've started working on porting the autologin changes into it...
Table of Contents
This section could be dropped...
License
I need to change this to match the imported text - it needs to be CC-BY-SA
doesn’t get too wide
I subsequently had an interesting conversation with a colleague along the following lines - one of the ways in which the wealth gap can be kept smaller is through taxation. In this metaphor that might imply restricting innovation. We agreed that this wasn't desireable but that we do all have work to do to ensure we measure the majority of progress using a reasonanle yardstick.
TEL wealth gap
Change has to fundamentally be a do-able thing. We need a twelve step programme because sometimes just working out what the first step to engagement should be is too much. We need to spell this out. Is 23 Things a good model maybe?
Using compliance activities to have conversations about data.
Brian's example was really good here. Fits also with our learning analytics principles and purposes. How do I use this activity within digital literacies more generally. Still think there's merit in an online course for our community in this space. Also see emails about analytics and consent frameworks.
The layer of commentary and marginalia is as vital to me as the main body of the thing.
Also - how can I easily export it and share it in a different format? For example I'd like to be able to PDF a snapshot of a blog post with all the comments inline (kind of like Word I guess) so that I could add it to a professional portfolio.
Only what can be wired together technically
This is where the scope of the NGDLE is absolutely at it's weakest. In this definition Wikipedia, making videos, DOOO, participating in shared spaces like ds106dc or DigiPo are all on the margins.
APIs and standards can massively increase the potential range of stuff we can do, but at the same time there's a fundamental tyranny in them. An API is still someone else's specification. You still need to conform. Maybe sometimes a loose affiliation (a URL) is a more even playing field?
What about Digital Visitors / Residents thinking? Tim Klapdor's blog post from Domains17 was excellent but I worry about the hub / node model in general. We tend to inhabit places, not broadcast out from our own siloed spaces. Community and connection is a thing we feel. Part of editing Wikipedia is being in Wikipedia when I work on it. I'm there.
I see nothing like that in the production of this vision or in much of the subsequent analysis.
I've heard some critique from a recent graduate which was very enlightening. Both their experience of institutional edTech systems and their perception of staff ability to use stuff.
Some more thoughts on the NGDLE, for what it’s worth
Some other thoughts that I never quite managed to get to: Universal design - big tensions around this - suppliers and open source projects will have their own ideas. Best solution might be to get to something skinnable and develop your own institutional GEL - http://gel.ed.ac.uk/ Amy Collier and Jen Ross' work on 'Not-Yetness' - in contradiction to the above and some of the other stuff in the NGDLE vision around interoperability is the need to have some ambiguity and complexity to prompt some of the critical enquiry that we want to see.
Whilst VLE vendors double down on their current positions
See the post in EDUCAUSE review from D2L and the recent interview with Martin Dougimas (summary on the Moodle site). My own conversations with others confirm the same positions. The "Universal design" element of the NGDLE is being interpreted as a need to continue to control and enforce the user experience.
probably at the zenith with this particular one
"Everyone in the streets and the windows said, "Oh, how fine are the Emperor's new clothes! Don't they fit him to perfection? And see his long train!" Nobody would confess that he couldn't see anything, for that would prove him either unfit for his position, or a fool. No costume the Emperor had worn before was ever such a complete success."
what risks being stolen away from us
"All the finest silk and the purest old thread which they demanded went into their traveling bags, while they worked the empty looms far into the night."
teacher except as “programmer” of the curriculum in the system
So in general I don't like the idea of devalueing the teacher's role, but I am still interested in the extent to which it might be possible to automate some aspects of being the teacher - thinking about Sian's work and Teacherbot etc. George Veletsianos, Caroline Rose, OnTask project. Stuff like this.
f support and advice
I know this is a link to a Coursera MOOC. The irony is not lost on me.
simple, lightly managed tools
Jim did another excellent post about this: http://bavatuesdays.com/lets-get-small-splotting-the-future/
very nature are designed to self-destruct
Questions abound about where one would want to enforce self-destruction. At an app container level? or in-app? For blogs in a WPMU config probably at the app level, but in a larger infrastructure, if apps were being popped up via a containerised architecture it would be simpler to enforce at the container level - more uniform. Would we want individual users to be able to see all their 'stuff' and the expiry dates kind of like your ISP account info gubbins?
whilst I probably can’t subscribe to the full breadth of his anarchist vision in my professional practice
I probably can't subscribe to it....much as I might want to. And in my private life? Well, that's another matter entirely.
Talking about this makes for a rubbish conference presentation though
I can totally do a rubbish presentation on this anytime. Just ask.
Remember too that our institutions are in the eye of the storm managing this complexity, because they and they alone carry all the risks around failure.
Which is okay, because we should be in charge of this stuff and dictating the agenda, not blindly following our suppliers lead. It's just that there will be some thresholds to tolerance for cost and risk in this space and when you are managing multiple suppliers and/or open source things at once it's that much more complex and risky.