Modeling

It's amazing that a book so short can be so repetitive. I lost track of how many times I was told that IIS 6 installs in a sepcial "locked down" state. Somehow, the book manage to avoid getting in any real detail about other security issues, like certificates and how to install SSL. What's worse, sometimes the repetition isn't even in agreement. For example, early in the chapter we're told that setting ODBC logging disables the kernel cache automatically. Later on, we're warned that if we enable ODBC logging, the kernel cache feature will still work and hits won't be logged. I'm still waiting for a third chapter to weigh in with the tie-breaking vote.

Perhaps the most entertaining part of this book is it's puzzling Confucius like sentences and complete disregard for grammar. Chapter 5 (Administering IIS) is particularly notable--it includes sentences like "Since ABO can't be used in scripts, we cannot use it to investigate ABO since they'll not be handy for us to do stuff quickly" (page 129) and "MMC is the most famous way to administrate" (page 102). No, I'm not making this up, and yes, I could continue, but I don't have time--I have to find a new IIS 6 book to make up for the time I've wasted reading this one.

The Book is really handy and provides a nice insight of the new features offered by IIS6. It was right to the point and a nice value addition to my tech book collection. Its really worth it....

This book was short, but to the point, and gave me all of the information I needed to get a good idea of what IIS 6 is (and is not). It's clearly a version worth the upgrade, and this book showed me all of the new features that support that decision. That's what these handbooks are for, no? Grin...

This book has no redeeming value whatsoever. The photographs look bad, the content is bad and many of the models are has-beens who never were. Overall a waste of paper pulp, although I initially picked it up because I liked the cover.

A book like this will normally be expected to contain lots of outstanding photographs with beautiful reproductions. Oddly, the photographs are the weakest part of the book. Much of the book is focused on brief, superficial interviews with famous model industry personalities conducted by David Bailey. The essays primarily repeat what popular magazines have said about the industry over the years, and are written in a similar style to that used in fashion magazines. If you are a younger person, and want to know about what modeling was like before the 90s, the text will probably be of some interest to you.

The essays begin with one about the role of the female model, and how these women emerged from being mannequins (or a blank canvases) who were often expoited into becoming well-known personalities who often developed nonmodeling careers (such as acting). The history of how agents went from controlling the industry (and getting 40 percent of the fees paid to the models) to losing control is then described. Some of the top fashion photographers are profiled next, along with their styles. Brief essays also look at designers, editors, the supermodel phenomenon, those who were harmed by becoming models (especially during heroin chic), and the fashion legends. These essays are the best part of the book

Brief interviews are reported with Isabella Blow; Karen Elson; Cindy Crawford; Jerry Hall; Michael Flutie; Eileen Ford, Lillian Bassman; Bruce Weber; Penelope Tree; Arthur Elgort, Peter Lindbergh; Patrick Demarchelier; Isabella Rossellini; Angelica Huston; Carmen Dell'Orefice; Isaac Mizrahi: Vivienne Westwood; Karl Lagerfeld; Jay Alexander; Liz Tilberis; Polly Mellen: Franca Sozzani; Anna Wintour; Christy Turlington; Naomi Campbell; Helena Christensen; Suzie Bick; James King; Jean Shrinpton; Dorian Leigh; Iman; Karen Elson; and Kate Moss. If you know much about fashion or modeling, little new will emerge here other than occasional snide comments about individuals.

All of the photographs are done by David Bailey. My favorite images in the book (as reproduced here) are:

Peter Lindbergh (p. 23)

Naomi Campbell (pp. 24-25)

Iman (p. 37)

Jerry Hall (pp. 53, 164)

Catherine Deneuve (p. 65)

Jean Shrimpton (pp. 69, 169, 185)

Anne Piaggi (p. 118)

Anna Wintour (p. 127)

Christy Turlington (p. 137)

Carmen Dell'Orefice and Dorian Leigh (p. 171).

Both the photographs and the reproductions are unremarkable. I came away thinking (once again) that David Bailey was lucky that he was able to photograph Jean Shrimpton and Catherine Deneuve so often. With other models, the results are not as good.

Having looked at this material made me realize how much fashion focus is like a brief glance, arresting . . . but then moving on to look at something else. It must be terribly difficult to go from obscurity to the center of attention to being of no more interest to most people. I admire those who can handle it well.

What can you do to make your life become a progression of rewarding accomplishments, so that maturity launches you further along in satisfactions? When you answer that question, you will have obtained a profound benefit from this panorama of fashion history.

When your heart and personality shine, you always look your best! But more importantly, you feel and act your best then, too.

Mario Sorrenti is not dead. You mentioned in the article that he died from a drug overdose. This, however, is not true. Mario's brother, Davide, died. Sorrenti has published a book on the life of his brother called "The Machine."

Less than half of this book really deals with what the title suggests. Chapters 6, 7, and 8 are the only things of value to someone already familiar with the UML. The previous chapters try to give the database designer an overview of using UML for all project aspects; however, this is done much more cleanly in other books like UML Distilled or Visual Modeling With Rational Rose 20XX and UML.

The authors also present things with assumptions made about how the organization is structured: separate application and database design teams. This slant requires that the reader translate what is written to their particular situation. A more useful book would have stated principles that can be applied to various organization structures with appropriate practices.

Also, there is no advice given as to how to actually implement any of these UML extensions for database design in the available tools. This makes the ideas presented hard to put in practice and makes the book much more theoretical than practical.

Bottom line, there is not enough unique information here for the book to stand on its own. It would be better to roll this information into texts like the ones I mentioned at the beginning, and also give examples using currently available tools.

Despite the previous reviews of this book I decided to read it and am glad that I did. The authors took me through a thorough yet easily understood path of both UML and database design. Not being an expert in UML, but having a background as a data analyst, I found the book useful to understand UML as it pertained to how I would use it. The callouts for database designers were very helpful and by following a consistent real-world example, I was able to understand how I would design my databases using the UML. I now understand that I don't have to know or even use the entire language to succeed, but only the parts that are relevant at the time I am designing and now I can be on the same page as my development team too.

I wanted a book that would show how to start using UML for data modeling. This did. I too liked the DB Designer sidebars and the detailed case study. I thought the case study "story" sections were a nice change of pace from most software books' straight technical style. (And I've see such stories happen on the job too often.) This book worked for me.

This book describes how the US mortgage and credit card industries approach modeling, from the industry standard practioners point of view. It is best read by those familiar with the industry. It ignores the potential of current thinking outside industry standard practices. However, everyone interested in the subect needs to know the way FICO does it; they are the standard.

I agree with everyone else, but they are comming from a different point of view than the person that would benefit from this book.

This book is very nicely done for the beginner who wants to read his first book on credit risk.

Even for me I found some information in it that was extremely beneficial; it will probbaly save our corporation a great deal of money.

The title says "Design and Application"; the book serves the title very well. Concise, loaded with different angles. Some writers' names are big in other fields. Surprisingly, a good economist's review is also included, Mark Z's. I once reviewed about 90 relevant publications in the credit scoring field for my thesis project. One impression was the literature was fragmented and heavily European oriented. This book clearly interests me more as it relates to American experience more.

The title does not say "Theory and application". So I don't complain about its "lack of substance". I don't believe either it is for beginners. Design is related to science, but design is often more an art than science; I don't expect it to be a theoretic tome. It is more like a "programmer's pocket book". So certain level of prerequistion and experience will max out the benefits for the reader.

I look forward to seeing another update.

ITS DUMB, IT HAS NO INFO ON HOW TO USE PALACE STUFF OR ANY INFO... IT ONLY SAYS HOW PEOPLE ARE ON THE PALACE AND STUFF!!!!!!!!!!!!

I have been using palace for numerous years,its a great program for people who are creative, but i had to delete it to update my hard drive, now i want to re-install it but i can't find where to download it, can anyone help me find it,or send me the program?thanks.

If you've just started using The Palace or if you've been using it for quite some time, get this book. It tells you everything you need to know about Palace, including helpful commands and a variety of other useful information.

By Libby Ingrassia Schwarz (Rating B) Judging from its title, you'd think that Gregory Pepus's Web Site Development With Domino is entirely about what the title says - Web site development with Domino. But it's not: about a third of the book is about administering Domino. Unlike most Domino books, which discuss only Domino on NT, this one explains how to install Domino on NT, OS/2, and UNIX.

The first six chapters take you from an overview of Domino technology through installation and configuration, introducing you, among other things, to the Domino Name and Address book and Internet messaging with Domino. These some good information here, but don't try to read these chapters straight through. The author skips around a lot:use the index to find what you need. The second part of the book (chapters 7 to 12) focuses on development including sample code in Java, JavaScript, LotusScript, CGI, and HTML. These chapters are't for beginners; even experienced database developers will have to skip around.

Chapters 7, 9, 10, and 11 contain a listing of useful @functions and @commands that can be used with the Web. Chapter 8 introduces Web site creation without the need for programming. The section ends with an introduction to Navigators, Imagemaps, and the use of frames in Domino apps. Chapters 13 and 14 explain how to enhance Web sites with search capabilities and java. There's a good seciton on how to conver code created in LotusScript to Java/JavaScript. The appendix contains information about Domino back-end classes and some sample Java code, as well as a Domino 4.6 feature list. The companion CD includes a sample copy of Notes/Domino 4.6.

Web Site Development With Domino is best used for reference. If you're a developer with some background in programming with Java, HTML, CGI, or LotusScript you'll find much that will add to your knowledge and help you create a Domino site. If you're less experienced, I suggest you get another book, such as Steve Oliver and Pete Wood's Lotus Domino Web Site Development for the basics, and use Pepus's as a reference for advanced programming.

Alhtough not what I expected, I found this book a comprehensive guideline to using Lotus Domino both on setup and administration as well as a good primer for Domino Web programming. It has allowed me a good start in the field.

Although I am an experienced Notes developer I'm new to using Domino for web development. I have found this book to be very useful. If you are in the same boat: You know something about Lotus Notes and want to understand how Domino creates HTML for the web, I suggest you check out this book. P.S. This is the first time I've felt compelled to write a review to balance the negative rating given by other reviewers.

Suprisingly thin on practical information - poorly written (or edited to create more pages) - and not usable. Better to read the Whitepapers on Microsoft's web site....for theory - which is the true nature of this book.

Buy it. This is an excellent book at a great price for those responsible for implementation planning and needing an introduction. The book is in-depth on theory and sure beats having to track down dozens of white papers. Other reviewers have badgered the book for its lack of technical details or practical examples of a migration but since that is not the intention of the book it is unfortunate they rated it so low. You can't judge a book by it's cover and that's why you need to glance at the outline to see if the contents are what you need. Anyway, at under 400 pages you can actually divulge the information provided in a reasonable period of time - important for those on a fast track. Kudos to the authors.

I found this book to be very helpful in assisting me with my migration to Windows 2000 and thorough in explaining the active directory concepts. I would recommend this book to anyone that is serious about planning and executing a migration to Windows 2000 or to anyone that just wants a better understanding of Active Directory.

The book is kind of blur and not much indication on how to do it. It is not worth to get one actually.

The author discusses some interesting topics, but I found the book far too full of vague statements about the usefulness of various ways of encoding XML and of database architecture. Similarly, the chapter on querying XML databases was enough to whet my appetite, but it was mostly on the representation of queries (useful, to be sure, but confusingly presented), had little about efficiency considerations (surely of paramount importance when discussing queries), and presented as "algorithms" methods that are so unrefined and simplistic that they're better labeled "query methodologies."

To be fair, I haven't been all that impressed with the other XML books I've been skimming...

XML is a critical emerging technology which has the potential to revolutionize database connectivity in enterprise software development. While the author provides knowledge about XML document design and delivery, the book falls short of providing meaningful insights to those who wish to construct integrated commercial XML/Database systems.

The writer doesn't seem to have a good idea of the history and development of these database concepts for commercial use. For example, he doesn't seem to know that Object databases have had repeated failures in terms of performance, maintainability and a host of other factors in mission critical applications.

He would have gained by referencing "Foundation for Future Database Systems: The Third Manifesto," by C.J. Date and High Darwin, and by familiarzing himself with "The Great Debate," where E.F. Cobb demonstrated how non-relational models are orders of magnitude more complex than relational models for the same problem.

As someone who has architected and developed large scale XML-based database applications, I sense that the author has come from a perspective of writing specialty XML document delivery databases for non-commercial purposes in the biotechnology industry, and provides minimal material which would be useful to anyone seeking to implement industrial strength XML databases (in an application server, for example) or to use XML messaging with relational databases (e..g., with webMethods and Rendezvous' Tibco.)

The author has a writing style which is quite chatty and unprofessional, which continually distracts from its purpose, which is to compare XML, Relational and Object database design issues. Buy this book to skim through it as a reference, but do not expect it to be of great value to many of the issues that are likely to be faced in building enterprise class databases. You can find better information of a higher quality on this subject for free by visiting [certain websites] and reading many of their XML-related articles. It may be of more value if you only wish to create XML document servers.

I agree completely with one of the other reviewers: the authors of this book took a decent book about Windows NT Server 4 and butchered it by just doing a search for 'Windows NT' and replacing with 'Windows 2000'. Too bad that they didn't proof read it afterwards, as it left obvious gaffs like 'Windows 2000, version 3.51' and the like; by about the tenth one of these I just had to put the book down. There is very little new material in this book even though W2K has a number of totally new topics. It would appear that it was rushed to press based on a Beta version of Windows 2000 so that they could cash in on the W2K craze. Sams: please have your books proof read by someone that is knowledgeable in the industry before you publish them. This could have been a useful book. Hopefully they will tune it up and republish it after fixing the problems.

I would have to also disagree with the bad review this book received. Sure it was written based on the Pre Release of Windows 2000 Server however I have found the book very useful and helpful. Saved me a lot of time. I would also recommend using the "Mastering Advance Server 2000" book to go along with this one for more in depth details.

I would have to also disagree with the bad review this book received. Sure it was written based on the Pre Release of Windows 2000 Server however I have found the book very useful and helpful. It Saved me a lot of time. I would also recommend using the "Mastering Advance Server 2000" book to go along with this one for more in depth details.

The book studies detonation waves at a superficial
mathematical level. It is good in showing how a code
can be used to calculate simple detonating flows.

The book lacks any mathematical depth and should be
avoided by researchers. People in the industry and in the
Labs might find it useful.

Too expensive for what it offers!

The book does not give any worked examples.

The mark of any good technical writer is
showing your work in detail, this book
leaves a lot to be desired.

I am trying to return the book to
amazon.

This book is not for the faint of heart.
It is a highly technical book and written only for those
with experience in this field.
The book does not start out with basic definitions
and is written for individuals who have professional
credentials in this particular industry.
Personally I look for a technical book to begin with
basic theory and then build from there with orderly
procedures and fully worked mathematical examples.
The author is a good communicator, however if you
are looking for basics in this field, it's a little
steep to try to start from this material.
If your a professional already working with
explosives in a research facility you will find this
book to be an excellent treatise.If like myself you
only have a passing interest and are looking for
general content, then this is not for you.
I was looking for information regarding pressure
relief for dust explosions inside production
vessels and purchased this book by mistake.