Talk:SORCER

note about archiving

To reduce clutter here, we manually archived all discussions, some of which may still have been active. Please see "Archive 1" over to the righthand side, to view the previous info. Feel free to open a new section here, if you want to discuss something in the archives further (don't edit the "Archive 1" contents directly though... too confusing!). I've already copied the sourcing-and-tone sections from the archives, see below. 74.192.84.101 (talk) 18:02, 30 December 2013 (UTC)

notability and sourcing

Worthwhile reading — WP:42 is the answer to most questions about new articles, in the wikiverse (gratitude to TRPoD for this link). Summary of the sources-list below is basically....

1. DoD, the multiyear multi-million-dollar supergrants by the USAF+NIST and NSFChina (plus hints of Ulyanovsk) ... and the classified weaponized-aerospace work these indicate. Such work is not useful as RS now, today, because WP:V demands the info be *published* aka available to the public... and wikiLeaks doesn't count as RS methinks... or does it? Hmmmm. Point is, this stuffwill be declassified someday. And it exists now, today. We cannot *use* it today, for sourcing the article, but that doesn't mean we have to pretend this set of classified sources, published-yet-top-secret, doesn't exist — when evaluating the public sources below, it can lend some perspective to what they don't say.
2. UK, the 2007 U.Cranfield lit-review & industry-survey (a solid secondary source), plus the 2009 G.Goteng PhD from same place. WP:SOURCES sez, "academic peer-reviewed pub's are usu the most RS". WP:SCHOLARSHIP sez, "PhD [theses]...can be used but care should be exercised".
3. RU, the 2007/YYYY/2013 newspaper articles in Russian (I've asked somebody who "can read a few words of Russian" to give us rough assessment of depth... anybody amongst us here know Cyrillic?)
4. ZH, the 2010 PhD and 3+ peer-reviewed journal articles by Nan Li (most of the work in Chinese but that is no hindrance to wikiNotability though it is a barrier to gauging depth... Clover1991 of DUROMAC fame has offered to help us with translating the mandarin if kazumo is busy), plus the 2011 and 2013 Beijing Jiaotong University PhD (students of Nan methinks?); *maybe* the ZH edu-news section; additional evidence, tho not themselves RS, are the two Master's theses. Again WP:SOURCES and WP:SCHOLARSHIP
5. US, the 2013 iosPress/AFRL papers (peer-reviewed by the 20 members of the conf-board and the 3 members of the editorial-subset which were mostly Aussies), plus the 2012 DaytonThesis PhD (which has a public-domain chapter on SORCER beginning on page 230... decent tone... might be the best place to start on the rewrite of mainspace?); additional evidence, tho not itself RS, is the WrightState Master's. SorcerDotCom in Poland, and SorcerSoftDotOrg at TTU in Texas, are the entities directly responsible for SORCER; the USAF and WPAFB are funding Prof.Sobolewski, U.Dayton, WrightSt.U, and various other stuff via the MSTC/AFRL folks in Ohio.

Meanwhile, as Tim and ScopeCreep and TRPoD and Garamond and others are analyzing whether this list of sources is bulletproof wikiNotability, safe from all future deletion-attempts, Pawelpacewicz and Martijn and Prubach and myself can try to start working on WP:TONE, and on clearly explaining the meaning of SORCER/nsh/exertions/mograms/SOOA/COLA/PEPSI/7UP/etc to the readership.

Fiddle Faddle's suggestion "that the first task is to show and prove notability though" ... there is one, and only one, way to prove wikiNotability. That is, namely, to find multiple independent Reliable Sources, which cover SORCER itself (specifically), in some amount of depth. Finding good sources, and proving wikiNotability, are the same thing. Nothing more is required, but also, nothing less is required. There is a difference between a *secondary* source, and an *independent* source. If anyone finds independent sources, fact-checked by an independent journalist's professional editorial board, or peer-reviewed by independent referees at some journal's science-board, please add them to the list below. Thanks for improving wikipedia. 74.192.84.101 (talk) 18:02, 30 December 2013 (UTC)

---

PLEASE EDIT THESE SOURCE-EVALUATIONS DIRECTLY, TO FILL IN MISSING DETAILS. Thanks much.  :-)  74.192.84.101 (talk) 18:27, 13 December 2013 (UTC)

some WP:ABOUTSELF sources

Mwsobol#0 sorcersoft.com (or maybe sorcer.com ??), company to market GUI systems built on top of open-source code from sorcersoft.org below, in Poland where Mwsobol teaches at PJIT Mwsobol#1 url == http://sorcersoft.org/publications/papers/2012/6.2012-5520.pdf title == "Efficient Supersonic Air Vehicle Analysis and Optimization Implementation using SORCER" collaborative university == Texas Tech University 2002-2009 , spun off as of 2010 into an open source project

AFRL / IOSPRESS x2 or x3

Shortname == iosPress#1 (there is also another one by the same author/publisher... I will add that later on).done Suggested as WP:RS to satisfy WP:NOTE. title == Physics-Based Distributed Collaborative Design for Aerospace Vehicle Development and Technology Assessment pages == 198-215 url == http://ebooks.iospress.nl/publication/34808 author == Raymond M. Kolonay possibly conflict == Director of MSTC/AFRL, an organization that is an enduser of Sorcer. Pawelpacewicz is of the opinion that therefore no COI exists; however, methinks AFRL is not just an enduser, but also the collaborator-slash-employer-slash-funder of the SORCER work (Professor Sobolewski among others... who is currently "Director of SORCER Lab in collab with AFRL/WPAFB and PL-JP Inst of IT"[1]), so this is somewhat of a grey area, Kolonay is a collaborator in SORCER research as well as an enduser... AFRL isn't just a typical customer in other words, cf the early history of Jeep vehicles during WWII. Background: the USAF is using Sorcer in their (aerospace-research) environment, and developing computational models to address the physics-based distributed collaborative design (i.e. aerospace-design-engineers using local exertion-scripts implemented via SORCER as the substrate-platform) for aerospace vehicle development. summary == One AFRL mission is to develop (and assess!) next-generation aerospace-system technologies i.e. fighters/bombers/missiles/etc. Currently, due to time/personnel/funding constraints, the tech-assessment work is traditionally achieved using empirical relationships and historical data associated with systems developed previously (i.e. earlier-generation fighters/bombers/missiles/etc)... this approach is fast, but not necessarily accurate, especially when neither empirical nor historical info exists! (The first version of a radical new bomber-design for instance.) Inaccurate assessment leads to poor USAF decisions about investment into future aerospace-systems. AFRL has an AerospaceSystemsDirectorate with the MultidisciplinaryScienceAndTechnologyCenter; these MSTC folks are under the author Kolonay. This group is creating tech-assessment-and-design-exploration apps/methods/processes, which are physics-based (the tech-assessment depends on weight/lift/drag/etc ... as opposed to historical data from wind tunnels and combat engagements and such ... whereas weight/lift/drag are known at CAD-design-time without needing to build a physical prototype). The aerospace-designers who work elsewhere in the USAF can work on their CAD-based designs, run SORCER-based apps that perform tech-assessment, and get quantitative estimates of cost/strength/firepower/etc (aka affordability/survivability/lethality/sustainability), which are the things USAF leadership && Congress uses to make funding-decisions. Basically, given merely an AutoCAD diagram of a radical new bomber-design, the MSTC tech-assessment app usesSORCER (how specifically?) to predict the quantitative real-world manufacturingCost/offensiveCombat/defensiveCombat/etc performance-characteristics of the hypothetical bomber, partly by running mission-simulations of various bomber-configs (different fuel-load crew-size weapon-selection whatnot). The new MSTC tech-assessment app takes the same amount of time as traditional tech-assessment. Aerospace-designers get a quantifiable usefulness-prediction-metric, repeated each time they incrementally adjust their CAD-design, and USAF leadership (and taxpayers) get better decision-making about funding for new aerospace-systems. publisher == iospress.nl was publication peer-reviewed aka refereed == Yes. By the conference board (see full list of 19-besides-Sobolewski in comment-section). Here you have the information about the committee: (https://www.engineersaustralia.org.au/20th-ispe-international-conference-concurrent-engineering/committee-information), And here you can find confirmation (at the bottom) that according to the rules of the conference proceedings each paper has to be peer reviewed: https://www.engineersaustralia.org.au/20th-ispe-international-conference-concurrent-engineering/presenter-information IOS Press confirms as well their peer-review process here:http://www.iospress.nl/service/authors/open-library-ios-press-open-access-option/ Here You have another organization which is using peer-review process by IOS Press: http://www.oapen.org/peerreview?page=ios url of iospress editorial board == Cees Bil, John Mo, Josip Stjepandić - You can find it on their page:http://ebooks.iospress.nl/book/20th-ispe-international-conference-on-concurrent-engineering is publisher independent == If I understand well your intention (correct), you would like to check if they are independent from authors-or-the-employers-of-authors of the SORCER work (correct). In my opinion the proof for this type of independency is the information on Wikipedia (https://en.wikipedia.org/wiki/IOS_Press) which shows that it was established 26 years ago, and that they are publishing approximately 90 international journals and releases and about 130 booktitles annually. (74 agrees with Pawelpacewicz... IOS press is not run by USAF nor any of the SORCER folks, but is an independent scientific publisher... however, interestingly enough, IOS Press does *not* provide their own professional editorial board, but rather, uses a subset of the peer-reviewers as their editors.) As such they’re not dependent from the author (correct) or any of the institutions for which the author works or had worked previously. (correct) is publisher a vanity press == Pawelpacewicz says: as an independent publisher of peer-reviewed scientific journal the publisher definitely doesn’t accept paid-for papers. 74 says, this seems to be mostly true. In fact the folks at IOS Press *do* require payment up front, as you can see in the link Pawelpacewicz provides, to the tune of a thousand euros per paper published. However, this is the business model of the publisher... they do not charge subscription-fees to the recipients of the papers (which is why wikipedians can see the full paper sans any paywall — the license is even Creative Commons of some sort). <grin> All papers that IOS Press publishes this way are from peer-reviewed scientific conferences (in this case the 20th ISPE ICCE), and the editorial board is also from academia slash industry (in this case RMIT*2 plus a firm in Germany). IOS is a member of STM, which also includes AAAS / ACS / AIP / AMS / AMA / APS ... that was just the first few which jumped out at me.  :-)   Seems legit; wikipedia already has about 20 computing-articles which cite iospress, plus about 20 medical-articles. was book printed, or ebook only == both: http://www.iospress.nl/book/20th-ispe-international-conference-on-concurrent-engineering/ date == if you click on the link right to “Ebook” You will go to page: http://ebooks.iospress.nl/book/20th-ispe-international-conference-on-concurrent-engineering and there is info that it was published in 2013 Shortname == iosPress#2 (Mwsobol#2) url == http://ebooks.iospress.nl/publication/34826 (here is the TOC[2] for the proceedings) title == Parametric Mogramming with Var-Oriented Modeling and Exertion-Oriented Programming Languages authors == Michael Sobolewski / Scott Burton / Raymond Kolonay author homes == SORCER Soft / ((unknown)) / MTSC of AFRL editors == Cees Bil / John Mo / Josip Stjepandić editor homes == RMIT University Australia / RMIT University Australia / PROSTEP AG Germany editorial review == 2013 Proceedings of the 20th ISPE International Conference on Concurrent Engineering; 978-1-61499-301-8 (print) | 978-1-61499-302-5 (online) peer review == 20th ISPE ICCE board (see list of twenty in the comments) publisher == IOS Press possibly conflict == primary author is inventor of SORCER & FIPRE, third author is director of MTSC at AFRL which collaborates with SorcerSoft ... but editors and most peer-reviewers have no conflicts

20th IPSE ICCE peer-reviewers

reviewer at 20th ISPE ICCE[] reviewer's home university-slash-org conceivableaka possible COI Ahmed Al-Ashaab Cranfield University, UK Amy Trappey National Tsing Hua University, Taiwan Cees Bil RMIT University, Australia Eric Simmon NIST, USA maybe? NIST funded FIPRE, the predecessor of SORCER, was Simmon involved? Essam Shehab Cranfield University, UK Geilson Loureiro INPE, Brazil Georg Rock University of Applied Science, Germany Jerzy Pokojski Warsaw University of Technology, Poland maybe? Sobolewski previously taught here; possible coworker/student? John Cha Beijing Jiaotong University, China John Mo RMIT University, Australia Josip Stjepandic PROSTEP, AG, Germany Kazuo Hiekata University of Tokyo, Japan Mike Sobolewski TTU, Texas, USA YES, works w/ Kolonay && funds FIPRE/SORCER Nel Wognum Wageningen University, The Netherlands Parisa Ghodous University of Lyon, France Rajkumar Roy Cranfield University, UK Ricardo Goncalves UNINOVA, Portugal Richard Curran Delft University of Technology, The Netherlands meh ... IOS Press recently bought out Delft University Press Shuichi Fukuda Stanford University, USA Shuo-Yan Chou Peking University, China

TBD sources which need sorting and filling

Kazumo#12 / Mwsobol#3 url == http://www.scirp.org/journal/PaperInformation.aspx?paperID=22393 title == "Unified Mogramming with Var-Oriented Modeling and Exertion-Oriented Programming Languages" Mwsobol#4 url == http://repositories.tdl.org/ttu-ir/handle/2346/15257 title == Max Berger's research (from Germany), a federated filesystem developed for SORCER Kazumo#11 author == M. Sobolewski editor == Anneke Kleppe chapter title == Chapter 3 "Languages and Mograms" book title == Software Language Engineering: Creating Domain-Specific Languages Using Metamodels 132 url == ?? title == ?? (won best-paper award) authors == Dan Kerrn, M.Sobolewski Kazumo#13 (this is a wiki methinks?) url == http://www.intechopen.com/books/howtoreference/advances-in-computer-science-and-it/metacomputing-with-federated-method-invocation Pawelpacewicz#73 url == http://arc.aiaa.org/doi/abs/10.2514/6.2012-5520 author1 == Scott Burton, American Optimization, LLC; Manager Ph.D. AIAA SEnior Member author2 == Edward Alyanak, Air Force Research Laboratory; Project Engineer Ph.D. AFRL/RQSA AIAA Senior Member author3 == Raymond Kolonay, Air Force Research Laboratory; Principal Engineer Ph.D. AFRL/RQSA AIAA Associate Fellow abstract == describes SORCER's application in ESAV project

NAN LI x3 or x4 of Beijing

Shortname == N.Li 2008. journal paper (Kozamo#1) url == http://www.cnki.com.cn/Article/CJFDTotal-HBGB200804012.htm (in Chinese) authors == ZHANG Rui-hong, LI Nan, CHA Jian-zhong, LU Yi-ping (张瑞红； 李楠； 查建中； 陆一平). type of source == journal paper w/ keyword SORCER title == A collaborative engineering design environment based on SOA (基于SOA的工程协同设计环境). publisher == (Chinese) Journal of Hebei University of Technology, vol.37, no.4 (河北工业大学学报), date == April 2008 (2008年04期), pages == 5 (pp.40-44) Shortname == N.Li 2009. PhD thesis (Kozamo#6) url == http://cdmd.cnki.com.cn/Article/CDMD-10004-2010040776.htm authors == Li Nan (李楠). type of source == PhD Dissertation title == A design activity modelling method for distributed design resources integration (一种用于分布式设计资源集成的设计活动建模方法) , publisher == Beijing Jiaotong University (北京交通大学) date == 2009-10-01 pages == ??pgs?? Shortname == N.Li 2011_A. journal paper (Kozamo#3_A) url == ??website?? authors == Nan Li; Bin Liu; Tao Feng type of source == conference paper w/ keyword SORCER title == A Loosely-Coupled Platform for Urban Traffic Strategic Noise Mapping, publisher == Proceedings of 2011 World Congress on Engineering and Technology, Vol. 07 date == ??year?? (~2011) pages == ??pgs?? Shortname == N.Li 2011_B. journal paper (Kozamo#3_B) url == http://link.springer.com/chapter/10.1007/978-3-642-34522-7_20?no-access=true authors == Wensheng Xu, Nan Li, type of source == conference paper w/ keyword SORCER title == A Loosely-Coupled Platform for Urban Traffic Strategic Noise Mapping, publisher == Proc 2012 Int'l Conf on IT & SW Engin — Lecture Notes in EE, Vol.211, date == 2013, pages == 8 (pp175-182) Shortname == N.Li 2011_C. conference paper (Kozamo#9) url == ??website?? authors == Nan Li type of source == conference paper w/ keyword SORCER title == Resources Integration and Binding in Distributed Collaborative Design Process. publisher == Proceedings of the First International Conference on Networking and Distributed Computing, Hangzhou, China date == 2011 pages == ??pgs?? Shortname == ICDMA'11 aka N.Li 2011_D. Suggested as WP:RS to satisty WP:NOTE. url == http://ieeexplore.ieee.org/xpl/articleDetails.jsp?tp=&arnumber=6051863&queryText%3DA+SOOA+Based+Distributed+Computing+Mechanism+for+Road+Traffic+Noise+Mapping authors == Nan Li ; Tao Feng ; Bin Liu affiliation == Sch. of Mater. & Mech. Eng., Beijing Technol. & Bus. Univ., Beijing, China ; title == A SOOA Based Distributed Computing Mechanism for Road Traffic Noise Mapping pages == 4 pages devoted (pg109-112) to this paper, 1402 pages total in the proceedings (two softcover volumes) abridged abstract == Current traffic noise mapping systems are not ideal for distributed computing in dynamic network. This paper investigates the approach and mechanism of distributed noise map generation based on SOOA. SORCER is employed to build a highly flexible distributed network services space. After that, a SOOA-based computer-aided noise-mapping system is presented. publisher#1 == 2011 Second International Conference on Digital Manufacturing and Automation (ICDMA) publisher#2 == TBD? (IEEE Press maybe?) (IEEE Press maybe?) IEEE – please take a look here:http://www.proceedings.com/13060.html in the product description,another prove you can find here:http://toc.proceedings.com/13060webtoc.pdf (they are official publisher and also methinks the sponsor of the conference) was publication peer-reviewed aka refereed by conference's independent science-board == On the conference’s web page you can find info describing the fact that papers “… are subject to both review and editing.”: http://www.icdma.org/paper-submission was publication fact-checked (or peer-reviewed) by ICDMA editorial-staff == Please see above was publication fact-checked (or peer-reviewed) by IEEE editorial-staff == Confirmation of peer review process by IEEE is described here: http://www.ieee.org/publications_standards/publications/authors/publish_benefits.html "conference papers ... undergo a thorough peer review process before acceptance for publication or presentation ... The reader or conference attendee is assured the research published is strong and credible." url of Proceedings of the ICDMA editorial/referee policy == Please see above http://www.icdma.org/paper-submission is at least one publisher independent == YES not only one: IEEE, ICDMA is publisher a vanity press == IEEE is a very reputable publisher, in particular, for computer science papers and journals and as such is definitely not a vanity press. Please take a look onhttps://en.wikipedia.org/wiki/Institute_of_Electrical_and_Electronics_Engineers conf_date == 5th-7th August 2011 (in Zhangjiajie, Hunan, China) ... published the same year doi == http://dx.doi.org/10.1109/ICDMA.2011.34 isbn == 978-1-4577-0755-1 (print) , 978-0-7695-4455-7 (ebook) cited by == n/a ... "as provided in real-time from CrossRef™, Scopus™ and Web of Science™." Shortname == N.Li 2012. journal paper (Kozamo#2) url == http://mall.cnki.net/magazine/Article/JSJY201208019.htm (in Chinese) authors == LI Nan, FENG Tao, LIU Bin1, LI Xian-hui, LIU Lei (李楠； 冯涛； 刘斌； 李贤徽； 刘磊). type of source == journal paper w/ keyword SORCER title == A distributed computing method for traffic noise mapping based on Service Object-Oriented Architecture (基于面向服务对象体系结构的交通噪声地图分布式计算方法). publisher == (Chinese) Journal of Computer Applications, vol.32, no.8 (计算机应用), date == August 2012 (2012年08期), pages == 4 (pp.2146-2149)

U.Cranfield in the UK

Shortname == Cranfield 2007. chapter (Beavercreekful#1) url == http://link.springer.com/chapter/10.1007%2F978-3-540-72377-6_10 chapter title == Evolutionary Computing within Grid Environment book title == Advances in Evolutionary Computing for System Design Studies in Computational Intelligence, Vol.66 date == 2007 pages == pp 229-248 publisher == Springer Verlag abstract == reviews SOA's including SORCER & FIPRE

RUSSIAN NEWSPAPERS x3

Beavercreekful#3 url == http://vestnik_old.ulsu.ru/issues/878/4 title == Техас готов к сотрудничеству" (Texas is Accepting Research Collaboration) type of source == Russian weekly newspaper publisher == Вестник - Областная еженедельная газета details == in Ulyanovsk Russia, where the largest Russian air vehicles are designed and manufactured, also the home of the Ulyanovsk State University Beavercreekful#4 url == http://vestnik.ulsu.ru/19-1145-07-iyunya-2013/takzhe-chitayte/sorcer-nam-v-pomosch title == "SORCER нам в помощь" (SORCER helps us) type of source == Russian weekly newspaper publisher == Вестник - Областная еженедельная газета date == June 7, 2013 (#19) details == in Ulyanovsk Russia, where the largest Russian air vehicles are designed and manufactured, also the home of the Ulyanovsk State University Beavercreekful#9 url == http://www.ssau.ru/files/editions/polet/2007/13-14-2007.pdf title == В СГАУ выступал профессор Техасского университета publsher == полет N13􏰁14, 30 мая 2007 г. инновационная образовательная программа

CHINESE EDU NEWS x4

Beavercreekful#5 url == http://www.news.uestc.edu.cn/NewsRead.aspx?newsID=57207 title == "Service oriented computing environment for BCA" publisher == News Center for UESTC, China date == 2013-03-21 Beavercreekful#6 url == http://mece.njtu.edu.cn/hzjl/gjhz/6752.htm title == “SORCER and the Service-oriented Programming Model” Beavercreekful#7 url == http://mse.hust.edu.cn/news.php?id=13279 author == 著名计算机专家Michael Sobolewski教授来我院学术交流, date == 发布时间:2013-03-01 发布人: 浏览次数：823 Beavercreekful#8 url == http://www.hustcad.com/content.aspx?typeid=156&id=625 author == Michael Sobolewski教授来我公司进行学术交流 publisher == Tianyu Soft, China Industrial Application Software

PHD THESIS x4 (cf N.Li 2009 above)

Shortname == G.Goteng 2009. PhD thesis (Beavercreekful#2) url == https://dspace.lib.cranfield.ac.uk/bitstream/1826/4423/1/Gokop_Goteng_thesis_2009.pdf title == Development of a Grid Service for Multi-objective Design Optimisation type of source == PhD thesis author == Gokop Goteng abstract == lit review & industry survey ... of grid services ... (including SORCER) date == 2009 publisher == Cranfield University (School of Applied Sciences) Shortname == J.Yu 2010. PhD thesis (Kozamo#7) url == http://cdmd.cnki.com.cn/Article/CDMD-10004-1011102578.htm authors == Yu Jiaqing (于加晴). type of source == PhD Dissertation title == Research on the design process reuse method based on decomposition (基于分解的设计过程重用方法研究) , publisher == Beijing Jiaotong University (北京交通大学) date == 2011-06-01 pages == ??pgs?? Shortname == L.Kong 2013. PhD thesis (Kozamo#8) url == http://cdmd.cnki.com.cn/Article/CDMD-10004-1013279659.htm authors == Kong Lingjun (孔令军). type of source == PhD Dissertation title == Research on servitization method of design resources in the cloud manufacturing environment (云制造环境下的设计资源服务化方法研究) , publisher == Beijing Jiaotong University (北京交通大学) date == 2013-06-01 pages == ??pgs?? Shortname == DaytonThesis. Ph.D. thesis (more than one?) from from University of Dayton url == https://etd.ohiolink.edu/ap:10:0::NO:10:P10_ACCESSION_NUM:dayton1335270317 permalink == http://rave.ohiolink.edu/etdc/view?acc_num=dayton1335270317 title == Incorporation of Computational Fluid Dynamics into Flight Vehicle Preliminary Design author == Ernest D. Thompson thesis == Doctor of Philosophy (Ph.D.) publisher == University of Dayton and OhioLINK home == University of Dayton committee == Franklin E. Eastep PhD (CmteChair & DirectAdvisor), Jose A. Camberos PhD, Raymond M. Kolonay PhD, Ramana V. Grandhi PhD, Rolf Sondergaard PhD cmte homes == Prof Emeritus MechE&AeroE, AdjunctProf MechE&AeroE, AdjunctProf MechE&AeroE, DistinguishedProf Mech&MaterialsE Wright State, SeniorResearcher in TurbineBranch of AFRL PropulsionDirectorate also signed off by == John G. Weber PhD (AssociateDean for U.Dayton School of Engineering), Tony E. Saliba PhD (WilkeDistinguishedProf & Dean for U.Dayton School of Engineering) date == May 2012 possible COI == Dayton is near Wright-Patterson AFB, the USAF facility where AFRL and SORCER are being created, Kolonay is adjunct prof @ dayton, director of MTSC @ afrl, and on thesis cmte. Grandhi supervised the WrightThesis, see above, but is prolly independent unless he get AFRL funding. Sondegaard works for AFRL, and is prolly an actual/potential enduser of SORCER for turbine-design. Seems pretty independent, by typically-insular academic standards, and as a PhD thesis, can be used with care. pages == 261 (content in 243 pages ... around 12 pages specifically about SORCER) subject == Aerospace Engineering (Air Vehicle Design) MLA == Thompson, Ernest. "Incorporation of Computational Fluid Dynamics into Flight Vehicle Preliminary Design." Electronic Thesis or Dissertation. University of Dayton, 2012. OhioLINK Electronic Theses and Dissertations Center. 25 Dec 2013. license == This material is declared a work of the U.S. Government and is not subject to copyright protection in the United States (aka public domain... can quote long passages if we wish)

details of DaytonThesis w.r.t. SORCER/exertions/SOOA

abstract == Nonlinear, high fidelity aerodynamic analysis methods are considered computationally expensive and impractical for use in the preliminary design environment. In lieu of nonlinear methods, linear aerodynamic methods are utilized in the execution of design tasks because of their computational efficiency. Linear codes are considered accurate in low Mach number flight regimes where aerodynamics is generally linear but are not accurate in transonic flight regime due to the simplified assumptions that are required by such codes. This investigation demonstrates that nonlinear aerodynamic analysis methods are necessary when performing design tasks in the presence of nonlinear phenomena. To reduce the cost of using nonlinear aerodynamic analysis, the velocity transpiration boundary condition was employed to simulate surface deformations and control surface deflections. Observations showed velocity transpiration offers significant computational savings when compared to mesh motion enabled codes. To improve turnaround, a distributed computing framework wasadopted to distribute workload and information storage across a network. A comparative design study was carried out comparing linear and nonlinear analysis tools in design. A rectangular wing's structural mass was optimized to perform both a roll and pull-up maneuver while subjected to rolleffectiveness and skin stress constraints. At a subsonic design point, the linear and nonlinear tools produced similar designs. However, at a transonic design point, the tools produced significantly different designs. The addition of aerodynamic shape variables to the design space at the transonic design point led to a further enhanced design. The results of this study reaffirm the notion that nonlinear high-fidelity aerodynamic analysis methods must be utilized when designing vehicles that will operate in nonlinear regimes. Further, several methods were demonstrated that could reduce the cost of using nonlinear analysis methods. SORCER-related technology is covered in reasonable depth: 3 pages in ch#4, 3 pages in ch#5, 6 pages in ap#G. which is a total of a dozen pages out of 243 pages of content, aka about 5% of the thesis. That said, sorcer played *the* key part, allowing the non-linear analysis to be computationally feasible. Exertions are mentioned on about 50% of those dozen pages (and are implicit in most of the rest of them), and services were mentioned in 80% of the dozen (and very implicit in all of them). Kolonay is on the thesis cmte, gets seven bibliography entries (out of 73 total aka ~10%), is credited as author of four SORCER-packages (plus helped write a bit of new code specifically for this thesis). Sobolewski is mentioned thrice: in the bibliography, as the creator of SORCER, plus credit for writing a few of the classes used in the thesis (perhaps specifically *for* this thesis project? unclear). selected entries of the 73-entry bibliography. N. S. Khot, F. E. Eastep, and R. M. Kolonay. Method for Enhancement of the Rolling Maneuver of a Flexible Wing. Journal of Aircraft, 35(5):688{694, September-October 1998 G. Anderson, R. Kolonay, and F. Eastep. Control-Surface Reversal in the Transonic Regime. Journal of Aircraft, 35(5):688{694, September-October 1998 R. Kolonay and M. Dindar. Lockheed Martin 1999 Aeroelasticity Shared Vision Project Final Report. Technical report, General Electric Corporate Research and Development, 1999 P. C. Chen, D. Sarhaddi, and D. D. Liu. Volume 4; ZAERO Theoretical Manual. Wright-Patterson Technical Report 3052, AFRL, Wright-Patterson Air Force Base, OH, February 1999 R. Kolonay, M. Dindar, M. Love, and A. De La Garza. A Methodology of Large Scale Compuational Aeroelasticity For The MDA/MDO Environment. AIAA Paper 2000-4789, AIAA, 2000 F. Eastep, G. Anderson, P. Beran, and R. Kolonay. Control Surface Reversal in the Transonic Flight Regime Including Viscous Effects. Journal of Aircraft, 38(4):653{663, Jul.-Aug. 2001 Air Force Research Laboratory, WPAFB, OH. Air Vehicles Unstructured Solver User's Manual, January 2005 Raymond M. Kolonay and Franklin E. Eastep. Optimal Scheduling of Control Surfaces on Flexible Wings to Reduce Induced Drag. Journal of Aircraft, 43(6):1655{1661, November-December 2006 Ernest Thompson, Raymond Kolonay, Franklin Eastep, and Jose Camberos. Aeroelastic Analysis with Transpiration Enabled Euler Flow Solver. AIAA Paper 2007-2331, AIAA, April 2007. 48th AIAA/ASME/ASCE/AHS/ASC Structures, Structural Dynamics, and Materials Conference, Waikii, Hawaii. Michael Sobolewski. Handbook On Business Information Systems, chapter Chaper 35 Object-Oriented Metacomputing with Exertions. World Scientific Publishing Co. Ore. Ltd., Toh Tuck Link, Singapore, 2010 Appendix G, on printed-page 230-245, is half-a-dozen pages explaining how SORCER works, what service-oriented means, and what exertions are. Recommended, and as pub-domain, we can reuse it if we like. As for the aerospace-design portion of the thesis, SORCER is specifically covered in the chapters on efficient automated numerical optimization of the wing-shape during the design-phase, as well as in the conclusions (nonlinear optimization is made possible by the efficiency gains of SORCER's grid-computing network-parallelism... this is not especially helpful at Mach 0.50 speed, but it hands-down results in a better wing-design for transonic flight at Mach 0.89). chapter four, distributed design optimization, printedPage73==pdfPage90 ...a grid-computing environment... Within SORCER the numerical optimizer and the aeroelastic solvers were exposed as services on a network. SORCER reduced the computational expense of using nonlinear aerodynamic analysis method within the preliminary design environment by allowing the computational workload to be distributed across a network of computers. SORCER allowed for multiple copies of services to be available for use when executing a design study. This effectively reduced the computational expense of using a nonlinear aerodynamic method in the preliminary design environment. chapter four, distributed design optimization, printedPage75&76==pdfPage92&93 The numerical optimization code utilized in this investigation was Design Optimization Tools (DOT). It is developed and maintained by Vanderplaats R&D Inc. The strategy used to solve the optimization problem was constructed within SORCER. ...the code determines ... if [automated] design investigation has converged and if an optimal [wing] design has been discovered. chapter five, conclusions, printedPage111&112==pdfPage128&129 The last set of tasks performed in this investigation involved executing the transpiration enabled aeroelastic solver in the performance of preliminary design tasks. To further improve the computational effciency of the transpiration enabled nonlinear aeroelastic solver, a preliminary design environment was constructed in SORCER. SORCER grid-computing capabilities allowed for design problems to scale across the computation resources available on a network of computers. In the execution of multidisciplinary design optimization studies, the velocity transpiration enabled computational aeroelastic solver proved quite serviceable. The solver generated optimal structural designs at a subsonic design point of Mach 0.50 and transonic design point of Mach 0.89. The designs developed using the [SORCER-based] nonlinear aerodynamic method compared to design produced using [traditional] linear aerodynamics. At subsonic design point [Mach 0.50] the optimal designs produced by the linear and nonlinear methods were very similar there was only 14.69 slugs difference in structural mass. However, at transonic design point [Mach 0.89] the structural design were very different. The design generated using the linear aerodynamic method did not properly account for the presence of a shock wave... ...proof that linear design tools produced completely different designs than nonlinear tools in a nonlinear flight regime. ... If a designer chose to use the design obtained using linear aerodynamic analysis methods as the basis of a detailed design or prototype, the end result could be a costly redesign of the structure because the design failed to account shock wave effects. Through the performance of the design optimization study portion of this investigation, it was demonstrated how distributed computing can be used to accelerate computational analysis through coarse parallelization of computational effort. Analysis tools were deployed across a network of computers as services. Information was transported from analysis service to analysis service via web servers, network proxies. Data was passed within service context data structures. SORCER's framework allowed for analysis tasks to be executed concurrently or sequentially depending [on] data dependencies. The design process was accelerated through the exploitation of this parallelism. A unique aspect of this work was the fact that the optimization design strategy was implemented within the design framework. One programs the network as oppose to programming individual computer systems. The framework calculated exact sensitivities via finite difference directly, selecting the appropriate network services to dynamically compute a gradient or function evaluations. The framework permitted some failure recovery in the analysis. Code was implemented to check for corrupt output. Intermediate results were archived in Java objects. Through execution of this investigation several ideas could be implemented to improve computational efficiency of nonlinear CFD [computational fluid dynamics] in the preliminary design environment. page113... paraphrasing: explains how greater performance could be achieved, by rewriting the CFD and CSD apps (computational fluid & structural dynamics) to be more granular, which would permit SORCER to expose subcomponents thereof as services in a parallelized pipeline (finer-grained parallelism rather than the coarse-grained parallelism actually used in the thesis project) page113, quoting: SORCER could offer a computation advantage over the conventional analysis codes... for very large problems SORCER may offer computational advantage over the message-passing interface currently used by the CFD solver to parallelize analysis effort.

MASTERS THESIS x3

Shortname == A.Liu 2010. master's thesis (Kozamo#4) url == http://cdmd.cnki.com.cn/Article/CDMD-10004-2010260506.htm authors == Liu Anjun (刘安军). type of source == Master's Dissertation title == Research on encapsulation method of finite element analysis service in Concurrent Engineering (并行工程中基于SOA的有限元分析服务封装技术研究), publisher == Beijing Jiaotong University (北京交通大学) date == 2010-06-01 pages == ??pgs?? Shortname == W.Wang 2011. master's thesis (Kozamo#5) url == http://cdmd.cnki.com.cn/Article/CDMD-10004-1012355719.htm authors == Wang Wei (王伟). type of source == Master's Dissertation title == Research of testing process modelling and management of weapon equipment systems (武器装备系统测试过程建模与管理系统研究), publisher == Beijing Jiaotong University (北京交通大学) date == 2011-05-26 pages == ??pgs?? Shortname == WrightThesis. Ph.D. Master's thesis (more than one?) from Wright State university overview_url == https://etd.ohiolink.edu/ap/10?222745293673013::NO:10:P10_ETD_SUBID:86171 fulltext_URL ==https://etd.ohiolink.edu/ap:0:0:APPLICATION_PROCESS=DOWNLOAD_ETD_SUB_DOC_ACCNUM:::F1501_ID:wright1316463759,attachment possible COI == Wright State is next door to Wright-Patterson AFB, the USAF facility where AFRL and SORCER are being created (some of the thesis-committee is possibly WP:COI ... student may work there now). Grandhi is a prof at Wright (both theses), Kolonay is dir of AFRL (both theses), Taylor is TBD. To use a PhD thesis as a wikiReliable_Source, the committee which reviews the thesis must be independent... ...and ideally, the published thesis itself must be widely cited. Is this the case at Wright State? Is this the case at U.Dayton? Please advise. Interestingly, although this is Master's rather than PhD, there was a committee of three (not just the one advisor); the Dayton thesis had a cmte of five. author == Karkada Nagesha Aithala title == A Collaborative Computational Framework for Multidisciplinary and Reliability-based Analysis and Optimization Using SORCER pages == 85 (content in 62 pages ... 30 pages specifically about SORCER) date == Finalized 16 Sept 2011 field == Mechanical Engineering (also AeroE & CompE & CompSci) signed off by == Ramana V. Grandhi PhD (thesis director aka advisor), George P. G. Huang PhD (Mech&MaterialsE Chair), Andrew T. Hsu PhD (School of Graduate Studies Dean) final examination cmte == Ramana V. Grandhi PhD (see above), Raymond M. Kolonay PhD (AFRL), Ronald F. Taylor PhD (TBD?)

SUPERGRANTS x3 or x4

Shortname == NIST funding agency == NIST/ATP (USD$21M) title == FIPER project universities == Ohio + Stanford corporations == GE (GE GRC && GE Aviation) + BFGoodrich + Parker Hannifin + Ohio Aerospace Institute + Engineous Software Shortname == USAF Shortname == NSFC 2012. quad-year R&D grant (Kozamo#10) url == ??website?? authors == (potentially... Kozamo et al.) type of source == (classified? TBD? high-speed-railway equipment) title == Research on manufacturing resource integration and coordination management based on SOOA in cloud manufacturing environment publisher == National Science Foundation of China project#51175033 (NSFC) date == 2012/2013/2014/2015 pages == ??pgs?? Shortname == Ulanyovsk(sp) rumours

notability and sourcing, further discussion thereof

Commentary goes here please, use the shortname of the source in the list above (if such is yet specified). 74.192.84.101 (talk) 18:02, 30 December 2013 (UTC)

dealing with terminology/jargon/neologisms

Good advice, copied from the archives. 74.192.84.101 (talk) 18:02, 30 December 2013 (UTC)

• mograms, mogramming - a new term (invented by you), which violates WP:OR. The UML? model is translated down to code, so it's just code with a service manifest. You need to explain that correctly, and get rid of mograms, mogramming. It's not cited anywhere in the firmament, except by yourself, which means it's not acceptable within WP.
  • If that is related to me ("invented by you") then you are making the uneducated statement regarding software language engineering. Please read the chapter on "Languages and Mograms" in the book on "Software Language Engineering: Creating Domain-Specific Languages Using Metamodels"Mwsobol (talk) 15:04, 1 January 2014 (UTC)
    • How many times have people asked about this particular neologism, and asked for a source? Now, since I doubt that anyone is going to :::buy this book for the present, perhaps it is time to furnish us with chapter and verse and quotation to show the provenance of the term? Fiddle Faddle 16:46, 1 January 2014 (UTC)
      • Why we cannot use the term "mogram" in the article as follow:

"mogram (program or model or both) " with the reference to the the independent third party source "Software Language Engineering: Creating Domain-Specific Languages Using Metamodels" by the leading expert in language engineering? Tell me what's wrong with it and please stop creating circular discussions on the same topics.Mwsobol (talk) 21:50, 1 January 2014 (UTC)

• No links to Java, Service (systems architecture),Service-oriented architecture,Service layer and other important links.

• SORCER is the first platform that created front-end service-oriented mogramming (programming or modeling or both) as the key element of its federated service orientation. (Where is the citation for this?)
  • Please show me another one that allows to define service compositions at the front-end. The fact that front-end compositions of service collaborations can be a hybrid of executable programs and executable models (mogram) is the secondary issue. If there is no another such platform with that feature then it's the first one. Are logical implications are invalid in Wikipedia?Mwsobol (talk) 15:14, 1 January 2014 (UTC)
    • That is not the way it works. Citations are required here. If it is the first then something must show that it is the first. Otherwise it may simply be stated to be "a platform" Fiddle Faddle 16:49, 1 January 2014 (UTC)

• Exertions Why? Not programs, applications, services? You need to explain why it was called that. I think it's the same as mogramming, re who is citing it generally, and if it's only you, it will not be acceptable.
  • Semantically different things have names, so please try to understand the semantics of exertions first. A front-end and back-end services have different semantics. A service composition at the server (back-end) is done by a programmer and deployed by a deployer before it is used by the end user. A service composition at the font-end (exertion) is created and executed by the end user at runtime. For interpreted exertions (netlets) no compilation and deployment is needed to run service compositions.Mwsobol (talk) 15:29, 1 January 2014 (UTC)
    • Wikipedia requires that the reader has things exlpained to them. "Trying to understand" is not the way it works. Again, where are the citations? Fiddle Faddle 16:56, 1 January 2014 (UTC)

• SORCER is the first system enabling front-end service-oriented programming with the relevant operating system and dynamic back-end service federations as its virtual processor. That's neat, but don't know if it's true. I think Gigaspaces has a similar mechanism. You will certainly need a citation for this, other wise it's a false assertion, and will need to go.
  • Gigaspaces is just the commercial implementation of JavaSpaces (one of Jini services) to support space computing. It's a space computing middleware based on the JavaSpaces technology. You can write into a Jini space any object, it's generic. In SORCER what is called an exertion space is a JavaSpace service (can be Gigaspaces, we use open source Blitz or Jini JavaSpace) to provide space computing (synchronous federations) for exertions. However with synchronous execution (PUSH vs. PULL in SORCER) the service providers are accessed directly by SOS. You can create an exertion with mix of PUSH/PULL strategies so a part of service providers is accessed directly by SOS and another part reads exertion requests from the exertion space. That is done with the unique SORCR's federated method invocation (FMI). So JavaSpace (Gigaspace) is just one of SOS modules used for FMI.Mwsobol (talk) 15:51, 1 January 2014 (UTC)

• The rest of the unexplained, non linked article content like Providers use discovery/join protocols to publish services in the network and the SOS uses discovery/join protocols to discover registries and lookup proxies in those registries. What providers? What discovery/join protocols, etc etc etc.
  • Terms service providers (services) and discovery/join protocols come from Jini terminology. The SORCER OS implementation uses Jini technology that defines its SOOA architecture. I assume that was stated explicitly in the article.Mwsobol (talk) 15:59, 1 January 2014 (UTC)

Lastly, it's written more as a reference manual, and currently doesn't make sense, lacks context and flow. The whole product seems to be built using Java, so how is it different from you average Java EE application server, like Weblogic or WebSphere. Sorry the criticism is so heavy. I knows your trying your best. scope_creep talk17:31 12 Dec 2013 (UTC)

• I can comment shortly (read at least one paper on SORCER if you want to see differences): SORCER is the federated platform (programming environment (exertions and var-models), service-oriented OS with FMI, and federated processor) it's not a server or a middleware. Exertion-oriented programming and var-oriented modeling in SORCER has nothing to to with Java syntax and semantics they are completely new service languages. The fact SORCER in part is implement with Java has nothing to do with the SORCER architecture and programming/modeling model.Mwsobol (talk) 16:07, 1 January 2014 (UTC)
  • Is this paper on SORCER a WP:RS? If not then it is not relevant. Please at least get to understand the Wikipedia environment. Talking for ever round this subject produces nothing except fluff and clutter. It is presumed that your own work environment has rigour. So does Wikipedia. Our rigour is an insistence on correct reference material. Talking round and round abut this topic without making forward progress reinforces my original beliefs about this. Not every workplace is WP:N. Fiddle Faddle 16:56, 1 January 2014 (UTC)

With the neologisms, may I suggest a special reference group named, perhaps neologism where a correct textual explanation is given , but in layman's language. I am sure I've explained this style of scheme to you before, but I only now see the application in this manner. One may have multiple names reference groups in an article. The only caveat is that the associated {{Reflist}}must come after the final instance on the page. Thus one may also have a group named note, another named Dr Pepper, and so forth. Fiddle Faddle 16:09, 29 December 2013 (UTC)

todo list

Here are the snark-spams at the top of the article today.

1. A major contributor to this article appears to have a close connection with its subject. (December 2013)
2. The topic of this article may not meet Wikipedia's general notability guideline. (December 2013)
3. This article possibly contains original research. (December 2013)
4. This article relies on references to primary sources. (December 2013)
5. This article may contain an excessive amount of intricate detail that may only interest a specific audience. (December 2013)
6. This article may be too technical for most readers to understand. (December 2013)

Pretty long list.  :-)   There are actually just two basic issues. WP:RS to prove wikiNotability, which is being covered above. WP:TONE, too much jargon, and gotta stay neutral. As we go through the paragraphs, we can start to solve tag#6 and tag#5. 74.192.84.101 (talk) 15:20, 29 December 2013 (UTC)

paragraph one

1. SORCER (Service ORiented Computing EnviRonment), sometimes written as SOCER,
2. is a cloud-based computing platform
3. that integrates applications such as engineering systems in large complex IT environments.
4. It is a follow up to the FIPER project
5. which was funded by the National Institute of Standards and Technology Advanced Technology Program.
6. The SORCER program was led by Michael Sobolewski at Texas Tech University[1] through 2009.
7. In 2010, the project spun off into an independent organization with a goal of providing an open source platform.[2]

Rewrite attempt. See WP:Footnotes#Footnotes:_predefined_groups for the 'efn' squiggly-syntax.

1. SORCER
2. is a cloud-based grid computing platform (typically using Java to write network-shell-scripts called exertions which implement location-agnostic web services).
3. SORCER's grid-computing capability is primarily used to speed up computerized analysis of aerospace simulations and traffic noise, as of 2013.
4. SORCER's predecessor was called FIPER, which was software for a GE aircraft-engine-design project
5. funded from 1999-2003 by NIST's ATP.
6. SORCER Labs was founded in November 2002 at TTU;
7. in 2010, SORCER Labs became a spin-off organization, funded primarily by the USAF's AFRL, and the source code was partially opened.
8. SORCER (and FIPER) were invented primarily by Professor Mike Sobolewski; his work from 1994-2002 at GE, then at TTU through 2009, and since then at AFRL, mirrors SORCER's history.
9. Other groups using SORCER include Beijing Jiaotong University in China, Cranfield University in the United Kingdom, andUlyanovsk State University in Russia.

Notes

Anybody else like this version better? 74.192.84.101 (talk) 15:20, 29 December 2013 (UTC)

I find it easier to read, thus it is, by definition, better. It lacks the main requirement of an opening paragraph, though. It does not tell me why this is important. From a journalist's or marketeer's persepctive, and, amusingly, from an encyclopaedia's perspective this is a must have. "Tell me why I should read this material and why it is here." Something like "By deploying SORCER, recorded costs savings/ productivity increases [quantify and verify] have been made." That is at least highly desirable. (oops, failed to sign) Fiddle Faddle 13:44, 31 December 2013 (UTC)

It sounds better and more like Wikipedia. But in my opinion we shoud not compare it to grid computing as:

• SORCER works on higher layers
• SORCER delivers logic for processing - grids doesn't (tools for grids does provide it but not grids itself);
• SORCER delivers language to operate on integrated systems - and grids does not.

Pawelpacewicz (talk) 13:34, 31 December 2013 (UTC)

Well, there *is* a new language from sorcerSoft the company-slash-organization-twins, but "SORCER" is not the language, it is the nsh and the FMI-stuff and the service-configuration-backend... whereas EOL is the language, which is built on Groovy, which is built on JVM-bytecode. But, one can always just use straight Java as the language, which proves that EOL and SORCER *are* distinct, right? EOL is a language that can be used to program exertion-scripts for nsh to execute, and EOL has some special features not included in the base Groovy/Java languages. Anyways, we'll get to a paragraph about languages-used-with-SORCER, further down in our list of paragraphs.

  As for the definition of SORCER as a type of grid-computing-infrastructure, it is a quote straight from DaytonThesis, by Thompson. What is SORCER called in other reliable sources? Sometimes it is referred to as a meta-operating-system, but that's not how it is often used currently. It is a capability, which might be used in the classified literature, but not in the sources we have at present, right? That is what we have to stick to. What is SORCER called in the 2007 lit-review from U.Cranfield, for instance?

  As for Tim's question, see fragment#3 ("primarily used to" is my codephrase meaning "primarily Notable for being used to") that same DaytonThesis also gives us a good quote about the purpose (or at least *one* purpose) for which SORCER is notable... using the extra speed that SORCER's spread-the-load-across-the-grid-related-features offer, aircraft-designers like Thompson can perform full-fledged non-linear analysis of aircraft-designs in simulations, rather than the traditional linear-analysis. When the DaytonThesis simulated the aircraft-wing-design at mach 0.50 there was no difference in the optimality of the design; linear was just as good as non-linear. However, when the same pair of design-methodologies was applied to the same aircraft-wing-design at mach 0.89 ... which is getting close enough to the sound barrier that weird things come into play ... the SORCER-powered non-linear analysis-methodology created a *much* more-optimal automated wing-design, using the same amount of time & personnel & whatnot. So at least from Thompson's DaytonThesis perspective, SORCER is purely a grid-computing-infrastructure-platform, which permits spreading the computations across a grid of machines, and thus gives better wing-designs without the need to fabricate physical models and test them in the wind-tunnel. What do our other WP:RS say, is the chief advantage of using SORCER, as opposed to other software-options? What is the big advantage of SORCER for Nan Li, and the traffic-noise-mapping work? HTH. 74.192.84.101 (talk) 23:06, 31 December 2013 (UTC)

paragraph two

Current.

1. Overview. SORCER is a computing platform that allows the end user
2. to program dynamic front-end compound services, called exertions,
3. bound at runtime by the SORCER OS (SOS)
4. to federations of service providers as new back-end dynamic services.
5. The SOS utilizes the service object-orient architecture (SOOA) and a federated method invocation.
6. The front-end services created by the end users
7. are service collaborations of users' applications, tools, and utilities with their data and corresponding control strategies.
8. The end users in understandable domain specific languages (DSL)
9. define only their service-oriented process expressions
10. and the SOS makes that process expressions actualized by the corresponding dynamic service federations in the network.

Rewrite.

1. Basic Explanation Of Typical Use. SORCER provides a new command-line shell nsh, running on top of Linux or Cygwin.
2. Shell scripts for nsh create web services which run on the local PC. These script-generated services can call each other.
3. The SORCER-runtime underneath nsh connects the scripted-services together dynamically,
4. both locally to other scripted-services on the PC, but also (depending on config-files) remotely across the LAN to back-end scripted-services.
5. Inside the SORCER environment, every executing nsh script is a service, which can be on the local PC, or across the LAN. Local scripted-services can act as wrappers around back-end scripted-services.
6. Scripted-services on the local PC
7. can also provide a service-oriented wrapper which controls existing command-line applications (and their associated data-files).
8. Creating these scripted-services, and configuring them, is a job for programmers and system administrators, respectively. Once complete, such frameworks implemented on top of the SORCER-runtime are usually controlled by the enduser (often a wing-designer or turbine-engineer or other aerospace-industry personnel) using application-specific DSLs.
9. Engineer-endusers can write straightforward process-definition-expressions,
10. and SORCER transparently spreads the process-workload out across the machines on the LAN.

Notes

Boy, howdy *this* is a heavy rewrite. My goal here is to explain the DEAD SIMPLE BASIC use case, not all the special/advanced/rare features, we can cover those further down. I've also tried to get rid of all the new words, and use existing concepts. I'm sure I've made some mistakes, please give me your corrections.  :-)   Thanks. 74.192.84.101 (talk) 23:55, 31 December 2013 (UTC)

how many source-code repos are there?

Questions about the number of forks/repos of the SORCER codebase (plus ancillary codebases surrounding it), which groups used what codebases (historically and recently), which groups contributed *code* as opposed to money/endusers/similar.

1. SORCER is about grids of distributed algorithms, for concurrent-engineering design-disciplines
2. SORCER is a huge computing environment, only a fraction of the results related to SORCER have been published
3. This is partly because some of the apps are classified (military), and partly because some of the apps are proprietary (corporate trade-secrets)
4. Still, there is a conceptual framework, and a reference architecture, which is what has been covered in the wikipedia article (to date).
5. Mwsobol works full-time for AFRL/WPAFB (which maintains one? two? more? repos of the SORCER codebase... plus various USAF-proprietary libs/apps/etc).
6. Mwsobol occasionally teachs SORCER, including in Russia (how many places? Ulyanovsk State University), and the Russians maintain their own SORCER repo (just one?)
7. Mwsobol occasionally teachs SORCER, including in China (how many places? Beijing Jiaotong University), and the Chinese maintain their own SORCER repo (just one?)
8. Cranfield University in the United Kingdom ... do they use SORCER, nowadays? When did they use it? What about UK military or British Airways or similar?
9. Mwsobol occasionally does consulting work, and helps interested parties to get started with SORCER
10. One such interested party was SorcerSoft.com, located in Poland, who got trained by Mwsobol during 2013
11. SorcerSoft.com is now just starting to develop commercial GUI-tools for SORCER
12. SorcerSoft.com's proprietary work is based on a private repo, an internal fork of the open-source codebase, is not available to the public,
13. SorcerSoft.com's public work is based on the version developed at TTU (aka SORCER Labs), which is currently open-source
14. Mwsobol occasionally teachs SORCER, including (in January 2014) in Poland at PJIIT, which is using an open-source version (different from SorcerSoft.com's? Different from SorcerSoft.org's repo, if any?)
15. SorcerSoft.org ... which is not officially connected to SorcerSoft.com ... is the current home of Mwsobol's SORCER Lab (still at TTU? or now at AFRL? or maybe now at PJIIT? or maybe just spun-off to Mwsobol's private webhost? confusion!)
16. The historical FIPER codebase, which was used at GE from the late 1990s (NIST-ATP-funded from 1999-2003 but Mwsobol first hired at GE GRC in 1996) for turbine-design.
17. One of the small companies involved with FIPER was later acquired by Dassault, the EU corporation. Do they have an internal version of FIPER, or of SORCER?
18. Is FIPER still being used by GE/Dassault/Stanford/OhioUniversities/others? If so, is the codebase (or are the codebases) available publically?
19. Has GE used SORCER?
20. Has Dassault used SORCER?
21. Has Stanford used SORCER?
22. Have OhioUniversities used SORCER? (yes, U.Dayton PhD + WrightStateU MEng) What about Ohio Aerospace Institute? What about BFGoodrich?
23. During the transition from FIPER to SOCER-and-then-SORCER,
24. some external links are redundant, already listed at http://sorcersoft.com
25. one particular repo was developed at TTU, and is now maintained by sorcerSoft.com
26. Github contributors page , https://github.com/sorcersoft/sorcer/graphs/contributors
27. This particular github group is the maintainers of the version developed at SORCER Lab
28. There are many maintainers of multiple repositories, not just that one
29. the SORCER platform is implemented in many places.
30. The MSTC/AFRL/WPAFB/USAF is using and developing SORCER to ... [3]
31. but, in the 2012 DaytonThesis, Kolonay (director of MSTC) was specifically mentioned as implementing three or four major class-libraries(?)
32. It is not fair to those who really contributed and are ignored.
33. Unless all development sites are listed it is just misleading information

Note that wikipedia tends to just give one main "official link" ... is that SorcerSoft.org , nowadays ... right? As for the main subject of this talkpage section, anybody want to try and give me the overview of what groups were responsible for what code, when? Please start historically, so we can give a summary of the history of the project's code, in the article. Danke, it's appreciated. 74.192.84.101 (talk) 01:48, 1 January 2014 (UTC)

technical question, about exertions versus federations

"An exertion as the service classifier is used in SORCER and so all federations such that the exertion can be bound to at runtime are instances of it." --Beavercreekful

1. I do not understand the above sentence.
2. I'm familiar theoretically with Self.
3. I'm familiar with Javascript-style prototyping where there is no classdef; objects are just modified-clones of previous objects.
4. An exertion is an nsh-shell-script, written in EOL or in Java.
5. A running/executing exertion is a service (kinda-like a web service but-not-exactly-like).
6. A federation is a compound-service (a wrapper around a set of services... and the wrapper itself can be treated as a service).
7. If I have a file called myExertion.sorcer stored on my local PC, that file (or the associated config-file maybe) will give the pointers (names? network-locations? URLs?) to the federations it depends upon.
8. When I use nsh to execute-slash-run myExertion.sorcer , the bindings of the actual underlying dependencies (local federations/services or remote federations/services or local Linux apps/datafiles) are bound-at-runtime.

What does the word "it" at the end of the confusing sentence, really mean? "...so all federations such that the exertion can be bound to at runtime are instances of it."

1. If an exertion can be bound-at-runtime to a federation, those federations are instances/subclasses/interfaceImplementations of that exertion?
2. Or, if an exertion can be bound-at-runtime to a federation, then that exertion must be an instance/subclass/interfaceImplementation of those federations?
3. Or, something else entirely?  :-)

Thanks. 74.192.84.101 (talk) 01:48, 1 January 2014 (UTC)

---

• Ad. 1) I do not understand the above sentence.

Let's start with the UML definition of "classifier" with "exertions" added for my service-oriented class.

classifier
A collection of instances that have something in common. A classifier can have features that characterize its instances. Classifiers include interfaces, classes, datatypes, components, services (exertions).

If object a is an instance of a class A, A is the classifier of a.

And now it's important to understand the difference with interface types. An object a of class A that implements interface B is instance of interface B. In other words, the interface B is a classifier of a. By the interface type we can classify objects independently of the object implementation (class). SORCER uses interface types in exertion signatures to bind to network objects that implement the signature interfaces.

If an exertion with a service signature including a service type B (practically Java interface B in SORCER) matches the interface of a network object (service provider) that implements the interface B then this service provider is the instance of this exertion. Now if an exertions includes 5 signatures with 5 services types (Java interfaces) then five service providers in the network that implement these interfaces create the service federation for this exertion. This federation is an instance of the exertion. In that case we say that the exertion binds to the federation and matching (binding) is done by the SORCER OS. Take into account that there in no any static references to service providers in exertion signatures. Service providers are replicated for reliability and load balancing. So, when you run the same exertion again you can get usually a different federation (a collection of matching providers based on the interface types only). Obviously another attributes can be used in SORCER as well if required but the basic concept of binding is based on service types. That federation concept does not exist in any other service-oriented platform. By the way provisioning in SORCER is based on the service type concept as well. For a set of signature the SORCER OS on-demand can create a corresponding federation or multiple federations (instances) of a given exertion.

• Ad. 4) An exertion is an nsh-shell-script, written in EOL or in Java

see "How to explain SORCER conceptualizations?" An exertion is a front-end specification of a service federation and its collaborative behavior. A textual form of interpreted exertions are called "netlets", exertions as instances of Exertion interface (Created with SORCER API) are called "exertlets", and exertions created with GUIs are called "service diagrams". Thus, three forms of exertion languages exist: EOL for the network shel (nsh), Java API (no need for the shell), and a visual exertion programming with a GUI that creates a corresponding exertlet or netlet or both if the round trip editing is supported between service diagrams and netlets.

• Ad. 5) A running/executing exertion is a service (kinda-like a web service but-not-exactly-like).

see "How to explain SORCER conceptualizations?" below. Oh, No!!!
Web services are back-end services (deployed at the app servers) and the front-end client can invoke only one service per invocation with a static server end-point (URL). What the invoked service do later is another story. An exertion is the from-end service that invokes a collaborative federation in the network (as explained above). There is no app servers, no static end-points, service providers are small footprint independent services that can come and go as needed in the global networkMwsobol (talk) 04:17, 1 January 2014 (UTC)

How to explain SORCER conceptualizations?

I was alarmed about the confusing SORCER conceptualizations above, so let's hope the clarification by analogy to a common computing platform will help to understand unique features of the SORCER platform. By the way, conceptually it does not have anything common with grid computing or web services. The fact you can do grid computing or run web services in SORCER does not mean it was designed directly to do so.

Let's consider a common computing platform (or runtime: programming environment, operating system, processor). For example, a UNIX platform (programming environment - Unix shell programming, a UNIX operating system, and a native or virtual processor such that the operating system can execute programs (executable codes) compiled for this platform. So, each platform has a front-end (shell or command processor), a back-end (executable codes) and in the middle (an operating system). A common platform is used predominantly to execute a single command that runs the executable code in the shell locally. Advanced users can write a shel script (in a file or at the command line) to create a pipeline of locally executing programs (pipes are local). The fact that an executable code can provide networking internally using for example sockets or any application protocol (FTP, SMPT, HTTP) is the feature of a program (application) not the platform. The common platform runs executable codes locally.

Now let's imagine that a platform at the back-end instead of local executable codes has applications, tools, utilities that can be provisioned on-demand in the network at runtime (they constitute a network processor of the platform). Now the shell script can define any collaboration (service pipeline (batch), workflow, block for branching and looping) of back-end services that can be found or provisioned in the network at runtime. These scripts define front-end services (programs) as collaborations of back-end services. The shell now executes front-end services and the operating system can run any collaboration of back-end services. These collaborations of backend services for each front-end service are called service federations. The paradigm is called federated service-oriented computing since a shel invokes a federation of service providers. To do so the operating system needs a new invocation method, instead of invoking a single program or pipeline of programs locally invokes a federation of back-end services in the network for each front-end service. Please match the above description to the chart of the SORCER OS in the article. Note that all other service platforms provide service collaborations at the back-end (called an applications server) only.

The above federated platform defines: a front-end service (exertion), a singleton back-end service (a service provider), and a back-end collaboration of services (federation) specified by a front-end service. When developing the FIPER architecture I have introduced the terms given in parenthesis to emphasize three types of completely different service semantics in federating computing. If you prefer, you can use longer names in the article: front-end service, back-end service, and a collaborative service at the backed defined by the front-end service. By the way a front-end service is a collaborative service as well but at the front-end as the virtual service (realized at the back-end by its federation). Also, calling a front-end service as a "service script" like UNIX script is confusing due to completely different semantics of the network shell, operating system, and the processor as a collection of dynamic service federations. SORCER front-end scripts are called "netlets". An exertion is a more generic concept for a front-end specification of a back-end federation. Formally, an exertion is a metamodel with models in the form of "netlet" (textual), "exertlet" (any object that implements Exertion interface, created with API), and "service diagram" (visual programming - interactive GUI). Therefore a netlet, exertlet, and service diagram are exertions. Three different forms of front-end services have to be called differently and three types of services (exertions, service providers, and federations) in federated computing have to be called differently.

The SORCER lab completed research in all aspects of federated computing as described above. Other organizations including AFRL develop federated service applications using the TTU SORCER platform. The research papers by AFRL are focused on how to design air vehicles using SORCER but not how to design SORCER. I assume this article is about the TTU platform architected, designed, and implemented at the SORCER lab as the extension of FIPER. The currently offered open source version maintained by SORCERsoft.com is the implementation completed at the SORCER lab. Thus, please drop any unjustified relationships of the TTU SORCER technology to other organizations that can be used as the secondary sources regarding how SORCER is used. They spent own money on the projects related directly to they business objectives. When they say we develop SORCER it means that develop tools to make SORCER easier to use with their applications. SORCERsoft.com is not developing the SORCER technology as well, the company is developing tools for interactive exertion-programming and var-oriented modeling. They do what Apple has done with BSD UNIX for Mac OSX. There is no any research paper on the SORCER technology from other places than the SORCER lab (sorcersoft.org) since that core technology is open to any organization with no need to redevelop it. I still assume the article should be about the core SORCER technology that originated from NIST FIPER and TTU SORCER.Mwsobol (talk) 02:59, 1 January 2014 (UTC)

This discussion has been circular since the start

Despite enormous efforts by experienced Wikipedia editors to find WP:RS, to show WP:N and to ensure WP:V, the discussion has proved to be an endless round of:

1. Show me that this is notable
2. It is notable because it is notable
3. Give me the reference
4. The reference is somewhere in this list of probably non WP:RS material
5. If I find it, show me that this source is WP:RS
6. It must be reliable because I say it is reliable
7. Return to number 1

This has been going on for a couple of days short of two months. This alone shows me that the topic is not notable. Were it to be notable this would have been proven a long time ago. Doubtless people use this environment. Good. Maybe it will become notable one day. Today it is not.

Yes, we have WP:NODEADLINE, but there is a threshold of notability all articles must pass. We cannot faff around for ever with those who work in SORCER telling us for ever that their project is notable without clarity of answers to questions. It is time for clear answers. If the SORCER folk can show that this is WP:N by proving the bona fides of their sources to be WP:RS, now is the time. Fiddle Faddle 17:18, 1 January 2014 (UTC)

• I was informed about new material, clarifications, references to UK, Chinese, and Russian sources provided by a few contributors here. I think they are valid. I have provided myself additional clarification trying to help to get it consistent with the state of the art in service-oriented computing. It seems to me you have accepted sources from the Cranfield University as OK regarding notability. If someone contradicts his own previous statements, is continuously blaming others for problems, offending collaborating editors, and not providing reasonable feedback based on pretty much flexible Wikipedia rules then that person causes unnecessary circles.Mwsobol (talk) 22:12, 1 January 2014 (UTC)
  • I am not sure what type of feedback you are looking for other than what has been said many times, there needs to be evidence of third party reliable sources discussing the subject in order for there to be a stand alone article on the topic. Where are the third party reliable sources? -- TRPoD aka The Red Pen of Doom 22:18, 1 January 2014 (UTC)
    • You can provide a feedback for a healthy collaborations as [74.192.84.101] does or for a destructive collaboration. I am not going to participate in the latter case.Mwsobol (talk) 22:40, 1 January 2014 (UTC)

support-- TRPoD aka The Red Pen of Doom 17:36, 1 January 2014 (UTC)