Electronic-data-interchange Books

I believe this book is good one for Business people so they know how does business get effected by E-commerce and technology. it has many examples and explanation but i believe that i could be doing the same purpose in less details and papers number, the case studies is good, but they do not have small and important information in the side of the papers as margin, in general i think you will like to read it but you have to be a little patient

I bought this book for a class at Strayer University-it's the textbook for an e-commerce class. The book gives a good overview of the current state of e-commerce and gives quite a bit of introductory information on putting together an e-commerce site; hardware requirements for hosting your own; security and payment systems. It's not in-depth, but that would require a much larger volume.

Schneider's seventh edition of "Electronic Commerce" graciously takes the user through many of the major topics that relate to electronic commerce and online business initiatives. I thoroughly enjoyed reading this book and it is packed full of real-life sites and examples to support the material being taught. Likewise, I found the "Learning From Failures" section within each chapter to be fascinating to read. There are many colored graphics and screenshots to help illustrate points and each chapter concludes with a thorough review along with dozens of additional resources that can be explored if further knowledge is desired.

It is worth noting that, with an average of 50 pages per chapter and 12 chapters in all, the wide range of material taught can be difficult to digest and at times topics seem to be brushed over far too quickly. Also, this book teaches the business concepts, evolution, trends, and terminology involving e-commerce but does not walk the reader through the actual process of designing and deploying such a site. So, people looking for a book that will directly assist them in setting up their own online store may wish to look elsewhere, since only a few chapters in the book even touch upon the subject of hardware and software options available for e-commerce design, although the book as a whole teaches the underlining concepts and knowledge useful in setting up such sites.

This book kept my interest from start to finish, and was written in a more leisurely and personable fashion than many other technical books I have read in the past. For this reason, I recommend this book to anyone majoring in an IT/Web-related field.

First let me disclose that I have been a programmer for years (and for some of the businesses described in the book).

In general the book is good.

Pros:
It summarizes the business end of ecommerce very well.
The book covers most of the technical aspects of ecommerce from a high level.
The book is not about abstract, useless business theory that is common in many university business courses; the book is a collection of good case studies of ecommerce.

Cons:
The book chews more than it can swallow given the pace it needs to set for a normal class. Since it needs to stay at certain length, the book doesn't always do a good job explaining the technical aspects of ecommerce with enough detail from a layman's point of view. At times it is more of a review for people already with the knowledge. So unless your technical background is strong and deep (eg you are either a programmer or systems administrator for web servers), there may be a lot of jargon in some areas that will confuse and bore you. Consequently this is probably a senior year book

(The author should take notes from the HeadFirst series of technical books.)

My heart goes out to Ben Matthews (below) who had this thing for a level 4700. That's nuts. I had this book for a level 222 and it was a complete joke. There's a lot of good information and stories about what makes a good e-commerce site, I'll give it that. But there's nothing in here to really give you an edge as far as this stuff goes. The entire point of this book can be summed up in this statement:

"Look at amazon, look at google and look at yahoo. Look for reasons why they're successfull and take note. Do the same practices in your online sites".

This book is an interesting read, but for a bunch of stories and business jargon it's not worth the money.

I have intermeidate experience with BizTalk, and many of the examples in this book are not fully explained, nor is there adequate sample code to review.

Also, on the publisher's site, there is not book code page to be found. Apparently there was once a page but the link has been broken for several weeks. I presume that so many people had questions that the author stopped supporting the book. I woulds stay away from this one.

BizTalk 2006 Recipes is a refreshing book. Rather than re-organize the existing help, they have taken the time to address dozens and dozens of common scenarios and provided "recipes" for each of these.
This is information that you don't find in the help. Just like a cookbook, appetizers, breads, drinks, poultry, salads, etc., BizTalk 2006 Recipes uses the same paradigm, Schemas, Mapping, Messaging, Orchestrations, etc. For each "recipe," you have the problem you are trying to solve, the solution for the problem, and then best part, "How it Works," which explains the underpinnings of each of the topics. They pick both simple and advanced topics and it is structured to allow you to either go through the book end-to-end or to use it as a reference. I think this is a great compliment to the existing documentation and a handy reference for any BizTalk developer.

Though this book covers basics, it is a good reference book to learn what some of the real world scenarios are and how to solve them.

However, if you assume this a 1-2-3 type "recipes", you may find challenges in following the instructions. To name a few, just try out Recipe 5-2 from the Sample Chapter of this book, I wonder how many people can get it working. You will also need good enough of background to jump right into some topics such as BRE and BAM, or you will be left with a lot of "Why" and "How" while reading some talk-through descriptions (Yes, you are reading right, not step 1-2-3 at all). "Related Activities" in Recipe 9-1 is one of many examples.

You may be questioning yourself and try to look for sample codes/project download from the publisher Apress official site. You will be very disappointed how many key subjects out there. This may be the nature of the BizTalk implementation, unlike other subjects such as C# coding sample which author can just zip and ship the sample codes out for download.

Overall, this book is fine. To me, it seems this book came out rush. More proof-reading can make this book better.

I find that the examples given in this book cover the basics well. There is nothing about the EDI subsystem or the Sharepoint Adapter.

This is a piece of the review I wrote on my blog (putting the URL would be against the policies here so I'm leaving it out).

The book format: It is a recipe book so is written in a "Problem, Solution, How it works" style format with each chapter being given an introductory page or two preface. This book will be a great one to have around as a reference book, but I have to say that I also enjoyed reading it cover to cover (well almost... honestly I skimmed chapter 10, this chapter probably could have been done away with and the contents moved to other chapters).

The book is fairly comprehensive in covering BizTalk soup to nuts; there is a chapter on Schemas, one on Business Rules engine (more on this one later in the post), one on BAM and one talking about HAT. The writing styles of the various authors were not too apparent, but rather fairly subtle; sometimes in code samples they were apparent however; one chapter has code that uses both hungarian notation on variables, but also on function parameters. That should be done away with in this persnickety developers opinion. I have to say that from still fairly green knowledge of BizTalk, it appears that at least some of the authors have implemented a fair amount of BT solutions in their careers; to me this was evidenced by the "NOTE" sections that were lusciously littered throughout the text that included well thought out pitfulls and other tips to assist in your BizTalk solutions. In my opinion the one chapter that stuck out (and obviously I could be wrong) as one that wasn't written from experience but rather written from a "I just learned this" kind of perspective was the business rules engine chapter 5 (which ironically is available for free download from Apress).

Overall, I would give this book 3 tivo thumbs up, 4.5 stars out of 5 rating. Get this book if you need assistance with BizTalk 2006.

Other side notes, the authors created a blog site just for the book, but thus far only posted one comment and apparently aren't interested in doing much blogging, I'd love to see that change.

One other note I forgot to include; there was a couple spots that made reference to BizTalk 2004; one of the spots was more of a "if you are used to doing it this way, here is what you will have to do now" kind of reference; I found that appropriate; the other one was "here is how to do it in 2004 and here is how to do it in 2006". That one the book could do without. I don't recall where in the book they were; but for the authors knowledge it was the first 2004 reference in the book that could go and the 2nd one could stay :) I gave them the full 5 stars since they are first to market; I think 4.5 stars would be an appropriate rating on this book. Great job to the authors!

I really should like this book - it's highly related to what I do and I love my job. There were a number of good nuggets of information and references that I will find useful however I found I had a great deal of trouble reading the actual text - I found it boring. The large print, gaps between the lines and the stretched filled spacing of each line made it difficult to quickly scan paragraphs and grasp the gist of what was being said, even when rereading. The grid diagrams were also problematic - they all had the same look - there was little that was memorable about them. The authors also often used round about wording where more direct statements would have been clearer.

As an experiment I typed a couple of random paragraphs from the text and found that they made a lot more sense. I also showed the text around to some of my co-workers and got the same reactions. Given the title of the book it is somewhat ironic that it should have this kind of a problem, but the book deals with principles for the automated transformation of content, not effective presentation style.

Better editing would have made a better book.

Component modeling, analysis of information exchanges, and
application services usage patterns are critical areas to focus
on in designing internal and external interfaces exposed by
enterprises, ASPs/SaaS, and other consumer-oriented internet
services. We have many good examples of scalable, evolvable,
easy to integrate and interoperable Web Services API in the
consumer-oriented internet industry currently. The areas
covered in the DOCUMENT ENGINEERING is very relevant to
architects, product managers, developers and technology
executives. I especially found the design patterns and process
discussion helpful. I would recommend this book to anyone
interested in services oriented application platforms, internal
and external enterprise integration to employ in the design
phase since it covers an effective methodology of designing
interfaces based on the document-centric component model.

Zahid Ahmed
San Jose, CA

The book is a refreshingly understandable approach to explaining Service Oriented Architecture, Web Services and the Semantic Web. Other texts often drown the reader in hugely verbose XML examples. But here, the authors achieve clarity in discussing the essence of the above concepts. The XML snippets are clear, without being overly long.

You can also see why interoperability issues might inevitably arise in a loosely coupled Web Services environment. Often due to differing semantic meanings attached to the same fields in a common document structure. The book touches upon hard problems of ontologies and how the different meanings might be accomodated in a realistic deployment of distributed Web Services.

Document Engineering is a practical exploration of the role documents play in the nexus of contracts that drive modern businesses. The interdisciplinary approach put forward here, taking document engineering out of the realm of pure software engineering, is eye opening and provides some real insight into what it takes to make Service Oriented Architectures work in the real world. This is an absolute must read book for anyone seriously considering developing an XML based document integration strategy.

I was lured by the title and reviews hoping to get insight on how to generically define large documents that could easily be extended as requirements change and consumed by a wide variety of clients using different arbitrary programming languages. I didn't learn anything new about extensibility, and programming languages are absent from this book.

Instead the book seems to be a somewhat dated look at a high level process for using documents in a service oriented architecture. The calendar example application seems too simple to translate into a more complex real life application. The approach described for "document engineering" is much more reminiscent of waterfall style development approaches rather than lean/agile techniques.

I also found the text very difficult to read; it's very dry.

Perhaps this book is useful for some, but it certainly isn't helpful for everybody.

I like this book since it explains EDI in a very simple way. This is a book I would recommend for those trying to grasp what EDI is all about.

I bought this book two days ago in an effort to learn more about EDI and how I can get started. I received it this morning, and was finished by noon.

It's great if you want a sales pitch for EDI, but there's no real useful information contained. I figured there would at least be a section near the end where I could "Get more information on EDI" or "Where to go from here".

If you're looking for a little technical information, don't look here. There's not a morsel of techno info.

I've now wasted money and half a workday, and still have no idea where to go from here.

Of course there don't seem to be too many viable alternatives short of hiring a consulting firm...

This book is very well written. It is an excellent source for anyone who plans to get involved in the world of EDI. It provides all the basics, but there are some other useful topics for the advanced readers. I would recommend this book for anyone who plans to be involved in an EDI project.

Our company is an EDI Systems Integrator for the Book Publishing Industry. We are now recommending this book as a good non-technical introduction for our customers new to EDI. Rich Vettel, president Unitech EDI Systems

It is suitable for every EDI/EC beginner. Not to difficult to understand, even you are not a technical person. IS manager must read this book.

Taking into consideration that this is a text book and I've only gotten through the first 3 chapters I find it a very informative, in-depth, and readable book. The information is provided in a manner that the average, non-computer, person can understand and absorb. I am an older adult returning to school after 20 years. It is hard to retain almost anything these days but this text makes it easier than most. I won't say its easy, that is a matter of personal opinion, but easier in the sense that you can read a section and still realize that you understand what it is you just read and that it flowed smoothly from the previous section; incorporating previously stated ideas and information while addressing new ones.

I read the third edition front to back. If the forth edition is anything like the third, you won't be disappointed.

i want to know more about local area networks

one of the best books in its field, gives details yet doesn't go deeper than what business students would like, its language is easy yet specific and use network jargons. in short, buy it.

I just finished a course on data communications at a local college. Since I knew absolutely nothing about the topic. I had nowhere to go but up. Mr Goldman's book is very readable and is chock filled with charts, checkoff lists and such that I will use when I get into the IT field. His objective to get the reader to think in terms of applying the material rather than memorizing it. He suceeds. Does he have any other related works out there? I'll buy them.

This book failed to provide deep level explainations for how BizTalk Server processes EDI formatted data. Many topics are glossed over and in some cases he simply states that a topic is beyond the scope of the book. At less than 200 pages this book serves as a primer for EDI message processing using BizTalk Server. I found the product documentation much more helpful than most of the rubish found in this book.

Also, a fair number of the "Examples" failed to work. In the case of the AS2 configuration (one of the highest priority topics for me), the book shows properties that don't even exist.

Apress let me down again. :(

There is not much material out there on the subject of EDI and BizTalk. Considering that, this is a very useful book. It has several useful exercises. It is definitely helpful if you have a working knowledge of BizTalk Server to get the most benefit from this book.

[...]

While EDI is straight forward in concept to understand it can be difficult to implement. This book is targeted towards the developer and architect tasked with crafting a B2B EDI solution and does a great job at detailing what needs to happen to make this task possible on the BizTalk 2006 R2 platform.

This book does not focus on the business specifics around EDI, but rather immediately jumps into detailed and concrete examples that can easily be extended into the real world. There are many EDI features with BizTalk 2006 R2 that can only be understood after working with the product across many projects. This book will reduce the time required experimenting with the tool just to understand the new features. I recommend this book to anyone working with EDI and BizTalk 2006 R2.

For understanding EDI processing in 2006 R2 this is a great material. It has all forms for processing like EDI, AS2 etc. The Book gives a brief description about all these Architectures and then comes the good part, the samples created and Tested which you can test at your machine.

The samples are so easy to deploy with minimum pre-requisites and test them thoroughly along with a book to understand what we have done. We can download the samples from a web page directed in the Book.

Even if you are newly introduced to EDI processing through Biztalk, there is no worry. All you need is a little hands on how Biztalk translates the EDI data. From there the book has all the techniques involved in resolving the data, retrieving and mapping the information and Orchestrate the message for processing as you wish.

The Book also briefs about the deployment and production support considerations and reporting updates with the new Server. In a nutshell this is the perfect material for understanding EDI processing in 2006 R2 environment.

Electronic Data Interchange (Edi : Using Electronic Commerce to Enhance Defense Logistics)

At 268 pages, this book is shorter than many programming books.

It describes developing for an open (jailbroken) iPhone. After the first edition sold out, this is the version with minor updates for the iPhone 2.x firmware. This book teaches you about the iPhone APIs used by the built-in Apple applications, but you should be aware that it does NOT target the Apple iPhone SDK, and does NOT guide you in developing apps for the AppStore, though the code will generally be applicable for AppStore applications.

It begins with a description of the process of jailbreaking, getting the compiler set up either on the Mac (hard) or the iPhone itself (trivial: http://soi.kd6.us/2008/09/27/so-i-made-my-iphone-say-hello-world/) and an introduction to Objective-C.

This book presents many complete example programs using the various iPhone UIKit controls, and presents information on Quartz (2d graphics) and the sound libraries.

It does not describe OpenGL ES (for high-performance/3D graphics) or web applications and APIs.

I found occasional editing errors - more than I'd expect in an O'Reilly Second Edition, ranging from typos (Quarts instead of Quartz) to old text describing an updated code example, to copy-and-paste errors between similar sections. Nothing too egregious, but distracting.

I list this book and other books that target the SDK in my Amazon Store: http://astore.amazon.com/iaw-20

The book is complete and detailed. It gives the conmputer developer what they need to know in order to comply with EDI standards

This book describes SET payment process & protocal standands clearly. I think someone who is new to SET process can read this book and it would definetly be helpful.