Hi all, I've followed the discussion and I just want to share my experience from teaching an introductory university course on web technologies. When I started in 2018, I had to create the syllabus from scratch: I spent hours checking similar courses and trying to figure what was important or not. It is a pleasure to see that my course covers quite all the objectives of this exams! :-)
Just some random thoughts: * 032.1 What about "Awareness of XML"? Maybe mentioning XML it could create confusion, maybe it could make the candidates aware that not everything with a tag is an HTML file * 035 I'm more a PHP-guy, but I was planning to move my course from PHP to NodeJS in 2021. I'd prefer PHP, but with NodeJS you can move from the client side to the server side without having to learn a new language (and students tend to like that :-) * 035.3 SQL Basics - From my (limited) experience, this could be hardest part for students who never followed an introductory course on databases. If the aim of 035.3 is just giving the idea that a database on the server-side could be used to store and extract data, SELECT (combined with WHERE) could be enough. * It seems JSON is not explicitly mentioned, but I think that candidates should be aware of what JSON is. Bye, Lele On Fri, Mar 27, 2020 at 9:06 PM Fabian Thorns <[email protected]> wrote: > > Dear all, > > thank you all for your feedback and comments, both on the list and in private > conversations. > > Patricia and I have collected all your comments and reviewed/discussed them. > Based on your comments we'd like to suggest the following adjustments of the > objectives draft: > > 031.1 > Add 'functional programming' > > 031.2 > Add 'Understand the principles of APIs' > Add 'Awareness of REST and GraphQL' > Add 'Awareness of single page apps' > Add 'Awareness of MongoDB, CouchDB and Redis' (awareness-level like MySQL and > PostgreSQL) > > 031.3 > Add 'Awareness of sessions and session hijacking' > > 032.3 > Add 'Understand key properties of common media file formats, inlcuding PNG, > JPG and SVG' > Remove '<video> and <audio>, including the controls attribute, <source>, > including the src and type attributes' > > 033.2: > Add 'Understand CSS pseudo-classes' (clarification only, they are already in > there) > Remove [attr], [attr=value], * > Remove a[attr] > Remove a + b; a ~ b; a > b > > 035.1: > Add 'Run a NodeJS application' > Add node index.js > > 035.2: > Add 'Awareness of cross-site Scripting (XSS)' > Add 'Awareness of cross-site request forgery (CSRF)' > > > 033.4 was not changed yet. We have discussed potential ways to reduce this > objective's complexity, but it's not that easy. Removing float would > implicitly remove the ability to define how text floats around other elements > (we won't use it for any other layout aspects, though), reducing the > properties of display or position would either remove rather modern ways to > define the overall layout of a page or not help at reducing the complexity at > all. Please share any ideas you might have on this. > > Also, please take the opportunity to review the current draft one again. The > complete draft is in the wiki at > > https://wiki.lpi.org/wiki/Web_Development_Essentials_Objectives_V1.0 > > The changes made due to your feedback can be seen here: > > > https://wiki.lpi.org/pubwiki/index.php?title=Web_Development_Essentials_Objectives_V1.0&type=revision&diff=5434&oldid=5432 > > If you have any other concerns or thoughts, please put them up for discussion > here or in a direct conversation. Also, if you'd like to help to create exam > contents or learning materials for this (or any other :) exam, please reach > out to me personally, too. > > Take care and stay healthy, > > Fabian > > > On Wed, Mar 11, 2020 at 11:43 PM Bryan Smith <[email protected]> wrote: >> >> Anselm Lingnau wrote: >> > Bryan Smith wrote: >> > > Again, it's important to keep the 'Essentials' aspect in mind. >> > >> > So you believe that, according to the objectives, for a web developer it is >> > “essential” to know about web sockets, what the NodeJS file system NPM >> > module >> > does, and what “inline-flex” means in CSS, but not how to protect one's >> > site >> > against CSRF? >> > >> > Your definition of “essential” must be different from mine ;^) >> >> What I believe is not important. >> >> I.e., if what I believed was important, the Security section of the >> LPI Learning Materials for just the Linux Essentials would be bloated >> 4x its current size, with about 3x the focus as desired by others. ;) >> >> So ... what LPI's Objective/Exam Development believes is what matters. >> >> I'm just saying that 'Essentials' cannot bloat beyond knowing every >> common attack vector of any technology. There must be a 'line drawn' >> somewhere or we might as well just make this a new LPIC-3 level >> objective set and exam. ;) >> >> - bjs >> >> -- >> Bryan J Smith - http://www.linkedin.com/in/bjsmith >> E-mail: b.j.smith at ieee.org or me at bjsmith.me >> _______________________________________________ >> lpi-examdev mailing list >> [email protected] >> https://list.lpi.org/mailman/listinfo/lpi-examdev > > > > -- > Fabian Thorns <[email protected]> GPG: F1426B12 > Director of Certification Development, Linux Professional Institute > _______________________________________________ > lpi-examdev mailing list > [email protected] > https://list.lpi.org/mailman/listinfo/lpi-examdev _______________________________________________ lpi-examdev mailing list [email protected] https://list.lpi.org/mailman/listinfo/lpi-examdev
