698:
easier "reference," because they are thousands of products, certifications, exams...etc, therefore we refer as by their company name, suite name or commonly understand name, hence in templates that is why people reduce things like LLC, Corporation, JT...etc. Suite name serve a good purpose in communications, but not explanation. Similar in essay you say "The man is made of clay" than to say "I think the man is made of clay" (the word I think is not necessary, because it doesn't serve as any support nor explanation and in the case of the article it also doesn't serve the purpose of explanation). --
201:
180:
80:
53:
148:
22:
285:
211:
378:
662:) 07:45, 20 December 2016 (UTC) The article is about WebSphere and therefore the products in them are already understated by the headings. I don't think we should add them, it is unncessary and make it look like a form of advertising. The ones that include both Websphere and other non-Webpshere branded products, I didn't remove them for easier understanding. --
609:? After some major revisions over the last week, the article is looking like it could stand alone now. I want to avoid going overboard by populating the article with too much information, but it is a very complex product, and it seems like I could always add more! Please let me know if there are still major gaps in the article or any other feedback. Thx!
554:
contributor to this article, but it looks like I'm the only one with any real motivation to work on this. So to the powers that be, will you please give this article till
Wednesday of next week before merging or moving (and I will be working till then on adding the bulk of info that will qualify this article to stand alone)?
733:
Further more, common names have to verifiable. Using
Silicon Graphics, Inc. as an example, there are many reliable sources that refer to the company as "SGI". In fact, the only authoritative source on this matter (the common name of this company), Silicon Graphics, Inc., refers to themselves as "SGI"
306:
576:
article to develop for a while, Rebekah. I'll tag it as "under construction" (although this is liable to be removed if no work actually gets undertaken!). My comment about starting in user space was really for any future articles that you might want to develop on a piece-by-piece basis. Note that
697:
The purpose of an article is to introduce and explain about the products and maybe include things like scope, goals...etc. In the article if we remove the WebSphere suite name, it is more clear and precise about what the product focus on, the suite name is not important. Abbreviations are made for
627:
It does look like the article is now contains sufficient information about the subject itself to require a separate article. I am therefore withdrawing the merge suggestion, especially since no-one else has volunteered any opinion on the matter. I would still recommend that a link is placed in
553:
Forgive me, this is my first attempt creating a wikipedia page. THANK YOU Mighty
Warrior for your pointer in developing under my profile first and then moving to this page after I've got the info... however, I was hoping that the community effort aspect would take over and I wouldn't be the sole
827:
There was a strong "keep" consensus for this article six years ago, rejecting the notion that the product's entry here was prophetic rather than encyclopedic. But now, the history is a single sentence, 95% of the article is a product catalog, and there are no references, just a single "further
538:
contains very little concrete information apart from a large collection of external links, most of which are duplicates or near duplicates of ones in this article. I suggest that the small amount of information in the RFID article could be easily merged into the main WebSphere one. --
677:
No, if the position is "Websphere
Developer" then it should be called that for disambiguation purposes, the exact reason why we refer to MSCEs as MSCEs and not just engineers. It is only advertising if it says, "Become one now! Sign up at webspheredeveloper.com," which it
445:
I've spent the last year and a half trying to develop middleware with different components and they're all rubbish, bar MQ. The concepts, although well thought out, are generally fundamentally flawed, but the part that makes them difficult to use is the fact they're so
802:
The amount of external links in this article is really kind of ridiculous. I mean, I think the idea of an exhaustive list of the products within the
Websphere brand is way too much regardless, but having external links for each one is in clear opposition to
828:
reading" entry. I've done a cursory Google search to find reliable sources and only find advertising. Is this article as pointless as it looks to me? Should it just redirect to the listing of IBM products? Or is there some potential?--
727:
states that the company is called "Silicon
Graphics, Inc." and then explains that the company is commonly referred to as "SGI" and only then proceededs to use the common name through the rest of the article as per
713:
How is it more precise to use a name that is not used? Take "Portlet
Factory" for example. How is it possible for someone unfamiliar with WebSphere to determine, from context, that "Portlet Factory" refers to
409:
This article has not been written to be understood. It is confusing, it does not indicate how WebSphere is suppose to work, it rather lists a bunch of parts or subproducts that have not meaning to the reader.
632:
to the new article, and other opportunities to link it into articles are explored. Care must also be taken not to let the new article sound too much like an advert or sales brochure. Regards. --
754:
Also in the WebSphere branding was the Micro
Environment Java Virtual Machine for Palm OS. Hasn't been updated since version 5.7.2 was released circa 2007, 5.7.1 was released in 2005.
416:
I agree completely. After seeing IBM's own site dealing with WebSphere, and finding nothing except enterprise-style yammering, I was really hoping
Knowledge could do a better job.
715:
525:
787:
891:
911:
847:
I would say it has become an important set of products, and now this page is functioning as a disambiguation page. So it will not be useful to redirect it.
257:
566:
489:
460:
548:
138:
906:
267:
856:
755:
718:" when it is not explained in the article or linked to the relevant article stating the full name? (Note that it was linked in previous revisions.)
618:
485:
641:
594:
356:
388:
417:
504:
What does the heading "Headline text" mean? Is this a place holder for a real heading or is it a correct heading relating to WebSphere?
671:
649:
519:
876:
128:
463:
886:
791:
499:
493:
162:
691:
478:
837:
433:
707:
871:
916:
881:
768:
926:
780:
Also, columns of the table were re-arranged to have the most modern version at the left of the table and not at the far end.
743:
511:
346:
841:
783:
585:
for the article to stand on its own, or not. That's really what this discussion hopes to decide, one way or the other. --
104:
655:
233:
931:
921:
814:
773:
The section "WebSphere
Compatibility Matrix" which is specific to WebSphere product was moved to the corresponding "
774:
817:
901:
322:
87:
58:
896:
452:
As far as I'm aware, Microsoft's BizTalk server is a similar competing product. From the above, what is "MQ"?
224:
185:
157:
63:
834:
232:
articles on Knowledge. If you would like to participate, please visit the project page, where you can join
33:
763:
602:
573:
535:
527:
318:
614:
562:
442:
Not at all, it's a set of middleware components that are built on top of another development platform.
313:
290:
777:" article which is specific at the WebSphere product, whereas this page is about the WebSphere brand.
425:
852:
822:
515:
384:
321:
on Knowledge. If you would like to participate, please visit the project page, where you can join
103:
on Knowledge. If you would like to participate, please visit the project page, where you can join
831:
807:, which says that they shouldn't be used within the body of an article. They need to be removed.
723:
When using common names, the full name is also mentioned, not completely ignored. The article on
659:
637:
590:
544:
21:
797:
100:
811:
610:
558:
474:
39:
682:. I might go and ask some of those who have contributed to this article for their opinions.
848:
507:
377:
8:
759:
582:
633:
586:
540:
808:
724:
703:
667:
470:
404:
749:
739:
687:
421:
216:
200:
179:
865:
629:
606:
578:
804:
456:
699:
663:
581:, even when the article is expanded. It all depends on whether there is
735:
683:
96:
229:
147:
92:
79:
52:
305:
284:
210:
438:
So basically, it's a development platform like PHP or ASPÂ ?
601:
Dear Mighty Warrior, what are the criteria for merging the
577:
there still might be a case for merging the content into
469:
Can someone give an example or two of how it's used?
317:, a collaborative effort to improve the coverage of
228:, a collaborative effort to improve the coverage of
206:
91:, a collaborative effort to improve the coverage of
484:
Perhaps, competing products are Jboss and Tomcat --
863:
892:Start-Class software articles of Mid-importance
912:Low-importance WikiProject Business articles
19:
907:Start-Class WikiProject Business articles
734:in their communications where possible.
864:
372:
311:This article is within the scope of
222:This article is within the scope of
85:This article is within the scope of
15:
650:Removing Websphere on products name
38:It is of interest to the following
13:
146:
14:
943:
877:Low-importance Computing articles
887:Mid-importance software articles
775:IBM WebSphere Application Server
434:Competing products/comparisons ?
376:
304:
283:
209:
199:
178:
78:
51:
20:
805:the guideline on external links
387:on 18 June 2007. The result of
383:This article was nominated for
351:This article has been rated as
262:This article has been rated as
133:This article has been rated as
113:Knowledge:WikiProject Computing
872:Start-Class Computing articles
792:20:08, 14 September 2010 (UTC)
769:WebSphere compatibility matrix
242:Knowledge:WikiProject Business
116:Template:WikiProject Computing
1:
917:WikiProject Business articles
882:Start-Class software articles
744:06:47, 15 November 2008 (UTC)
708:21:54, 14 November 2008 (UTC)
325:and see a list of open tasks.
248:WikiProject Business articles
245:Template:WikiProject Business
236:and see a list of open tasks.
155:This article is supported by
107:and see a list of open tasks.
927:Mid-importance Java articles
842:21:47, 8 February 2013 (UTC)
692:05:00, 7 November 2008 (UTC)
672:21:34, 5 November 2008 (UTC)
7:
764:09:50, 20 August 2010 (UTC)
603:IBM RFID Information Center
574:IBM RFID Information Center
536:IBM RFID Information Center
528:IBM RFID Information Center
494:01:30, 2 October 2010 (UTC)
10:
948:
642:09:08, 17 April 2008 (UTC)
619:06:12, 17 April 2008 (UTC)
595:21:03, 11 April 2008 (UTC)
567:19:01, 11 April 2008 (UTC)
549:12:16, 11 April 2008 (UTC)
479:03:46, 6 August 2008 (UTC)
464:12:05, 30 April 2007 (UTC)
357:project's importance scale
331:Knowledge:WikiProject Java
268:project's importance scale
139:project's importance scale
932:WikiProject Java articles
922:Start-Class Java articles
857:13:10, 14 June 2015 (UTC)
818:17:53, 30 July 2012 (UTC)
716:WebSphere Portlet Factory
520:00:41, 3 March 2008 (UTC)
426:05:35, 14 June 2015 (UTC)
350:
334:Template:WikiProject Java
299:
261:
194:
154:
132:
73:
46:
572:No problem to allow the
500:Heading "Headline text"
902:All Computing articles
459:is a messaging engine
151:
101:information technology
28:This article is rated
897:All Software articles
150:
88:WikiProject Computing
225:WikiProject Business
158:WikiProject Software
152:
119:Computing articles
34:content assessment
823:Revisit deletion?
530:into this article
522:
510:comment added by
399:
398:
371:
370:
367:
366:
363:
362:
278:
277:
274:
273:
173:
172:
169:
168:
939:
725:Silicon Graphics
680:clearly does not
611:Rebekahalnablack
559:Rebekahalnablack
505:
380:
373:
339:
338:
335:
332:
329:
314:WikiProject Java
308:
301:
300:
295:
287:
280:
279:
250:
249:
246:
243:
240:
219:
214:
213:
203:
196:
195:
190:
182:
175:
174:
121:
120:
117:
114:
111:
82:
75:
74:
69:
66:
55:
48:
47:
31:
25:
24:
16:
947:
946:
942:
941:
940:
938:
937:
936:
862:
861:
849:Graeme Bartlett
825:
800:
771:
752:
652:
532:
512:202.175.143.143
502:
436:
407:
336:
333:
330:
327:
326:
293:
247:
244:
241:
238:
237:
217:Business portal
215:
208:
188:
118:
115:
112:
109:
108:
67:
61:
32:on Knowledge's
29:
12:
11:
5:
945:
935:
934:
929:
924:
919:
914:
909:
904:
899:
894:
889:
884:
879:
874:
860:
859:
824:
821:
799:
798:External links
796:
784:91.178.115.186
770:
767:
751:
748:
747:
746:
730:
729:
720:
719:
695:
694:
651:
648:
647:
646:
645:
644:
622:
621:
598:
597:
531:
524:
501:
498:
497:
496:
467:
466:
450:
449:
448:
447:
435:
432:
431:
430:
429:
428:
406:
403:
401:
397:
396:
389:the discussion
381:
369:
368:
365:
364:
361:
360:
353:Mid-importance
349:
343:
342:
340:
323:the discussion
309:
297:
296:
294:Mid‑importance
288:
276:
275:
272:
271:
264:Low-importance
260:
254:
253:
251:
234:the discussion
221:
220:
204:
192:
191:
189:Low‑importance
183:
171:
170:
167:
166:
163:Mid-importance
153:
143:
142:
135:Low-importance
131:
125:
124:
122:
105:the discussion
83:
71:
70:
68:Low‑importance
56:
44:
43:
37:
26:
9:
6:
4:
3:
2:
944:
933:
930:
928:
925:
923:
920:
918:
915:
913:
910:
908:
905:
903:
900:
898:
895:
893:
890:
888:
885:
883:
880:
878:
875:
873:
870:
869:
867:
858:
854:
850:
846:
845:
844:
843:
840:
839:
836:
833:
820:
819:
816:
813:
810:
806:
795:
793:
789:
785:
781:
778:
776:
766:
765:
761:
757:
745:
741:
737:
732:
731:
726:
722:
721:
717:
712:
711:
710:
709:
705:
701:
693:
689:
685:
681:
676:
675:
674:
673:
669:
665:
661:
657:
656:121.242.29.87
643:
639:
635:
634:MightyWarrior
631:
630:IBM WebSphere
626:
625:
624:
623:
620:
616:
612:
608:
607:IBM WebSphere
605:article into
604:
600:
599:
596:
592:
588:
587:MightyWarrior
584:
580:
579:IBM WebSphere
575:
571:
570:
569:
568:
564:
560:
555:
551:
550:
546:
542:
541:MightyWarrior
537:
529:
523:
521:
517:
513:
509:
495:
491:
487:
483:
482:
481:
480:
476:
472:
465:
462:
461:84.51.146.100
458:
455:
454:
453:
444:
443:
441:
440:
439:
427:
423:
419:
415:
414:
413:
412:
411:
402:
394:
390:
386:
382:
379:
375:
374:
358:
354:
348:
345:
344:
341:
337:Java articles
324:
320:
316:
315:
310:
307:
303:
302:
298:
292:
289:
286:
282:
281:
269:
265:
259:
256:
255:
252:
235:
231:
227:
226:
218:
212:
207:
205:
202:
198:
197:
193:
187:
184:
181:
177:
176:
164:
161:(assessed as
160:
159:
149:
145:
144:
140:
136:
130:
127:
126:
123:
106:
102:
98:
94:
90:
89:
84:
81:
77:
76:
72:
65:
60:
57:
54:
50:
49:
45:
41:
35:
27:
23:
18:
17:
829:
826:
801:
782:
779:
772:
753:
696:
679:
653:
556:
552:
534:The article
533:
503:
468:
457:Websphere MQ
451:
437:
408:
400:
392:
352:
312:
263:
223:
156:
134:
86:
40:WikiProjects
809:Writ Keeper
506:—Preceding
471:Badgerclark
30:Start-class
866:Categories
756:Bizzybody
583:consensus
446:unstable.
110:Computing
97:computing
93:computers
59:Computing
508:unsigned
486:OmadaXam
405:Untitled
385:deletion
239:Business
230:business
186:Business
64:Software
750:Palm OS
355:on the
266:on the
137:on the
700:Ramu50
664:Ramu50
526:Merge
99:, and
36:scale.
736:Rilak
684:Rilak
557:Thx.
418:Wvxvw
853:talk
794:Ben
788:talk
760:talk
740:talk
728:MoS.
704:talk
688:talk
668:talk
660:talk
638:talk
615:talk
591:talk
563:talk
545:talk
516:talk
490:talk
475:talk
422:talk
393:keep
391:was
328:Java
319:Java
291:Java
347:Mid
258:Low
129:Low
868::
855:)
790:)
762:)
742:)
706:)
690:)
670:)
654:--
640:)
617:)
593:)
565:)
547:)
518:)
492:)
477:)
424:)
165:).
95:,
62::
851:(
838:W
835:P
832:T
830:~
815:â™”
812:⚇
786:(
758:(
738:(
714:"
702:(
686:(
666:(
658:(
636:(
613:(
589:(
561:(
543:(
514:(
488:(
473:(
420:(
395:.
359:.
270:.
141:.
42::
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
