[Year 12 SofDev] SD key knowledge

Mark KELLY kel at mckinnonsc.vic.edu.au
Thu Mar 10 08:22:45 EST 2011


Hi Andrew.  I just wanted to eliminate the very real possibility that I had
missed a blindingly obvious reason for the key knowledge being included.
>From your reply, it seems that you can't see its relevance either.

In that case, I'll escalate the enquiry and report back...

Cheers
Mark

On 9 March 2011 20:18, Andrew Shortell <shortell at get2me.net> wrote:

>  Hi Mark
>
> [nice ppt btw]
>
> Each and EVERY member of the study design panel should be able to clearly
> and unequivocally, definitively  answer your question because they put it in
> the study design. It did not get there by accident. All members of the panel
> are responsible for the document...
> Members of the panel discuss (and read) the document and have the
> opportunity to clarify anything that they do not understand.
> Just occasionally something gets missed ... That is why we have errata and
> corrections published (and I know all about those!)
>
> If it is not an errata the there must be a definitive answer so let’s just
> ask the panel to provide it rather than us guessing, perhaps not getting it
> in the way that the panel intended  and absolutely missing what the exam
> setting panel might think. We do NOT want the exam setting panel to receive
> a torrent of unwarranted adverse comments.
>
> As mature sensible professionals we should all be working towards a common
> set of understandings that are generously shared (as per this list).
>
>
> [btw – at least a dead dog does not fight you when you stick the cotton bud
> in to its ears! Try doing an alive Alaskan malamute! ]
>
>
> Andrew
>
> --
> Andrew Shortell
>
> Heidelberg Teaching Unit
> Ph 9470 3403
> Fax  9470 3215
>
> c/o Reservoir High School
> 855 Plenty Rd
> Reservoir 3073
>
>
>
> On 9/03/11 1:21 PM, "Mark KELLY" <kel at mckinnonsc.vic.edu.au> wrote:
>
> *SD U3O1 KK04
> Purposes and functions of the physical layer (Layer 1) of the OSI and the
> relationship of the physical layer to the Transmission Control
> Protocol/Internet Protocol model
> *
> For quite some time now I've been avoiding this KK because I'd rather clean
> a dead dog's ears than spend time on the OSI.
>
> But in the end I had to find the cotton buds and get stuck in, and I think
> I have a reasonable overview of the OSI and how TCP/IP maps to it.  (even
> produced a draft slideshow <http://www.vceit.com/slideshows/SD-OSI.ppt> ).
>
>
> But the second part of KK04 really has me baffled: *the relationship of
> the physical layer to the Transmission Control Protocol/Internet Protocol
> model.
> *I know that TCP/IP's Network interface layer maps to OSI's physical layer
> (and the data link layer), but for the life of me I can't see how it's any
> more significant than any of OSI's or TCP/IP's other layers.
>
> Can someone suggest why the relationship between the OSI physical layer and
> TCP/IP is so significant?
> Has this relationship been in the papers?  Has this physical relationship
> resulted in offspring?
> Is Mr OSI going to be on Oprah... or the Jerry Springer show?
>
>
> _______________________________________________
> http://www.edulists.com.au - FAQ, Subscribe, Unsubscribe
> IT Software Development Mailing List kindly supported by
> http://www.vcaa.vic.edu.au - Victorian Curriculum and Assessment Authority
> and
> http://www.vcaa.vic.edu.au/vce/studies/infotech/softwaredevel3-4.html
> http://www.vitta.org.au  - VITTA Victorian Information Technology Teachers
> Association Inc
>



-- 
Mark Kelly
Manager of ICT, Reporting, IT Learning Area
McKinnon Secondary College
McKinnon Rd McKinnon 3204, Victoria, Australia
Direct line / Voicemail: +613 8520 9085, Fax +613 9578 9253
kel at mckinnonsc.vic.edu.au

VCE IT Lecture Notes: http://vceit.com
Moderator: IT Applications Edulist

All generalisations are false, except this one.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.edulists.com.au/pipermail/sofdev/attachments/20110310/49aa3153/attachment.html 


More information about the sofdev mailing list