text:
User talk:Lazyquasar

Its dead Jim.

I will check back in few years. user:lazyquasar

Wikiversity edit
You said: "you inserted a phrase stating that materials were wanted only from teachers not students. I would like this phrase deleted or a correcting bullet added to this page immediately. [...] I go now to see if I can find an admin to make the change" — I've responded to both points at Talk:Wikiversity. - dcljr 08:07, 17 June 2006 (UTC)

Logging in, signing comments
Please remember to log in before you make edits, and sign your posts on talk pages by using three or four tildes:  ~  (3 tildes = no date, 4 tildes = date included). See Help:Editing for more information about wiki syntax. - dcljr 08:19, 17 June 2006 (UTC)

 * I appreciate the information user:Dcljr but I often prefer to be editing anonymously. If someone sees a mistake or has better wording they are welcome to change it.  I experienced a rather severe level of wiki stalking early in Wikipedia's startup and have no desire for all of my inputs to be easily targeted by my editing handle. In my view people often need to learn to evaluate the content rather than who provides it. Lazyquasar 03:17, 18 June 2006 (UTC)

 * At the very least, you should only edit your own user page(s) after logging in. That way people can distinguish your edits from anon vandalism. And for similar reasons, you shouldn't sign your "real" username to a comment you've posted anonymously (see next comment by User:Derbeth). If you sign with tildes, there is never any confusion (unless what you're saying makes it sound like you're posing as "another" user — i.e., your named identity). - dcljr 17:43, 19 June 2006 (UTC)

Staff lounge
These comments were made by an IP, I was not sure if he was you. --Derbeth talk 08:23, 18 June 2006 (UTC)

Wikiversity Instructor
I'm setting up a course of Calculus over at the Mathematics department, if you're interested and wanted to join, that's great. However, I was mainly concerned whether admins would allow me to do this. Your name appeared in a ton of Wikiversity pages, so I thought I could ask you. Fephisto 22:56, 9 July 2006 (UTC)

Thanks for the (quite belated) delay, I went ahead and made the page and the course has already ended, there was a whopping one person (technically two people) that participated. If you're interested in the format or results check it out: School of Mathematics:Calculus.Fephisto 23:50, 19 August 2006 (UTC)

My proposal
Hi Michael - just to say I replied to your comment about my research proposal. Thanks. Cormaggio 13:40, 20 July 2006 (UTC)

title: User talk:Lazyquasar


text:
Talk:Linear Algebra/Matrix operations

Either I am not following the multiplication instructions or the examplein the Eigenvector page does not seem to follow the same rules.

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: Talk:Linear Algebra/Matrix operations


text:
Guide to Social Activity/Driving

Driving is a social activity because the driver must share the road with other drivers and pedestrians. Also there are telephones, drive-through shops, cyclists, etc.

Topics to be added

 * Traffic (In English, traffic refers to the mass movement of cars.)
 * Road rage
 * Accidental deaths
 * Races (on the public streets)
 * Drivers that want to pass every other car
 * Persons who like to buy cars; car culture
 * Persons who hate high petrol prices

title: Guide to Social Activity/Driving


text:
Wikibooks:Assume good faith

Trust and respect for people's good intentions whenever you can help to encourage cooperation and collaboration at Wikibooks.

Assume good faith means to trust other people's intentions are sincere and honest. It is an honor system with expectations that you be polite, respectful, civil, skeptical of your suspicions, and trust that other people are doing likewise. View what is written about you as constructive criticism, and clarify your intentions as you feel the situation warrants.

Honest mistakes can and do happen. Make no assumptions when you address concerns. Even an edit which may seem to add apparent nonsense or removes significant content with no explanation may be an accident, an experiment, or a case where he or she thinks their reasons are self-explanatory. Similarly, when you encounter what you believe to be untrue claims, ask constructive questions and never assume things. Remember intentions can be good even when you do not understand or agree with decisions.

Vandalism is intentionally destructive. The expected assumption of good faith is not a shield against the consequences of bad behavior—Wikibooks Administrators can block users from editing, if there appears to be no other viable recourse. However, problems can often be resolved by contacting the person to politely express concerns and constructive alternatives, like what things he or she can do to help out. Only when reasonable communication attempts fail should you report the user's behavior to Administrators. Note that such reporting is in itself a statement that the assumption of good faith has failed, and thus should not be done prematurely.

Examples
Here are some examples of how to address common concerns:

 * Out-of-scope material added. Move material to the discussion page or to where it is within scope, and explain where the material went in the edit summary.
 * Wanted links added. You can fix links to point to existing pages within the book, temperately point links to external websites with more information, replace links with missing information, or encourage someone else to fix it by adding dewikify to the page. People may need help understanding that books are expected to be self-contained and to include explanations directly.
 * Incorrectly titled. Move the page to the correct title, with a link to the naming policy in the move summary.
 * Inconsistent style. Make a minor edit, replace HTML with wiki markup, add wiki markup to plain text, and make corrections that follow the book's manual of style. Explain what was changed and point to Help:Editing or the book's manual of style in the edit summary.
 * Fixed word variants. People may fix unfamiliar spelling variants of words. However, books should attempt to use a consistent variant of English. Use a minor edit to restore the correct variants of words and point people to a major English dictionary like Wiktionary for variations in spelling.
 * Inaccuracies. You can clarify the facts, or add disputed to the page to encourage discussion.

title: Wikibooks:Assume good faith


text:
Wikibooks talk:Assume good faith

Adapted from en.wiki. This is just common sense, IMHO already in practice in the community, and should be an officially enforced guideline. -- LV (Dark Mark) 22:41, 28 November 2005 (UTC)

 * I believed that the Wikibooks policy should somehow be different from the Wikipedia policy, so I edited it - but now it is a lengthy four-section essay. I added some content specific to Wikibooks, but I might also have misinterpreted "assume good faith" in some way. Other users should edit the policy, because a few users alone cannot represent how the community "assumes good faith". --Kernigh 03:20, 23 January 2006 (UTC)

 * If something is common sense, the last thing we want to do is create a rule to enforce it. If people can understand how something benefits them, the only purpose of also forcing it upon them is to create a hierarchy of power and control. Before we make ourselves little dictators of our virtual domain, perhaps we ought to think about the ramifications. Systems of crime and punishment are a failure state. They are an admission that we weren't able to work congenially as co-editors on a common project — that our little Animal Farm couldn't exist without making some of us "more equal." Do we really want to duplicate the system of punishment and vandalism that exists at Wikipedia? Is their instruction creep working for them? Perhaps we could learn something from our founder. --Zephram Stark 04:11, 7 May 2006 (UTC)

"The problem we are seeing, again and again, is this attitude that some poor victim of a biased rant in Wikipedia ought to not get pissed and take us up on our offer of 'anyone can edit' but should rather immerse themselves in our arcane internal culture until they understand the right way to get things done. I do not know what is going to change, but something BIG has got to happen and SOON about this issue, because the amount of time it is consuming for some of our best editors is getting way out of control."
 * ~Jimbo Wales May 3, 2006 WikiEN-l

Maybe this should not be a policy. AssumeGoodFaith is not policy on Meatball. "Assume good faith" is a good concept, but it might not make sense as a policy. (I do not see how Jimbo Wales's quote above is relevant.) --Kernigh 01:45, 8 May 2006 (UTC)

Move To Reject, and include in Help Namespace
If it is common sense, and the last thing needed it to make it into a policy and enforce it, as it is an advice or guide of conduct it should be moved to a Help page in the help namespace. --Panic 01:20, 10 October 2006 (UTC)

 * Strongly disagree! This isn't some how-to-use-a-talk-page instruction page. It is a statement of what the community sees as unacceptible behaviour. Past experience, from this venue and others like it, shows that when this principle is disregarded communication often soon breaks down and otherwise reasonable people cease to be able to work together.
 * It is imperative that users assume good faith. Repeated disregard of this principle is detrimental to a productive working environment. This policy/guideline will allow the community to discipline those violating it in order to restore more coolheaded debate. --Swift 05:53, 10 October 2006 (UTC)
 * I support making this a policy/guideline, it is common sense to "good" users, but to others this is a way to define proper behaviour. --Cspurrier 23:11, 21 October 2006 (UTC)
 * Of course make this into a policy and guideline, this is quite far the most important thing in any wiki project I think. If two people are in dispute over making a fact or what not, a moderator can mention this guideline to remind them that both are trying to help the wiki not hurt it. Those who want to hurt it probably don´t even have any idea that we have guidelines here. :) --Girdi 18:56, 1 December 2007 (UTC)

 * A policy "or" a guideline ?. I have a problem in making this a policy, as good faith can't be truly verified and so enforced (the basis for a policy) as it depends on the scope and personal observation of an action, it is not black and white or a fixed line in the ground . As for the above action it is more or less dead (last year) and was a response for the above discussion with strong arguments to drop it. I would agree in making it a guideline but the point remains is this something we really need ? Can't this be seen in itself like assuming bad faith for users ?  --Panic 20:08, 1 December 2007 (UTC)

 * I agree with Cspurrier 100% (hello craig, long time no see!). This isn't common sense by any means. In fact, I think natural human behavior is to do exactly the opposite of this. I also agree with Cspurrier and Girdi here that this should likely be made into an official policy (i prefer policy to guideline, since there aren't any situations in which we shouldn't assume good faith, or where it would be acceptable not to). --Whiteknight (Page) (Talk) 20:14, 1 December 2007 (UTC)

 * Well put Whiteknight. I think when two people are arguing, on how an article should be designed, they take it too personal sometimes and start to attack the other contributing user. If they step back a moment and read the Assume Good Faith policy, they would be reminded oh yeah, lets work together for a compromise since we both want to help the wiki not hurt it. That is what makes a good wikiuser. :) --Girdi 20:19, 1 December 2007 (UTC)

 * reset

The problem is that it isn't enforcible (heck WK, me and a lot of users could have been targeted at several times in the past if this was a policy), the only reason to make this a policy it to have a punitive side to perceived abusers and this will open things up for witch hunts, any abuses resulting of activating the policy without "good faith" would it self be a violation, things will indeed be funny if this gets policy status...

"the road to hell is paved with good intentions" but the devil is mostly on the eye of the beholder, without assuming bad intentions how would we be able to identify and call them out as such. I'm not even considering levels of threshold that will not be the same across the community. As a policy this will be a problem not a problem solver. --Panic 20:45, 1 December 2007 (UTC)
 * Panic2k4, you seem like you are quoting evil things and such. A healthy enviornment is those which people are open minded to others' ideas and such. Like now, we are assuming that you are assuming good faith now at the moment for helping Wikibooks, whilst you are stating that it is ok to have bad intentions, according to your quote. Hmm. :) --Girdi 21:00, 1 December 2007 (UTC)

 * Not so... One thing is enforcing something tangible that can be fully attested or agreed upon (like for instance the BeCivil) even that policy has from time to time been used to shut down discussion (not altercations) or when something was said out of context or even in the heat of the moment and at least to my knowledge every attempt to make a point about that policy has failed (it would indeed seem be uncivil to call someone uncivil :), we already have a code of behavior and most people do behave, the problem with this assume good faith thing is that it attempts to enforce a policy on "perceived" intentions that is the problem and I think I have already covered all aspects of attempting to enforce (make policy) of this, and can't see a real benefit (unless we are already working against the policy itself). And yes if you put it into those words that is my point it is not ok but it the less evil to let someone have bad intentions we just have to make sure not to let people act on it and if they to the act itself will be the prof...
 * In simpler and very broad terms, it more or less the problem in starting a war with Iran. (just an illustration of the need for facts, perception can be worked on, I don't want to discuss that topic here, but whatever your side or view you have you should see the problem) --Panic 00:12, 2 December 2007 (UTC)

 * We make it a policy precisely because it's not part of normal human activity to make such an assumption about those around them. Also, since we are in a completely text-based medium, many of those "cues" from your quote above arent available to us. As an example of this, consider how difficult it is to portray something so common as sarcasm on the internet. It is for the purposes of making peoples intentions more obvious artificially that many things on the internet, such as emoticons, have been created. The point here is that all our members are volunteers, and it should be assumed that people are trying to work for the good of the project unless explicitly noted otherwise. We assume that people are doing their best to try and help, even when it appears that they are causing more harm then good. By making this assumption, we decrease the commonality of witch-hunts, and we put more emphasis on helping new users or assisting other wikibookians. Even a bad action can be assumed to be a mistake, mistakes can be corrected, and the people who made mistakes can be taught to avoid them in the future. Without a mandatory assumption of good faith, every mistake and every disagreement descends into another gigantic internet flame war. I think we can all agree that such descentions are not in the common good. --Whiteknight (Page) (Talk) 20:19, 3 December 2007 (UTC)

For myself, I don't see the reason why we need so many policies and guidelines to cover what amounts to the same thing. Why do we need WB:FAITH, WB:BITE, WB:PROFANE, WB:CIVIL and WB:ATTACK? Surely creating one policy or guideline that covers all behavioral issues is enough? Most non-wiki websites have a "Terms of Use" policy that must be followed that covers all these issues and I think its something we could do too. I don't see a need or point in copying Wikipedia's lead on this. --dark lama  17:11, 3 December 2007 (UTC)

 * There are some major areas of overlap in that list. For instance, I think that WB:CIVIL and WB:ATTACK are closely-enough related that they could be merged together. WB:BITE Is also similar, but it's a point that is worth making explicitly. WB:FAITH and WB:PROFANE aren't really covered by any of the others. What you are talking about, I think, is having fewer pages of policy, and not really having fewer policies. That is, if we took all these behavior pages and put them into one, we would have multiple policies on a single page. It's not a question of having more or less policy, but a question of whether we want multiple short pages or a single long page that contains all this information. Any behavior policy (or "policies") should cover the same general points: be nice to each other, assume that things are done in good faith, be supportive and helpful to new users, avoid profanity and obscenity, etc. However you prefer to organize these points, so long as they are made explicit, is of no concern to me. --Whiteknight (Page) (Talk) 20:11, 3 December 2007 (UTC)

 * I go back to the words of User:Zephram Stark above, "If something is common sense, the last thing we want to do is create a rule to enforce it." and reduce it to there is no need to point out the obvious (or be redundant), this will reduce the number of "unneeded" policies. Taking as example the BeBold policy it already does use a reference to good faith in general terms (even if the proposal was linked there), there is no real benefit on providing and enforcing a definition for it, as ultimately it couldn't be attested.
 * Guidelines are a different subject, and using more vague/general notions probably wouldn't create any new problem. Guidelines are mostly informative of the will of the community by having to fallow a formalized process for acceptance, in  using them no one can really abuse or unwilling cause harm with the texts, and so guidelines numbers aren't as problematic,  they serve to refine the understanding Wikibookians have about each others views and on how things should be...  --Panic 21:00, 3 December 2007 (UTC)

 * My point is that assuming good faith is not common sense, and that's exactly why we need a policy to enforce it. Your other quote, above, shows that humam common sense is to base our interpretation of another person's intentions on visual and verbal cues, not to have blind faith that all people have good intentions. You're really making my point for me here.
 * Also, as far as I am concerned, the difference between a "policy" and a "guideline" is nominal at best. The only reason why we have guidelines at all is because it seems to make some people feel more comfortable about making something "official". Historically, policy and guidelines are treated basically the same: Follow them as well as you can, break them only if you have very very good reasons to. And before you jump up on your high horse and claim that this is only my "opinion", I'm basing this on the way things have been done around here. From a practical standpoint, whether we should or not, guidelines and policies have been treated the same. With that in mind, the question here is whether we make this "official" or not. Once we have decided to make it official, we can affix any label that makes you feel good about it. --Whiteknight (Page) (Talk) 00:22, 4 December 2007 (UTC)

 * I (and others) do think that it is common sense to expect that people willing to contribute time/work/money in a Wiki environment to collaborate in writing content for free to be doing so in good faith, even more with all other very similar policies already in place. Good faith can also have a limited scope or be very general (toward the final goal), I can act according to some priorities and goals that are not share by you or even actively opposed (vocalized objection, expressed distrust), the way this clash of opinions is expressed can have a myriad of deferent interpretations depending on the position of the observer regarding the parties or in it's relation to the topics.
 * In any case your reference to my high horse is incorrect, I never claimed to have any higher moral ground or any special power to make any claim, only the right to state what I think when I think is best.
 * The tricky part is simple to demonstrate, for example on this subject of Policy vs Guidelines (and your view versus mine) I can prove that I'm at least not alone and provide some historical and even logical facts, I doubt you could do the same, but I for one accept your right to disagree with my view but again will not subscribe as having the rouge view on this.
 * I will point you again that your view in fact is not consensual and is without supporting facts, from our previous discussion on this (here) I make again a historical reference to User:RobinH using the same distinction I do. Don't doubt I could find more examples like:
 * policy - This refers to an official policy document or some other generally accepted policy.
 * guideline - This refers to a less strict guideline, or convention.
 * From Decision making Revision as of 20:22, 20 October 2005, but this is not the core of what we are addressing here now, and Darklama raised even the point that this text may not even be necessary that has a higher contrast to you validating it as a policy, I for myself would not have a problem making it a guideline and since you see them as almost the same thing our positions are really closer :) this time. --Panic 01:34, 4 December 2007 (UTC)

 * Again, the fact that policy and guidelines have been treated identically is not my "view". In fact, I haven't said what my "view" on the issue is. All I'm saying is that they have been treated identically here. A distinction has never been made, that I know of, between the way policies and guidelines have been administered here. Present me evidence to the contrary, of course, I would love to see it.
 * Also, I would be fine with making it a guideline. That certainly is better then being lost in the hell that we call the help namespace. Better still, I think, would be to make a "Wikibooks Behavior Handbook" or something that would include all our behavior policies in book-form for easy readability. --Whiteknight (Page) (Talk) 01:46, 4 December 2007 (UTC)

 * If you think this subject is important to this discussion I will point out that your view even if not expressed here extensively can be resumed to that there shouldn't be any distinction ("as far as I am concerned, the difference between a "policy" and a "guideline" is nominal at best.") and this was also the basis of our previous discussion on this topic (should versus must), and my claim that only policies are enforcible, to what you disagreed giving the similar status to both. As for evidence of use I already gave it, in discussions and previous text the distinction is prevalent, but to date there hasn't been any practical challenge to it (if so probably done buy myself). Was there any punitive action as result of breaking a guideline ?
 * Ok, so since from all the expressed opinions so far only Darklama expressed a contrary view to this text, let's see if he will be ok with your compromise. In any case the text should be tweaked to reflect some of what was said here, probably simplified, checked against what is now linking to it and altered as a guideline.
 * I'm ok to any action that would make the behavior text more easily available and understandable to Wikibookians, my proposal to use the help namespace was because the proposal seemed bound to be denied and that namespace is were new users will probably look for it (due to our search limitation). --Panic 02:13, 4 December 2007 (UTC)

The case against
I realize that this has not been discussed for quite a while, but with the page remaining classified as a draft proposal there is still a chance it could be promoted at some point, so I thought I'd make my opposition known. "Assume good faith" is a very good principle to follow yourself while working on a collaborative project such as Wikibooks, but having it as a policy or guideline is problematic. Telling someone to "Assume good faith" is often itself a violation of the principle behind that very concept, as it seemingly assumes that bad faith is being assumed—see this Wikipedia essay. Moreover, when exactly is it all right to conclude that someone is not acting in good faith? Then again, what does "good faith" actually mean in the context of a project like this? If, even after being warned, someone continues to believe sincerely that effectively going against community standards improves the project, and acts on that belief, are they acting in good faith or not, and does it matter at that point? The amount of qualifications and clarifications this page would need hardly seem worth the trouble. No personal attacks, Be civil, and Please do not bite the newcomers should be more than sufficient to articulate what is expected as far as interaction with others is concerned, and if they aren't, it is doubtful that a separate "Assume good faith" guideline would be. Belteshazzar (talk) 09:49, 6 April 2010 (UTC)

 * I have yet to look deeply in your post, and even if I also don't believe this was a good proposal and it seems you aren't promoting the readdressing of the text or any specific changes to it, I find somethings on your posts that I don't agree.
 * I don't see any issue on a guideline that promotes the assumption of good faith (on the intentions of others), a guideline is just that it is not enforcible and provides some latitude to exceptions or mitigation. It promotes a common starting ground and can help defuse some rash interpretation of the actions of others before it escalates. (Much like the Please do not bite the newcomers guideline)
 * Establishing good faith doesn't by force imply that bad faith is/was expected, it just promotes an understanding that without bellicose activity any action should be considered well intentioned or at least non destructive, it raises the bar to the response that can be given to any perceived (but unclear) bad action.
 * As someone that has actively engaged in civil disobedience on the project in the past and been target of colluded attacks, I don't wish that anything like this gets passed as an enforcible (policy) but on the other hand see in it some benefits as a proactive extension to the Be civil (that indeed is an extension of No personal attacks as one implies the other). But I assure you that even those policies can have the standing of a guideline at times as they rest in a thin gray line... --Panic (talk) 10:24, 6 April 2010 (UTC)

 * I guess I wouldn't be upset if this became a guideline, as long as it includes a caution about citing itself in discussion. My preference, however would be for it to be an essay. The problem with making it any more than that, besides the points I made above, is that it tells you how to think. Belteshazzar (talk) 17:23, 26 December 2010 (UTC)

 * I think I would be fine with it being an essay for now. I think it could be made a guideline later. I think there should be more emphasis on not telling people to assume good faith. I think people should never tell people to assume good faith, but rather explain specifically the motivation or reasoning behind the belief for thinking a person is not assuming good faith instead. Telling people to assume good faith does not allow the real issues to be addressed. I think the proposal was never intended to address how people should think. I think the proposal should focus more on how the actions/edits/contributions people make should be treated with good faith. In other words the proposal should be related to how people behave towards one another rather than how to think. Maybe this is why it seems to me as though you and I are working against each other to some degree. --dark lama  14:45, 27 December 2010 (UTC)

Off topic material?
It seems to me that the Correcting mistakes section gets a bit off the topic of this page. Yes, mistakes are made in good faith, and that is worth mentioning here, but none of the items on the bulleted list seem particularly likely to be taken as bad faith editing. Perhaps the list could be moved to WB:BITE or somewhere else? Belteshazzar (talk) 16:03, 11 November 2010 (UTC)

 * I think providing some practical examples of how to assume good faith is good to have as part of this page. Seasoned contributors might be less likely to assume bad faith with the examples given than new contributors, but I think proposals are rarely for seasoned contributors to begin with. --dark lama  16:17, 11 November 2010 (UTC)

 * That said, I did notice there was some overlap between the Correcting mistakes and Practical Application sections, and figured a way to reduce the overlap by merging the two sections. Does that help to address your concerns? --dark lama  16:37, 11 November 2010 (UTC)

 * I still don't really see how any of the mistakes in the bulleted list relate to assuming good faith. It doesn't seem likely that anyone will perceive the addition of out-of-scope material as a deliberate attempt to harm the project, and the other four items seem even less likely to be perceived as malicious. Those things could be responded to inappropriately, but that doesn't mean that anyone is assuming bad faith. That is rather an issue for WB:BITE or WB:Editing guideline to address.
 * I also think that the first section's second paragraph now gets off-topic after the first sentence. Often your best choice is to help preserve information by further editing well-intentioned edits as other people may find some value in those edits. Reverting well-intentioned edits can often cause frustration for everyone, cause valuable and potential contributors to leave Wikibooks, and cause fights for control over the current revision to persist. That tells you how to best handle content problems, but that is only peripheral to "Assume Good Faith". Once again, that would be better addressed by WB:Editing guideline or other pages.
 * I feel that this page overall still has an illogical flow, and removing the off-topic material would help to streamline it. Belteshazzar (talk) 21:54, 28 November 2010 (UTC)

 * I think the bulleted list consists of the more frequent examples of problems that people can encounter where it is easy to at times forget to assume good faith. Out-of-scope material and the rest can be deliberate vandalism at times, and people can forget to take a step back and assume good faith when it isn't deliberate, which has lead people to assume bad faith where none existed. That is also why in one form or another the page has mentioned vandalism.
 * Reverting good faith contributions has historically at least been frowned upon at Wikibooks as assuming bad faith and as something that must never be done. I don't actually know this still holds true, but I think its worth including in the proposal for the community to decide on because if it still holds true, it is a major factor in how people believe assume good faith should be applied at Wikibooks. I think that rule is the equivalent of the "zero revert rule" that some people follow at Wikipedia and I've tried to reflect that as I think it applies to assuming good faith here, although probably not as absolute and as enforceable as people might prefer, and to include some of the motivation behind that approach to assuming good faith as I thought was relevant to this proposal. I think this could make sense in WB:BITE too, but I think the problem is this isn't really limited to being polite to new contributors, even though it is one possible factor. I think it isn't really about guidelines for editing either in that its more to do with Wikibooks' etiquette on assuming good faith than it does with editing specifically.
 * I have no objections to trying to improve the logical flow of the page, but I think its important to preserve the information included in the proposal within the proposal, one way or another, unless there is a consensus that both the bullet list and the rest doesn't belong here. dark lama  02:44, 29 November 2010 (UTC)

 * I will note that the bulleted list of mistakes was long ago removed from this page's "unstable branch" and hasn't been re-added, so whether it has consensus to be here is questionable. I would agree that this page should have some reference to not assuming vandalism, but I think the details should be left to WB:VANDALISM, WB:Editing guideline, and possibly WB:BITE. Belteshazzar (talk) 09:48, 23 December 2010 (UTC)

 * I think the diff you pointed to represents the initial fork of this draft where another proposal was to be drummed out as an alternative to this one due to incompatible and conflicting opinions. At some point an attempt was made to incorporate perspectives from that other draft back into this one and to find a balance between the two so the community could agree on a single proposal instead of being split in two on what the policy should be. This occasionally happens and can be a good way to allow people to iron out proposals which appear to conflict with each other and look for a middle ground later. I could point out things in this draft or that draft to try to prove consensus or lack of consensus, but the fact is neither draft actually represents any sort of official consensus yet, otherwise one would already be a policy/guideline and not just a draft. --dark lama  16:23, 23 December 2010 (UTC)

 * I wasn't trying to say that the absence of the bulleted list from the fork proves that it doesn't have consensus to be here, just that it calls that into question. I won't try to remove the bulleted list without feedback from more users, but my opinion is that it shouldn't be here. Belteshazzar (talk) 17:09, 26 December 2010 (UTC)

Applying WB:AGF to itself
Regarding this edit, I think the problem with this logic is that "when people are mistaken, treat it as an honest mistake" doesn't quite get the point across. If you are inclined to think that someone is intentionally spreading misinformation, "when people are mistaken" doesn't apply to the situation in your mind. "When you encounter misinformation" is a more practical characterization in this regard. Belteshazzar (discuss • contribs) 21:20, 17 January 2011 (UTC)

 * I think the wording needs to be more neutral in tone. AGF should attempt to demonstrate through its wording how to assume good faith. Patent nonsense and intentionally spreading of misinformation is to assume a person does not have good intentions. The wording may also cause people to entertain ideas they had not thought of before. I doubt examples of changes people disagree with are needed too, because in general changes should not be treated as vandalism. Also there may be no need to revert a revision in order to correct mistakes. I think a far better assumption overall is that any changes are meant to improve factual accuracy, and more changes may be needed in order to achieve factual accuracy. --dark lama  14:28, 19 January 2011 (UTC)

AGF and vandalism
To let people know, the unstable branch of this page now almost directly contradicts what we say here regarding vandalism. Belteshazzar (discuss • contribs) 07:00, 18 April 2011 (UTC)

Any idea why this is pending approval?
I've seen pretty much everybody follow this policy. 15:28, 28 January 2023 (UTC)

title: Wikibooks talk:Assume good faith


text:
User talk:210.19.115.7

You have been temporarily blocked from editing Wikibooks. You were warned several times that linking to commercial sites is not allowed. If you wish to make useful contributions, you are welcome to come back after the block expires.

title: User talk:210.19.115.7


text:
Blender 3D: Blending Into Python/Features

Here is the temp location for features Campbell and Vince from MetaVR wish to add for improved modelling in simulation.

 * Vert Select to UV Selection.
 * UV Window, Align weld- to be able to welt to the left, right,top,bottom.
 * Relax vertex to surrounding.
 * Relax vertex- make the vertex evenly spaced and fit the surrounding faces/verts.
 * Rotate along edge.
 * Projection UV mapping modifier. (use cameras?)
 * Move uv island to another edge non connected edge
 * BuildingGenerator: BuildingGenerator [[image:50%.svg]] — building Generator


text:
Template:Blender 3D: HotKeys/Multiple Windows/Multiple Modes/F11

F11 - shows render window.


text:
Talk:Communication Theory/The Frankfurt School

This is a very interesting read. I think some of the usage could be made a bit more, let's say, consistent with English philosophical thinking. Continental thinkers are notoriously obscure in the construction of their German syntax and Frankfurt critical theorists were among the most dense, especially Adorno. It is not easy to wade through a stack of their writing and then write in the crisp, concise style that English readers expect, so the writers of this book get high marks despite my collegial "critical" remarks.Geofferybard (discuss • contribs) 05:04, 19 May 2011 (UTC)

CAT
What hard about that subject Onthatile Khumo (discuss • contribs) 14:35, 6 February 2023 (UTC)

Accounting equation
The liabilities Onthatile Khumo (discuss • contribs) 14:37, 6 February 2023 (UTC)


text:
United States Government/Constitution Preamble

THE PREAMBLE
We the people of the United States, in Order to form a more perfect union, establish justice, insure domestic tranquility, provide for the common defence, promote the general welfare, and secure the Blessings of Liberty to ourselves and our posterity, do ordain and establish this constitution for the United States of America.

Purpose and Effect of the Preamble

 * Although the preamble is not a source of power for any department of the Federal Government, the Supreme Court has often referred to it as evidence of the origin, scope, and purpose of the Constitution. "Its true office," wrote Joseph Story in his Commentaries, "is to expound the nature and extent and application of the powers actually conferred by the Constitution, and not substantively to create them. For example, the preamble declares one object to be, ‘provide for the common defense.’ No one can doubt that this does not enlarge the powers of Congress to pass any measures which they deem useful for the common defence. But suppose the terms of a given power admit of two constructions, the one more restrictive, the other more liberal, and each of them is consistent with the words, but is, and ought to be, governed by the intent of the power; if one could promote and the other defeat the common defence, ought not the former, upon the soundest principles of interpretation, to be adopted?"


text: User talk:24.249.52.136

title: User talk:24.249.52.136


text: Japanese/Reader/第三夜/Part 1

title: Japanese/Reader/第三夜/Part 1


text: Japanese/Reader/第三夜/Part 2

title: Japanese/Reader/第三夜/Part 2


text: Japanese/Reader/第三夜/Part 3

title: Japanese/Reader/第三夜/Part 3


text: Japanese/Reader/第三夜/Part 4

title: Japanese/Reader/第三夜/Part 4


text: Japanese/Reader/第三夜/Part 5

title: Japanese/Reader/第三夜/Part 5


text: Japanese/Reader/第三夜/Part 6

title: Japanese/Reader/第三夜/Part 6


text:
United States Government/Constitution Authorization

Text

 * AUTHORIZATION
 * HISTORICAL NOTE PUBLIC LAW 91-589, 84
 * STAT. 1585, 2 U.S.C. § 168

 * JOINT RESOLUTION Authorizing the preparation and printing of a revised edition of the Constitution of the United States of America--Analysis and Interpretation, of decennial revised editions thereof, and of biennial cumulative supplements to such revised editions.

 * Whereas the Constitution of the United States of America--Analysis and Interpretation, published in 1964 as Senate Document Numbered39, Eighty-eighth Congress, serves a very useful purpose by supplying essential information, not only to the Members of Congress but also to the public at large;

 * Whereas such document contains annotations of cases decided by the Supreme Court of the United States to June 22, 1964;

 * Whereas many cases bearing significantly upon the analysis and interpretation of the Constitution have been decided by the Supreme Court since June 22, 1964;

 * Whereas the Congress, in recognition of the usefulness of this type of document, has in the last half century since 1913, ordered the preparation and printing of revised editions of such a document on six occasions at intervals of from ten to fourteen years; and

 * Whereas the continuing usefulness and importance of such a document will be greatly enhanced by revision at shorter intervals on a regular schedule and thus made more readily available to Members and Committees by means of pocket-part supplements: Now, therefore, be it

 * Resolved by the Senate and House of Representatives of the United States of America in Congress assembled, That the Librarian of Congress shall have prepared—

 * (1) a hardbound revised edition of the Constitution of the United States of America--Analysis and Interpretation, published as Senate Document Numbered 39, Eighty-eighth Congress (referred to hereinafter as the Constitution Annotated), which shall contain annotations of decisions of the Supreme Court of the United States through the end of the October 1971 term of the Supreme Court, construing provisions of the Constitution;

 * (2) upon the completion of each of the October 1973, October 1975, October 1977, and October 1979 terms of the Supreme Court, a cumulative pocket-part supplement to the hardbound revised edition of the Constitution Annotated prepared pursuant to clause (1), which shall contain cumulative annotations of all such decisions rendered by the Supreme Court after the end of the October 1971 term;

 * (3) upon the completion of the October 1981 term of the Supreme Court, and upon the completion of each tenth October term of the Supreme Court thereafter, a hardbound decennial revised edition of the Constitution Annotated, which shall contain annotations of all decisions theretofore rendered by the Supreme Court construing provisions of the Constitution; and

 * (4) upon the completion of the October 1983 term of the Supreme Court, and upon the completion of each subsequent October term of the Supreme Court beginning in an odd-numbered year (the final digit of which is not a 1), a cumulative pocket-part supplement to the most recent hardbound decennial revised edition of the Constitution Annotated, which shall contain cumulative annotations of all such decisions rendered by the Supreme Court which were not included in that hardbound decennial revised edition of the Constitution Annotated.

 * Sec. 2. All hardbound revised editions and all cumulative pocket-part supplements shall be printed as Senate documents.

 * Sec. 3. There shall be printed four thousand eight hundred and seventy additional copies of the hardbound revised editions prepared pursuant to clause (1) of the first section and of all cumulative pocket-part supplements thereto, of which two thousands six hundred and thirty-four copies shall be for the use of the House of Representatives, one thousand two hundred and thirty-six copies shall be for the use of the Senate, and one thousand copies shall be for the use of the Joint Committee on Printing. All Members of the Congress, Vice Presidents of the United States, and Delegates and Resident Commissioners, newly elected subsequent to the issuance of the hardbound revised edition prepared pursuant to such clause and prior to the first hardbound decennial revised edition, who did not receive a copy of the edition prepared pursuant to such clause, shall, upon timely request, receive one copy of such edition and the then current cumulative pocket-part supplement and any further supplements thereto. All Members of the Congress, Vice Presidents of the United States, and Delegates and Resident Commissioners, no longer serving after the issuance of the hardbound revised edition prepared pursuant to such clause and who received such edition, may receive one copy of each cumulative pocket-part supplement thereto upon timely request.

 * Sec. 4. Additional copies of each hardbound decennial revised edition and of the cumulative pocket-part supplements thereto shall be printed and distributed in accordance with the provisions of any concurrent resolution hereafter adopted with respect thereto.

 * Sec. 5. There are authorized to be appropriated such sums, to remain available until expended, as may be necessary to carry out the provisions of this joint resolution.

 * Approved: 1970-12-24.


text: Template:Japanese/第三夜Nav

title: Template:Japanese/第三夜Nav


text:
Handbook of Genetic Counseling/Dysmorphic Features - Developmental Delay

Dysmorphic Features - Developmental Delay

Contracting

 * Introduce myself and counselor
 * Explain role of counselor is supervisory
 * Discuss the reason for referral
 * Do you know why you are here today?
 * Elicit prior knowledge
 * Assess parental concerns
 * Any further plans for children?
 * I understand you had a previous child that was stillborn?
 * Set goals for the session/overview what will happen
 * Physical exam by Dr.
 * Address parental concerns
 * Discuss any further testing
 * Arrange for follow up

Intake and Family History Update

 * Pedigree
 * Interim History
 * Illnesses
 * Hospitalizations
 * Surgeries
 * Current medications
 * Review of systems
 * Diet/feeding
 * What he eats, how much, how often
 * Skin
 * Rashes, birthmarks, dry skin
 * CV
 * Heart murmur, special heart tests (EKG)
 * Endo
 * Hormone problems, diabetes, thyroid disease, weight gain or loss
 * GU
 * Kidney anomalies, renal ultrasound
 * MS
 * Muscle weakness, scoliosis, bone fractures
 * ENT
 * Sinusitis, ear infection, hearing loss
 * Psych
 * Temperament, sleeping patterns
 * GI
 * Diarrhea, constipation
 * Allergy to food, medicine, etc.
 * Eyes
 * Visual problems, cataracts
 * Neuro
 * Seizures, brain abnormality
 * Resp
 * Colds, infection, wheezing, pneumonia
 * Heme
 * Bleeding disorders
 * Recent tests and procedures
 * Developmental Assessment
 * Currently 1 year, 2 weeks old
 * Skills for a 1 year old
 * Pulls self to standing, may step with support
 * Picks things up with thumb and one finger
 * Stacks two blocks, gives toy on request
 * Gives affection
 * Follows simple directions accompanied by gestures
 * May say 2 or 3 words
 * Skills for a 9 month old
 * Sits alone, changes position without falling
 * Plays with 2 objects at the same time
 * Says mama & baba
 * Skills for 6 month old
 * Sits with minimal support, rolls from back to stomach
 * Transfers object from hand to hand and hand to mouth
 * Babbles, more than 2 sounds
 * Skills for 15 month old
 * May walk without support
 * Stacks 2 blocks
 * Vocalized up and down like conversation; may say 4 or 5 words
 * Some self-feeding
 * Any early intervention programs?
 * Psychosocial assessment
 * Physical exam
 * Macro/microcephaly?
 * Height and weight?

Differential Diagnosis

 * Input criteria using London Dysmorphology Database:
 * Hypertelorism; posteriorly rotated ears; epicanthic folds; developmental delay
 * Output:
 * Braegger: ischiadic hypoplasia; renal dysfunction; immunodeficiency
 * Autosomal recessive
 * Conductive hearing loss, intrauterine growth retardation, microcephaly, syndactyly
 * Cardio-Facio-Cutaneous (CFC) syndrome
 * Common features with Noonan syndrome
 * Pulmonary stenosis is common
 * Enlarged liver and spleen, mild to moderate mental retardation in 80%, macrocephaly, sparse, curly and/or slow-growing hair, lack of eyebrows and eyelashes, abnormal skin lesions varying from severe atopic dermatitis to hyperkeratosis/ichthyosis-like lesions
 * Hypotonia, strabismus, brain anomalies including hydrocephalus, cortical atrophy, hypoplasia of frontal lobes and/or brain stem atrophy
 * Farag: hypertelorism; hypospadias; tetralogy of Fallot
 * Autosomal recessive
 * Mental retardation, also other cardiac defects including PFO, PDA, and absent pulmonary valve
 * Fetal Alcohol Syndrome
 * Low birth-weight
 * Hypotonia, microcephaly, FTT, smooth philtrum with a thin upper lip
 * Cardiac lesions in 1/3 of cases: VSD is most common
 * Hurst: congenital heart disease; choanal stenosis; short stature
 * Autosomal recessive
 * ASD and VSD; microcephaly, small nose, long philtrum, thin upper lip
 * Morillo-Cucci: short stature, mental retardation; unusual face
 * Hypertelorism, ptosis, myopia, strabismus, antimongoloid palpebral fissures
 * Hyperextensible joints; bilateral 5th finger clinodactyly
 * Multiple circumferential skin folds (Michelin baby)
 * Autosomal dominant; heterogeneous condition.
 * Marked annular skin creases on the limbs with underlying nevus lipomatosus
 * Hemihypertorphy, CP can be seen, micrognathia, pectus excavatum, scoliosis, hypoplastic scrotum, and retractile testes.
 * Multiple pterygium syndrome
 * Autosomal dominant
 * Ptosis, antimongoloid eye slant, scoliosis, camptodactyly, vertebral anomalies
 * Small stature, cryptorchidism, normal intelligence
 * Noonan syndrome (Turner-like syndrome)
 * 1/1000 and 1/2300 live births
 * Short stature, short neck with webbing, cardiac anomalies, characteristic chest deformity (pectus excavatum), widespaced nipples, characteristic facies, 35% mental retardation
 * Cryptorchidism, pulmonic stenosis, bleeding disorders
 * Polyhydramnios in 33% of cases and feeding difficulties in 75%
 * Noonan-like/multiple giant cell lesion syndrome
 * Cherubism and polyarticular pigmented villonodular synovitis
 * Opitz-BBB syndrome
 * X-linked and AD (indistinguishable clinically)
 * Hypertelorism, hypospadias, CL/CP, imperforate anus (although rare), hypotonia
 * Congenital heart defect, cryptorchidism, bifid scrotum, mental retardation
 * Hernias, micrognathia, broad flat nasal bridge
 * Pascual-Castroviejo: cerebro-facio-thoracic dysplasia
 * Mental retardation, narrow forehead, bushy eyebrows, triangular-shaped mouth with downturned corners, short neck with low posterior hairline, brachycephaly, maxillary hypoplasia, and multiple skeletal anomalies.
 * Pashayan: MR; truncal obesity, webbed neck, blepharophimosis
 * Simple philtrum, thin upper lip, flat, broad nasal bridge, short stubby nasal tip, hypertelorism, developmental delay
 * Glaucoma requiring enucleation.
 * Pterygium colli-mental retardation-digital anomalies
 * Pterygium colli, ptosis, upslanting palpebral fissures, hypertelorism, broad nasal base and bridge, epicanthus inversus, syndactyly of toes
 * Ritscher-Schinzel: Dandy-Walker malformation of the brain; atrioventricular septal defect
 * Hypertelorism, downslanting palpebral fissures, low-set ears, postnatal growth retardation, cardiac defects, DD
 * Rubinstein-Taybi syndrome
 * Microcephaly, antimongoloid eye slant, hypertelorism, long eyelashes, milt ptosis, prominent and/or beaked nose with or without nasal septum extending below alae nasi (100%), thumbs are broad, occasionally bifid, cardiac defects in 25%, broad great toes in 100%, ear infections are common
 * Sleep problems possibly due to sleep apnea, feeding difficulties are common

Resources

 * The family Village
 * www.familyvillage.wisc.edu


text:
User:Dragontamer/wikiversity

Yeah... talk here

title: User:Dragontamer/wikiversity


text:
Handbook of Genetic Counseling/Dysmorphic Features - Hypotonia

Dysmorphic Features - Hypotonia

Preparation

 * Call Cytolab and see if FISH for Prader-Wili was ever ordered for client.

Contracting

 * What are your concerns? I know that when we talked you mentioned the difficulty in feeding that he experienced before. Is there anything else?
 * I've read your chart and looked over the information you told me over the phone, but pretend I don't know anything and tell me why you are here today.
 * Review family history
 * Review medical history
 * Physical exam
 * Answer any questions/ order any tests

Review medical history

 * Mom, how long were you in the hospital following birth?
 * Was the client "floppy" at birth?
 * Can you describe the floppiness and when it began to improve
 * What doctors does the client see?
 * Neurology…how often and last visit?
 * Pediatrician
 * Is the client on any medications?
 * Has the client ever had PT, ST, OT?
 * Has the client ever been involved in an Early Intervention program?

Describe what we think may be going on

 * Any genetic conditions (prader-wili)
 * multifactorial inheritance
 * sporadic events

Wrap up session

 * Answer any questions mom might have
 * Set up method of returning results to mom
 * Set up follow-up appointment?
 * Get referrals per instructions from Dr.


text:
Handbook of Genetic Counseling/Echogenic Bowel

Echogenic Bowel

What is it?

 * when, on ultrasound, the fetus' bowel appears to have more echogenicity than the liver, or similar or greater echogenicity than the surrounding bone
 * can be a transient feature

What does it mean?

 * most likely etiology is intra-amniotic bleeding and swallowing of the stained fluid by the fetus, followed by its accumulation within the meconium
 * can be indicative of a chromosome abnormality (e.g., Down Syndrome, Cystic Fibrosis)
 * is most often a non-specific finding (seen in fetuses with intestinal obstruction/blockage, congenital cytomegalovirus infection, growth restriction)
 * has been reported as a normal variant during the second trimester
 * can also be indicative of early ascites, fetal hypoxia, placental insufficiency, and meconium peritonitis

What are the risks?

 * the risk of Down Syndrome in fetuses with isolated hyperechogenic bowel is 1.4%
 * in "high risk" women (abnormal MSAFP screen, family history of Cystic Fibrosis, and/or AMA), echogenic bowel is associated with:
 * Cystic Fibrosis in 3% of fetuses
 * chromosome abnormalities in 12.4% of fetuses
 * (most data has been collected from this high risk group)
 * 12.5% of fetuses with Down Syndrome have been reported to have echogenic bowel
 * the only abnormal ultrasound finding in 41% of these cases
 * chromosomal abnormalities are more often diagnosed when there are findings in addition to hyperechogenic bowel (multiple abnormalities)

What should be done?

 * future ultrasounds should be performed to determine if the finding is transient and to monitor growth
 * all women with this ultrasound finding should be counselled and their risk factors assessed to determine whether they should undergo an amniocentesis for fetal karyotype, parental CF mutation studies, and assessment of the presence of a congenital infection

Reference

 * Genetic Disorders and the Fetus. 4th Edition Ed. Aubrey Milunsky. 1998


text:
User talk:Yeahitslokesh

Welcome to Wikibooks!

I noticed your edit to Template:Bookshelves (all), which effectively removed five bookshelf templates from the Main Page. I reverted (undid) your edit.

Please use the Sandbox for test edits and experiments. Edits to the sandbox do not harm other pages on Wikibooks. --Kernigh 03:59, 29 November 2005 (UTC)

title: User talk:Yeahitslokesh


text:
Handbook of Genetic Counseling/Ehlers-Danlos Syndrome

Ehlers-Danlos Syndrome

Contracting

 * Introductions, acknowledge any prior contact
 * Assess main concerns of patient
 * Why are they visiting Genetics today?
 * What do they hope to gain from the session?
 * Assess knowledge of diagnosis -- any questions?
 * Overview of today's session
 * Restate patient's concerns
 * Medical history, family history, physical exam, genetics, recurrence risk, testing options and limitations

Pediatric Intake

 * Pregnancy and Medical History
 * umbilical/unguinal hernia? prematurity? cervical incompetence?
 * Developmental History
 * learning disabilities?
 * Family History
 * heart problems? joint hypermobility? stretchy skin? fragile skin? easy to scar? scoliosis? easy bruising? congenital hip dislocations? stroke? umbilical/inguinal hernias? early loss of teeth?

Incidence and Carrier Frequency

 * no well-founded figures for prevalence
 * for all forms, estimates of 1/5000 have been made

Clinical Features
have joint laxity and dermal features in common **
 * a group of clinically diverse inherited connective tissue disorders that
 * Classical (Type I and Type II)
 * Major diagnostic criteria
 * Hyperextensibility of the skin
 * Widened atrophic scars
 * Joint hypermobility
 * Can lead to osteoarthritis in the 3rd or 4th decade
 * Other features
 * Poor wound healing
 * ½ of affected individuals are delivered up to 1 month premature due to premature rupture of fetal membranes
 * Some have cardiac abnormalities
 * Mitral valve prolapse
 * Aortic root dilation with occasional rupture
 * Scoliosis
 * Pes planus (flatfoot)
 * Molluscoid pseudotumors (calcified hematomas) may be associated with scars
 * Inheritance
 * Autosomal dominant single-gene disorder
 * Etiology
 * A major cause is mutations in type V collagen
 * At least 3 loci are involved
 * Biochemical Defects
 * Thickened collagen fibrils in skin as well as "cauliflower" deformities of collagen fibrils
 * Mutations in COL5A1 and COL5A2 have been seen in some families
 * Testing
 * No biochemical or molecular based testing methods have been devised to provide reliable results
 * Hypermobility Type (Type III)
 * Primary characteristics
 * Hyperextensibility of large and small joints
 * Soft, velvety skin
 * Other features
 * May have normal scarring but stretchy skin
 * Dilatation and/or rupture of the ascending aorta
 * Scoliosis
 * Pes planus
 * Inheritance
 * Autosomal dominant single-gene disorder
 * Diagnosis is clinical
 * Vascular Type (Type IV)
 * Major diagnostic criteria
 * Characteristic facial appearance
 * Thin, delicate, "pinched" nose
 * Thick lips
 * Hollow cheeks
 * Some have staring appearance due to decreased adipose tissue below the eyes
 * Thin, translucent skin
 * In fair-skinned individuals, subcutaneous vasculature is easily visible beneath the skin
 * Arterial/intestinal/uterine fragility or rupture which can be life threatening
 * Extensive bruising
 * Other characteristics
 * Normal scar formation
 * May be increased incidence of stroke
 * Acrogeria (aged appearance to extremities, particularly hands)
 * ¼ of affected individuals experience a significant medical problem by age 20
 * Median age of death is 48 years old
 * Inheritance
 * Autosomal dominant as demonstrated by linkage analysis
 * Etiology (COL3A1 gene)
 * Dominant mutations in the gene for the pro-alpha 1 chain of type II collagen
 * Caused by abnormal synthesis, structure, or secretion of type II collagen
 * 50% have new disease-causing mutations
 * Over 250 COL3A1 disease-causing mutations have been found
 * Testing
 * Can be reliably accomplished by analysis of type III procollagen and collagen chains harvested from cultured dermal fibroblasts
 * Kyphoscoliosis type (type VI)
 * Key features
 * Neonatal onset of joint laxity
 * Kyphoscoliosis (lateral curvature of the spine accompanying an anteroposterior hump)
 * Muscle hypotonia
 * Other features
 * Ocular fragility
 * Skin fragility
 * Easy bruisability
 * Dermal hyperextensibility
 * Risk for arterial rupture
 * Most have radiologically detectable osteopenia (decreased bone density), but pathological fractures are rare
 * Intelligence is normal
 * Lifespan may be normal
 * Etiology
 * Caused by deficient activity of the enzyme procollagen lysine hydroxylase
 * Inheritance
 * Autosomal recessive
 * Testing
 * Diagnosis depends on demonstration of increased ratio of deoxypyridinoline to pyridinoline crosslinks in urine measured by HPLC
 * Mutation analysis of the PLOD gene that encodes the enzyme procollagen lysine hydroxylase is available on a research basis
 * Carrier testing is not available
 * Arthrochalasia type (types VIIA, VIIB)
 * Major criteria
 * Severe generalized joint hypermobility
 * Congenital bilateral hip dislocations that are difficult to repair surgically
 * Other features
 * Tissue fragility including atrophic scars
 * Kyphoscoliosis
 * Skin hyperextensibility
 * Etiology
 * Caused by a failure to accomplish normal cleavage of the amino-terminal propeptide of type I collagen in all tissues
 * Mutations that remove exon 6 in COL1A1 and COL1A2 are seen
 * Inheritance
 * Autosomal dominant
 * Testing
 * Demonstration of exon 6 skipping in cDNAs of COL1A1 or COL1A2 followed by mutational analysis
 * Dermatosporaxis type (type VIIC)
 * Very rare form of EDS
 * Diagnostic Features
 * Dermal fragility: the skin is lax but not stretchy
 * Other features
 * Joint dislocation is usually not a feature
 * Infants have been reported with premature rupture of membranes and umbilical/inguinal hernias
 * Etiology
 * Caused by failure to cleave off the amino-terminal propeptide of type I collagen due to deficiency of the procolagen I N-peptidase gene
 * Inheritance
 * Autosomal recessive
 * Other variants (VIII, V X-linked, X)
 * Type VIII
 * Rare autosomal dominant condition
 * Characterized by soft, hyperextensible skin, abnormal scarring, easy bruising, hyperextensible joints and generalized periodontitis
 * Resembles type I, but is distinguished by early loss of teeth and characteristic purplish discoloration of scars on the shins
 * Molecular basis is unknown
 * Not clear if it is truly distinct from classical form
 * Type V X-linked
 * Similar to mild classical type
 * X-linked recessive inheritance
 * Unknown molecular defect
 * Type X
 * Joint hyperextensibility, mitral valve prolapse, easy bruising, poor wound healing, clotting disorder
 * Clotting studies showed a defect in the platelet adhesion that is normally observed in response to exposure of platelets to collagen
 * May be caused by a defect in fibronectin

Management and Treatment

 * Pregnancy
 * All cases should be referred to high-risk obstetric practice
 * Prematurity is a concern
 * Cervical incompetence can be treated with bed rest and the Trendelenburg position
 * Musculoskeletal
 * P/T can improve strength of muscles surrounding lax joints
 * Surgical procedures can correct dislocation
 * Intervention for pain management is necessary
 * An exercise program can strengthen muscles and stabilize joints
 * Cardiovascular
 * Enlarged aortic root can be treated with beta blockers but the efficacy or length of treatment is currently unknown
 * Exercise limitation may be necessary, especially competitive sports
 * Surgical complications and intraoperative problems are common
 * Dermatologic
 * Plastic surgery can be done to close facial wounds or other aesthetically significant areas
 * Retention sutures tied at a distance from the incision may help support the skin during scar formation

Psychosocial Issues

 * Self esteem
 * scars, bruising, scoliosis
 * Financial concerns?
 * Guilt at passing on mutation
 * Pain management issues
 * support network?
 * family? friends? church?

Support Groups and Resources

 * Ehlers-Danlos National Foundation
 * 800-956-2902
 * http//:www.ednf.org

 * Ehlers-Danlos Support Group
 * http//:www.ehlers-danlos.org

 * Family Village
 * http//:www.familyvillage.wisc.edu/lib_e-ds.htm


text:
Handbook of Genetic Counseling/Ehlers-Danlos Syndrome-2

Ehlers-Danlos Syndrome

Introduction

 * Ehlers-Danlos syndromes are a genetically, biochemically, and clinically diverse group of heritable connective tissue disorders
 * They have joint laxity and dermal features in common
 * Manly clinical reports, especially before the mid 1980s, do not distinguish between different subtypes
 * There are very few large or population-based series that might provide information about the full range of therapeutic outcomes or accurate estimates of the prevalence of certain complications of EDS
 * Prior classification has included up to 11 disorders
 * New classification includes
 * Classical type (types I and II)
 * Hypermobility type (type III)
 * Vascular type (type IV)
 * Kyphoscoliosis type (type VI)
 * Arthrochalasia type (types VIIA, VIIB)
 * Dermatosporaxis type (type VIIC)
 * Other variants (VIII, V X-linked, X)

Incidence

 * There are no well-founded figures for prevalence
 * For all forms, estimates of 1/5000 have been made

The Classical Type

 * Major diagnostic criteria
 * Hyperextensibility of the skin
 * Widened atrophic scars
 * Joint hypermobility
 * Can lead to osteoarthritis in the 3rd or 4th decade
 * Other features
 * Poor wound healing
 * ½ of affected individuals are delivered up to 1 month premature due to premature rupture of fetal membranes
 * Some have cardiac abnormalities
 * Mitral valve prolapse
 * Aortic root dilation with occasional rupture
 * Scoliosis
 * Pes planus (flatfoot)
 * Molluscoid pseudotumors (calcified hematomas) may be associated with scars
 * Inheritance
 * Autosomal dominant single-gene disorder
 * Etiology
 * A major cause is mutations in type V collagen
 * At least 3 loci are involved
 * Biochemical Defects
 * Thickened collagen fibrils in skin as well as "cauliflower" deformities of collagen fibrils
 * Mutations in COL5A1 and COL5A2 have been seen in some families
 * Testing
 * No biochemical or molecular based testing methods have been devised to provide reliable results

The Hypermobility Type

 * Primary characteristics
 * Hyperextensibility of large and small joints
 * Soft, velvety skin
 * Other features
 * May have normal scarring but stretchy skin
 * Dilatation and/or rupture of the ascending aorta
 * Scoliosis
 * Pes planus
 * Inheritance
 * Autosomal dominant single-gene disorder
 * Diagnosis is clinical

The Vascular Type

 * Major diagnostic criteria
 * Characteristic facial appearance
 * Thin, delicate, "pinched" nose
 * Think lips
 * Hollow cheeks
 * Some have staring appearance due to decreased adipose tissue below the eyes
 * Thin, translucent skin
 * In fair-skinned individuals, subcutaneous vasculature is easily visible beneath the skin
 * Arterial/intestinal/uterine fragility or rupture which can be life threatening
 * Extensive bruising
 * Other characteristics
 * Normal scar formation
 * May be increased incidence of stroke
 * Acrogeria (aged appearance to extremities, particularly hands)_
 * ¼ of affected individuals experience a significant medical problem by age 20
 * Median age of death is 48 years old
 * Inheritance
 * Autosomal dominant as demonstrated by linkage analysis
 * Etiology (COL3A1 gene)
 * Dominant mutations in the gene for the pro-alpha 1 chain of type II collagen
 * Caused by abnormal synthesis, structure, or secretion of type II collagen
 * 50% have new disease-causing mutations
 * Over 250 COL3A1 disease-causing mutations have been found
 * Testing
 * Can be reliably accomplished by analysis of type III procollagen and collagen chains harvested from cultured dermal fibroblasts

The Kyphoscoliosis Type

 * Key features
 * Neonatal onset of joint laxity
 * Kyphoscoliosis (lateral curvature of the spine accompanying an anteroposterior hump)
 * Muscle hypotonia
 * Other features
 * Ocular fragility
 * Skin fragility
 * Easy bruisability
 * Dermal hyperextensibility
 * Risk for arterial rupture
 * Most have radiologically detectable osteopenia (decreased bone density), but pathological fractures are rare
 * Intelligence is normal
 * Lifespan may be normal
 * Etiology
 * Caused by deficient activity of the enzyme procollagen lysine hydroxylase
 * Inheritance
 * Autosomal recessive
 * Testing
 * Diagnosis depends on demonstration of increased ratio of deoxypyridinoline to pyridinoline crosslinks in urine measured by HPLC
 * Mutation analysis of the PLOD gene that encodes the enzyme procollagen lysine hydroxylase is available on a research basis
 * Carrier testing is not available

The Arthrochalasia Type

 * Major criteria
 * Severe generalized joint hypermobility
 * Congenital bilateral hip dislocations that are difficult to repair surgically
 * Other features
 * Tissue fragility including atrophic scars
 * Kyphoscoliosis
 * Skin hyperextensibility
 * Etiology
 * Caused by a failure to accomplish normal cleavage of the amino-terminal propeptide of type I collagen in all tissues
 * Mutations that remove exon 6 in COL1A1 and COL1A2 are seen
 * This exon encodes the amino-terminal propeptide cleave site
 * Inheritance
 * Autosomal dominant
 * Testing
 * Demonstration of exon 6 skipping in cDNAs of COL1A1 or COL1A2 followed by mutational analysis

The Dermatosporaxis Type

 * Very rare form of EDS
 * Diagnostic Features
 * Dermal fragility: the skin is lax but not stretchy
 * Other features
 * Joint dislocation is usually not a feature
 * Infants have been reported with premature rupture of membranes and umbilical/inguinal hernias
 * Etiology
 * Caused by failure to cleave off the amino-terminal propeptide of type I collagen due to deficiency of the procolagen I N-peptidase gene
 * Inheritance
 * Autosomal recessive

Other Ehlers-Danlos Syndrome Variants

 * Type VIII
 * Rare autosomal dominant condition
 * Characterized by soft, hyperextensible skin, abnormal scarring, easy bruising, hyperextensible joints and generalized periodontitis
 * Resembles type I, but is distinguished by early loss of teeth and characteristic purplish discoloration of scars on the shins
 * Molecular basis is unknown
 * Not clear if it is truly distinct from classical form
 * Type V X-linked
 * Similar to mild classical type
 * X-linked recessive inheritance
 * Unknown molecular defect
 * Type X
 * Joint hyperextensibility, mitral valve prolapse, easy bruising, poor wound healing, clotting disorder
 * Clotting studies showed a defect in the platelet adhesion that is normally observed in response to exposure of platelets to collagen
 * May be caused by a defect in fibronectin

Management

 * Pregnancy
 * All cases should be referred to high-risk obstetric practice
 * Prematurity is a concern
 * Cervical incompetence can be treated with bed rest and the Trendelenburg position
 * Musculoskeletal
 * Physical therapy can improve strength of muscles surrounding lax joints
 * Surgical procedures can correct dislocation
 * Intervention for pain management is necessary
 * A regular exercise program can strengthen muscles and stabilize joints
 * Cardiovascular
 * Enlarged aortic root can be treated with beta blockers but the efficacy or length of treatment is currently unknown
 * Exercise limitation may be necessary especially competitive sports
 * Surgical complications and intraoperative problems are common
 * Dermatologic
 * Plastic surgery can be done to close facial wounds or other aesthetically significant areas
 * Retention sutures tied at a distance from the incision may help support the skin during scar formation

Resources

 * Ehlers-Danlos National Foundation
 * 800-956-2902
 * http//:www.ednf.org

 * Ehlers-Danlos Support Group
 * http//:www.ehlers-danlos.org

 * Family Village
 * http//:www.familyvillage.wisc.edu/lib_e-ds.htm


text:
Handbook of Genetic Counseling/Ehlers-Danlos Syndrome-3

Ehlers Danlos Syndrome

What Is It?

 * A connective tissue disorder involving their skin, joints, muscles, ligaments, and certain organs. (NOTE: nomenclature has changed over the years to reflect the type of EDS. For example, Type I and II have been combined to be Classic Type. Throughout the following information, you will see both the numerical and names used.)

What Causes It?

 * Mutations in the genes that produce collagen or the enzymes that help maintain the collagen.

What Is the Prevalence?

 * 1/5000-1/10000

What Are the Manifestations?

 * Skin: Hyper-extensibility of the skin, fragile skin that bruises and tears easily, severe scarring
 * Joints: Hyper-mobility of joints, loose joints that may dislocate easily with subluxation (space between them). There may be hernias and there are usually molluscoid pseudotumors (calcified hematomas) over areas like elbows and knees.
 * Cardiac: mitral valve prolapse, and aortic dysfunction (1/4 of Type I&II)
 * Other: dental problems, small teeth, short stature
 * Also, depending on the type of EDS, there can be a variety of manifestations:
 * Vascular Type IV = arterial/intestinal/uterine fragility and rupture (as a result, life expectancy is around 50)
 * Kyphoscoliosis Type VI = scoliosis at birth and fragile sclera (the white of the eye- often looks blue)
 * Arthrochalasia Type VIIB= poor muscle tone

Depends on the type of EDS

 * Type I & Type II-Classic, Type III, Type IV-vascular, Type VIII = Autosomal Dominant
 * Type VI, Type X, Type VI-kyphoscoliosis = Autosomal Recessive
 * Type V, Type IX = X-linked recessive
 * Pregnant women who have EDS are at an increased risk for having premature babies. Additionally, there may be an increase in bruising during pregnancy. A woman who has Type IV is at extreme risk when pregnant because of the risk of uterine rupture and maternal death is possible.

Management

 * Possible bracing for joint stability if needed.
 * The most important aspect is to avoid strenuous activities that would put stress on the joints.
 * Children should not be encouraged to maintain strange positions with their bodies as they may cause degeneration of their joints later on.

How Is It Diagnosed?

 * In most cases the diagnosis is clinical only. There are a few types that can be diagnosed molecularly.
 * Type I & II - Classic Type has been found to be liked to mutations in the collagen V, alpha1 and alpha 2 gene. These changes can be diagnosed with a skin biopsy.
 * Type IV-Vascular Type is caused by a structural defect in the proal chain of collagen type III. A skin biopsy will diagnose it.
 * Type VI - Kyphoscoliosis can be diagnosed by a urine test and is a result of a deficiency of lysyl hydroxylase (a collagen-modifying enzyme).
 * Type VIIB-Arthrochalasia Type can be diagnosed through skin biopsy. It is caused by incorrect processing of the amnio terminal end of the proa1(IA) or proa2 (IA) chains of collagen type I.
 * Type VIIC - Dermatosparaxis can be diagnosed through skin biopsy. It is caused by a deficiency of procollagen I on the N-terminal.

Where Can Parents Get More Information?

 * Ehlers-Danlos National Foundation (EDNF)
 * 6399 Wilshire Blvd Suite 510
 * Los Angeles, CA 90048
 * (213) 651-1366
 * http://www.ednf.org

Resources

 * The Ehlers-Danlos National Foundation: http://www.ednf.org
 * Beighton, Peter. McKusick's Heritable Disorders of Connective Tissue 5th Ed. Mosby 1992, Chap. 6.
 * OMIM
 * Smith's
 * Wheeless' Textbook of orthopedics: http://www.medmedia.com/med.htm


text:
Handbook of Genetic Counseling/Epilepsy and Seizures

Epilepsy and Seizures

Background

 * Epilepsies
 * Group of disorders characterized by chronic, recurrent changes in neurologic function
 * Caused by abnormalities in electrical activity of brain
 * An individual with isolated, nonrecurrent seizures who are otherwise healthy do not have epilepsy
 * Prevalence is 0.5-1.0% in general population
 * Seizures
 * An episode of neurologic dysfunction
 * Convulsive seizures are accompanied by motor manifestations or other changes in neurologic function
 * Sensory
 * Cognitive
 * Emotional
 * Classification is based on electroencephalographic pattern, clinical seizure type, and clinical context
 * Age of patient
 * Type of seizure
 * Presence of neurologic lesions

Classifications and Clinical Findings

 * Partial or focal seizures
 * Begin with activation of neurons in only one part of the brain
 * Specific clinical symptoms depend on area of brain involved
 * Potential causes
 * Birth injury
 * Postnatal trauma
 * Tumor
 * Abscess
 * Infarction
 * Vascular malformation
 * Structural abnormality
 * Two subclassifications
 * Simple if no alteration in consciousness
 * Complex if lose awareness of the environment
 * Simple partial seizures
 * Recurrent contractions of muscles of one part of body without loss of consciousness
 * May remain confined to one area of body or spread to surrounding parts
 * May cause sensory symptoms (hallucinations) or psychic symptoms (unwarranted emotions)
 * Complex partial seizures
 * Episodic changes in behavior causing a loss of conscious contact with environment
 * May begin with illusions, hallucinations, feeling of déjà vu, or unusual smell
 * May see lip smacking, swallowing, walking aimlessly, automatisms, or unconscious performance of highly skilled activities
 * When seizure ends, individual experiences amnesia
 * Secondary generalization of partial seizures
 * Progression of partial seizure to loss of consciousness and convulsive motor activity
 * May happen after a few seconds or a few minutes
 * Primary generalized seizures
 * Tonic-clonic (Grand mal)
 * Usually begin without warning
 * Cause sudden loss of consciousness, tonic contraction of muscles, loss of posture control, and cry as respiratory muscles contract
 * Individual may sustain injury when they fall to the floor
 * May suffer cyanosis if respiration inhibited
 * Clonic period of rhythmic contractions of all four limbs that lasts for variable period of time
 * Headaches, drowsiness, amnesia, incontinence, and tongue biting may occur
 * Tonic seizures
 * Sudden occurrence of rigid posturing of limbs and torso
 * Not followed by clonic phase and shorter in duration
 * Absence seizures (petit mal)
 * Sudden cessation of ongoing conscious activity
 * No convulsive muscular activity or loss of postural control
 * So brief they may not be apparent but may cause lapse of consciousness or awareness accompanied by minor motor manifestations
 * Usually begin in children 6-14
 * Often appear neurologically normal
 * Usually sensitive to antiepileptic drugs
 * 1/3 outgrow disorder, 1/3 continue to have only absence seizures, 1/3 have tonic-clonic seizures
 * Atypical absence
 * Similar to absence seizures by coexist with other forms of seizures
 * Occur in children with underlying neurologic dysfunction
 * Resistant to medication
 * Myoclonic seizures
 * Sudden, brief, single or repetitive muscle contractions involving one body part or entire body
 * May occur alone or with other types
 * Symptom of medical conditions
 * Uremia
 * Hepatic failure
 * Creutzfeldt-Jakob Disease
 * Subacute leukoencephalopathies
 * Lafora body disease
 * Juvenile Myoclonic Epilepsy (JME)
 * Atonic seizures
 * Brief loss of posture and consciousness
 * No muscular contraction
 * Usually occur in children
 * Infantile spasms or hypsarrhthmia
 * Occur in infants birth to 12 months
 * All signs of seizures disappear from ages 3-5
 * Suffer other types of generalized seizures later in life
 * Contractions of neck, torso, and both arms
 * Usually occur in children with neurological disease
 * Tuberous sclerosis
 * Anoxic encephalopathy
 * 90% of these children develop mental retardation
 * Febrile seizures
 * Controversial definition, prognosis, treatment, pathophysiology
 * Associated with fever but no evidence of intracranial infection or other cause
 * Usually occur from 3 months to 5 years of age
 * 2-6% go on to develop epilepsy
 * Estimated to occur in 2-5% of all Caucasian children
 * Family history reported in 7-58% of all children with these seizures
 * 8-15%% of first degree relatives may also be affected
 * Multifactorial inheritance
 * Recurrence risks for children of affected proband
 * 18.5% if only proband affected
 * 36.5% if proband and one parent affected
 * 45% if proband and both parents affected

Genetic Etiology

 * Genetic influences may be chromosomal, dominant or recessive autosomal, X-linked, or multifactorial
 * Environmentally induced seizures carry low recurrence risk for other family members

Differential Diagnosis

 * Syncope
 * Fainting or a sudden loss of consciousness not involving convulsions
 * If origin unknown, patient should undergo cardiovascular evaluation, EEG with sleep recording, and prolonged ambulatory EEG monitoring
 * Transient ischemic attacks and migraines
 * Transient alteration in neurologic function without loss of consciousness
 * Can undergo MRI or CT scan, carotid studies, and EEG precedures
 * Antiepileptic drugs may help migraines
 * Pseudoseizures and "hysterical seizures"
 * Patients may appear emotionally disturbed and receive psychiatric treatment
 * Normal EEG but may have activity in deep temporal lobe not detected
 * May be eliminated or reduced by suggestion

Treatment and Management Options

 * Eliminate cause, suppress expression, and deal with psychosocial consequences
 * May be treated by correcting metabolic disturbance, hormonal disruptions, etc.
 * Pharmacologic control
 * Goal is to prevent seizures without interfering with cognitive function
 * Many patients are resistant to medication
 * Teratogenic
 * Neurosurgical treatment
 * Remove structural lesion and nearby diseased part of brain (e.g. - tumor)
 * May not help eliminate psychological disturbances that may occur

Psychosocial Issues

 * Anxiety over potential future development of epilepsy
 * Complications associated with pregnancy
 * Difficulty assessing exact recurrence risks
 * Frustration if unknown etiology or explanation
 * Social stigma associated with neurological disorders
 * Fear of potential seizures at school, in public, etc.


text:
Handbook of Genetic Counseling/Ewing's Sarcoma

Ewing's Sarcoma

What is Ewing's sarcoma/PNET?

 * a cancer that can start in bone or soft tissues
 * most common sites for are the pelvis, the thigh, and the trunk of the body
 * peak ages are 10-20, but younger children and older adults can also get it
 * half are under 15 years
 * less common before 5 or after 30
 * no known cause
 * cells in the tumours have a piece of chromosome 11 moved to chromosome 22
 * 85% contain chromosomal translocation at the t(11;22)(q24;q12)
 * the genetic change occurs only in the tumour cells, not in the sperm or egg
 * 2.5% of cases of childhood cancer
 * development of the tumour appears to be in some way related to periods in life with rapid growth, hence the average for tumour development is 14-15 years
 * slightly more common in boys than in girls
 * most common early signs are pain and swelling
 * can spread to other parts of the body
 * always requires treatment to the whole body (chemotherapy, surgery, radiation therapy)

Symptoms

 * vary from person to person depending on the location and size of the cancer
 * most common symptoms are pain and swelling or tenderness in the affected area
 * pain may become very intense when the tumour is located near important nerves, like in the sacrum, pelvis or spine
 * swelling is often seen, especially when the log bones of the arms or legs are affected
 * tiredness, fever, weight loss, and anaemia


text:
User talk:80.68.6.198

You have been temporarily blocked from editing Wikibooks. You were warned several times that linking to commercial sites is not allowed. If you wish to make useful contributions, you are welcome to come back after the block expires.

title: User talk:80.68.6.198


text:
User talk:128.172.19.25

Please stop adding nonsense to Wikibooks. It is considered vandalism. If you would like to experiment, use the sandbox. Thank you.

title: User talk:128.172.19.25


text:
User talk:Patrick

I will notice messages sooner if they are put on w:en:User talk:Patrick of m:user talk:Patrick.

title: User talk:Patrick


text:
XML - Managing Data Exchange/XQuery

1. Definition of XQuery
XQuery is a query language under development by the World Wide Web Consortium (W3C) and makes possible to efficiently and easily extract information from native XML databases and relational databases that store XML data.

Every query consists of an introduction and a body. The introduction establishes the compile-time environment such as schema and module imports, namespace and function declarations, and user-defined functions. The body generates the value of the entire query. The structure of XQuery shows in Figure 1.

   Figure 1. Structure of XQuery   Introduction  Comment:  (: Sample version 1.0 :)

Namespace Declaration:
declare namespace my = “ urn:foo ”;

Function Declaration:
declare function my:fact ($n) {

if ($n < 2)

then 1

else $n * my:fact ($n – 1)

};

Global Variable:
declare variable $my:ten { my:fact (10)};

Body
Constructed XML:
<table>{

FLWOR Expression:
for $ i in 1 to 10

return

< tr >

Enclosed Expression:
< td> 10!/{$ i }! = {$ my:ten div my:fact ($i )} </td>

</tr >

} </table>

2. XQuery versus Other Query Languages
2.1 XQuery versus XPath and XSLT

XQuery, XPath, XSLT, and SQL are good query languages. Each of these languages has their own advantages in diverse situations, so XQuery cannot substitute for them at every task. XQuery is built on XPath expressions. XQuery 1.0 and XPath 2.0 shares the same data model, the same functions, and the same syntax. Table 1 shows the advantages and the drawbacks of each query language.

Table 1. XQuery versus XPath and XSLT

Advantage
Drawback

 XQuery
1.expressing joins and sorts
2.manipulating sequences of values and nodes in arbitrary order
3.easy to write user-defined functions including recursive ones
4.allows users to construct temporary XML results in the middle of a query, and then navigate into that
1.XQuery implementations are less mature than XSLT ones

 XPath  1.0
1.convenient syntax for addressing parts of an XML document
2.selecting a node out of an existing XML document or database
1.cannot create new XML
2.cannot select only part of an XML node
3.cannot introduce variables or namespace bindings
4.cannot work with date values, calculate the maximum of a set of numbers, or sort a list of strings

XSLT 1.0
1.recursively processing an XML document or translating XML into HTML and text
2.creating new XML or part of existing nodes
3.introducing variables and namespaces
1.cannot be addressed without effectively creating a language like XQuery
2.cannot work with sequences of values

2.2 XQuery versus SQL

XQuery has similarities to SQL in both style and syntax. The main difference between XQuery and SQL is that SQL focuses on unordered sets of “flat” rows, while XQuery focuses on ordered sequences of values and hierarchical nodes.

3. XQuery Expressions
3.1 FLWOR expressions FLWOR expressions are important part of XQuery. FLWOR is pronounced "flower". This name comes from the FOR, LET, WHERE, ORDER BY, and RETURN clauses that organize the expressions. The FOR and LET clauses can come out any number of times in any order. The WHERE and ORDER BY clauses are optional. However, these clauses must be shown in the order given if they are used. The RETURN clause should exist.

XQuery permits you to use join queries in a similar way to SQL. This example is depicted in Example 1 as a join between the videos table and the actors table.

Example 1. let $doc :=. for $v in $doc//video, $a in $doc//actors/actor where ends-with($a, 'Lisa') and $v/actorRef = $a/@id order by $v/year return $v/title

The LET clause states a variable assignment. In this case, the query initializes it to doc ('videos.xml'), or a query’s result places a document in a database. The FOR clause describes a mechanism for iteration: one variable processes all the videos in turn, another variable processes all the actors in turn. In this case, the query processes the pairs of videos and actors. The WHERE clause selects tables in which you are interested. In this case, you want to know that the actor shows in video table with the name ending with “Lisa”. The ORDER BY clause obtains the results in sorted order. In this case, you desire to have a result with the videos in order of their release date. The RETURN clause at the end of an expression informs the system what information you want to get back. In this case, you want the video’s title.

3.2 Conditional expression

XQuery offers IF, THEN, and ELSE clause, conditional expression. The ELSE clause is obligatory. The reason is that each expression in XQuery should return a value. A query is showed at example 2 to retrieve all books and their authors. You desire to return additional authors as “et-al” after the first two authors.

Example 2.

for $b in document("books.xml")/bib/book return if (count($b/author) <= 2) then $b else { $b/@*, $b/title, $b/author[position <= 2], <et-al/>, ...... $b/publisher, $b/price }

This query reads book data from a books.xml. If the author count is less than 2 or equal to 2 for each book, then the query returns the book straightly. Otherwise the query makes a new book element including all the original data, excepting that the query contains only the first two authors and attaches an et-al element. Position function is returned only the first two authors. $b/@*, XPath expression, refers to all the attributes on $b.

3.3 XQuery functions and operators XQuery contains a huge set of functions and operators. Table 2 shows frequently used built-in functions. You are able to describe your own and many engines provide custom extensions as well.

Table 2. Commonly used built-in functions

Function
Commentary

Math:
+, -, *, div, idiv , mod, =, !=, <, >, <=, >= floor, ceiling, round, count, min, max, avg, sum
Division is done using div rather than a slash because a slash indicates an XPath step expression. idiv is a  special operator for integer-only division that returns an integer and ignores any remainder.

Strings and Regular Expressions:
compare, concat , starts-with, ends-with, contains, substring, string-length, substring-before, substring-after, normalize-space, upper-case, lower-case, translate, matches, replace, tokenize
 compare( ) dictates string ordering. translate performs a special mapping of characters. matches, replace, and tokenize use regular expressions to find, manipulate, and split string values.

Date and Time:
current-date, current-time, current-dateTime +, -, div eq, ne, lt , gt , le, gt
 XQuery  has many special types for date and time values such as duration, dateTime, date, and time. On most you can do arithmetic and comparison operators as if they were numeric. The two-letter abbreviations stand for equal, not equal, less than, greater than, less than or equal, and greater than or equal.

XML node and QNames :
node-kind, node-name, base-uri eq, ne , is, isnot, get-local-name-from- QName , get-namespace-from- QName deep-equal >>, <<
node- kind returns the type of a node (i.e. "element"). node-name returns the QName of the node, if it exists. base- uri   returns the URI this node is from.
Nodes and QName values can also be compared using eq and ne (for value comparison), or is and isnot (for identity comparison). deep- equal compares two nodes based on their full recursive content.
The << operator returns true if the left operand preceeds the right operand in  document order. The >> operator is a following comparison.

Sequences:
item-at, index-of, empty, exists, distinct-nodes, distinct-values, insert, remove, subsequence, unordered.position, last
item- at returns an item at a given position while index-of attempts to find a position for a given item. empty returns true if the sequence is empty and exists returns true if it's not. dictinct -nodes returns a sequence with exactly identical nodes removed and distinct-values returns a sequence with any duplicate atomic values removed. unordered allows the query engine to optimize without preserving order. position returns the position of the context item currently being processed. last returns the index of the last item.

Type Conversion:
string, data, decimal, boolean
These functions return the node as the given type, where possible. data returns the "typed value" of the node.

Booleans:
true, false, not
There's no "true" or "false" keywords in XQuery but rather true and false functions. not returns the boolean negation of its argument.

Input:
document, input, collection
 document( ) returns a document of nodes based on a URI parameter. collection returns a collection based on a string parameter (perhaps multiple documents). input returns s general engine-provided set of input nodes.

4. References
The contents of this chapter were quoted from the following lists.

- X Is for XQuery, Jason Hunter: http://www.oracle.com/technology/oramag/oracle/03-may/o33devxml.html

- An Introduction to the XQuery FLWOR Expression, Michael Kay: http://www.stylusstudio.com/xquery_flwor.html

- Learn XQuery in 10 Minutes, Michael Kay: http://www.stylusstudio.com/xquery_primer.html

- XQuery: The XML Query Language, Michael Brundage, Addison-Wesley 2004

5. Useful Links and Books
- W3C XML Query (XQuery): http://www.w3.org/XML/Query

- XQuery Latest version: http://www.w3.org/TR/xquery/

- XQuery 1.0 and XPath 2.0 Functions and Operators: http://www.w3.org/TR/xpath-functions/

- XQuery 1.0 and XPath 2.0 Data Model (XDM): http://www.w3.org/TR/xpath-datamodel/

- XSLT 2.0 and XQuery 1.0 Serialization: http://www.w3.org/TR/xslt-xquery-serialization/

- XML Query Use Cases: http://www.w3.org/TR/xquery-use-cases/

- XML Query (XQuery) Requirements: http://www.w3.org/TR/xquery-requirements/

- XQuery: The XML Query Language, Michael Brundage, Addison-Wesley 2004

title: XML - Managing Data Exchange/XQuery


text: Japanese/Reader/第三夜/Part 7

title: Japanese/Reader/第三夜/Part 7


text:
User:Dolive21

Hello.

I am a Male from south east england. My interests include Runescape and Law. My political beliefs are mainly left wing, but with some right wing streaks when it comes to national security.

title: User:Dolive21


text:
Digital Circuits/Flip-Flops

A flip-flop is a device very much like a latch in that it is a bistable multivibrator, having two states and a feedback path that allows it to store a bit of information. The difference between a latch and a flip-flop is that a latch is asynchronous, and the outputs can change as soon as the inputs do (or at least after a small propagation delay). A flip-flop, on the other hand, is edge-triggered and only changes state when a control signal goes from high to low or low to high. This distinction is relatively recent and is not formal, with many authorities still referring to flip-flops as latches and vice versa, but it is a helpful distinction to make for the sake of clarity.

There are several different types of flip-flop each with its own uses and peculiarities. The four main types of flip-flop are : SR, JK, D, and T.

SR Flip-flops
An SR(Set/Reset) flip-flop is perhaps the simplest flip-flop, and is very similar to the SR latch, other than for the fact that it only transitions on clock edges. While as theoretically valid as any flip-flop, synchronous edge-triggered SR flip-flops are extremely uncommon because they retain the illegal state when both S and R are asserted.

D flip-flop
The D(DATA) flip-flop is the edge-triggered variant of the transparent latch. On the rising (usually, although negative edge triggering is just as possible) edge of the clock, the output is given the value of the D input at that moment. The output can be only changed at the clock edge, and if the input changes at other times, the output will be unaffected.

D flip-flops are by far the most common type of flip-flops and some devices (for example some FPGAs) are made entirely from D flip-flops. They are also commonly used for shift-registers and input synchronisation.

JK Flip-flop

The JK flip-flop is a simple enhancement of the SR flip-flop where the state J=K=1 is not forbidden. It works just like a SR flip-flop where J is serving as set input and K serving as reset. The only difference is that for the formerly "forbidden" combination J=K=1 now performs an action: it inverts its state. As the behavior of the JK flip-flop is completely predictable under all conditions, this is the preferred type of flip-flop for most logic circuit designs. But there is still a problem; i.e. both the outputs are same when one tests the circuit practically. This is because of the internal toggling on every propagation elapse completion. The main remedy is going for master-slave JK flip-flop; this flip-flop overrides the internal recurring toggling through the pulsed clocking feature incorporated.

T flip-flops

A T flip-flop is a device which swaps or "toggles" state every time it is triggered if the T input is asserted, otherwise it holds the current output. This behavior is described by the characteristic equation:

 * $$Q_{next} = T \oplus Q = T\overline{Q} + \overline{T}Q$$

and can be described either of the following tables:

When T is held high, the toggle flip-flop divides the clock frequency by two; that is, if clock frequency is 4 MHz, the output frequency obtained from the flip-flop will be 2 MHz. This 'divide-by' feature has application in various types of digital counters. A T flip-flop can also be built using a JK flip-flop (J & K pins are connected together and act as T) or D flip-flop (T input and Qprev are connected to the D input through an XOR gate). d t

title: Digital Circuits/Flip-Flops