The first grid I had created was based on different beverages. I wanted to know what the difference between and the similarities that there were between the different types of beverages. Maybe the topic I choose, but I did not find webgrid to be that informational. So my first impression was a little dim.
The PrinCom grid was able to show the difference between the different beverages. It was easy to see how the relations evloved through the different elements. As beer, wine and highballs were one one end of the scale, coffee and tea were on the other end of the scale, suggesting that these are totally differnt items, yet there was some correspondence between those items such as caffine content and drank more by adults.
In comparing items using the FOCUS, it was easy to see how some items did not even link with others. That is Highball, Wine and Beer all linked together, but did not link with any of the other items, such as tea or coffee. In looking at the constructs, all the items linked together somehow, yet, there was one "Alcoholic - Non-Alcoholic" which did not match with any of the other terms directly.
I found difficulty in developing constructs for these topics as they all seemed to be such different areas, and my initial thought was that the constructs I was using would not show any bindings whatsoever between the items.
When I did the PrinCom on my constructs, it was easy to see how the elements were so spaced out, in almost a perfect star shape. The visual programming element was over in the conflict area, which would suggest that is was quite different compared to the other elements.
The FOCUS shows that there there is quite a difference between all of the elements. The only elements that have any binding qualities is between the Cross-platform GUIs, Visual Programming and Oject Oriented System. For the Contructs, there was again, not great bindings between any of the items and any links that there were had a very low value.
In comparing the grid with Brian Gaines webgrid, it was easy to see that there was no tight correspondance between any of the items. For the elements, the tightest link was in the Visual Programming element, which would have been higher but the difference on one of the constructs caused for the link to be lower. It was interesting to see that the Electronic Publishing element was so different compared to mine, that our correspondance was roughly at a 60% which seemed pretty low,in that category we seemed to differ a lot.
The constructs were a little closer bound on the rating scale, yet the scores were a little lower compared to the elements. The tightest link being between the "Multi-User System - Single-User" and Brian's construct "Communication Technology - Application technology". These to me would seem to be from totally different categories, and I am surprised that they show such a high correspondence. Although, the lowest construct comparison between "Area of Interest - Not interested" and Brian's construct "Application technology - Communication technology", which are 2 totally different topics, and to prove this, had the lowest score on the grid.
The Ethics and Liability issues were a little easier to develop constructs and elements, yet when looking that the items on the print out, there doesn't seem to be much correlation between them.
The PrinCom shows that there is quite a different between the constructs "System Operators Liability - Web Page Owner Liability" and "Web Page Owner Liability - Browser Liability" as they are on opposite diagonals. It was almost expected to see elements like Adult and Child Pornography to have consensus. Also for the elements, Selling Copyrighted Software and Downloading Copyrighted Software to be in the conflict category.
The FOCUS did not show much of a change from what was learned in the PrinCom screen. The only constructs to show a tighter link was "Web Page Owner Liability - System Operators Liability" and "Against proper netiquette - Follows proper netiquette". It is interesting to see that these items are so closely linked yet they are totally different terms. The construct "Web Page Owner Liability - Brower Liability" had a very loose link for all of the elements.
It was interesting to note how the elements were set into 2 different distinctions, and then at a low point of 60 they finally did make a link between one another. The two groupings were quite different, as one was based more on netiquette issues, and one was more illegal types of issues.