Download the Author Guidelines As A

Total Page:16

File Type:pdf, Size:1020Kb

Download the Author Guidelines As A As of October 18, 2019, all manuscripts are now submitted through the Research Exchange (REX) Submission Portal. For submissions started prior to October 18, 2019, including revised submissions or invited submissions, please visit ScholarOne to manage your submission. If you have any questions about the submission portals, please email [email protected] or [email protected]. Editorial Process Overview Journal Aim and Scope The Journal of Neuroscience Research (JNR) publishes novel research results that will advance our understanding of the development, function and pathophysiology of the nervous system, using molecular, cellular, systems, and translational approaches. The journal focuses on uncovering the intricacies of brain structure and function. Research published in JNR covers all species from invertebrates to humans, and the reports inform the readers about the function and organization of the nervous system, with emphasis on how disease modifies the function and organization. The acceptance criteria for all papers are the quality and originality of the research, and its significance to the journal’s readership. Except where otherwise stated, manuscripts are single-blind peer reviewed. Papers will only be sent to review if the Editor-in-Chief determines that the paper meets the appropriate quality and relevance requirements. The Journal does not consider Case Reports or studies using herbal remedies/natural compounds derived from plants as these are difficult to reproduce. In addition, studies involving immortalized cell lines that are not accompanied by primary cultures, slice or in vivo work will not be considered as it is difficult or impossible to extrapolate results to normal neuronal populations. Peer Review Peer review by two to three external reviewers will be made after editorial prescreening. Submitted manuscripts are assigned to the Editor-in-Chief for prescreening, and then distributed among the Handling Editors (either Executive Editors or Associate Editors) based on expertise. All submissions to JNR are subject to stringent evaluation first by the Editor-in-Chief. Submissions are assessed to ensure they fall within the scope of the journal and meet its requirements for transparency, scientific rigor and novelty. If deemed suitable for peer review, the Handling Editor will send the manuscript to external reviewers with expertise in the topic and methods. This manuscript triage is essential to avoid undue burden on the peer review system. Referee exclusions by the authors will be honored as long as the total number of excluded referees are reasonable (i.e., total number of exclusions reflecting the size of expert pool for a given topic). Referee suggestions from the authors may be considered. JNR operates using a transparent review process. We make peer review documentation (referees' de-anonymized reports, authors' responses and editors' comments) available alongside the published articles. Unblinding will occur only after a manuscript is accepted for publication; reviews will remain anonymous until this point (reviewers' names will not be disclosed for manuscripts that are ultimately rejected). We believe that this will result in a more transparent and accountable process. To highlight the skill and importance of reviewing, Wiley has partnered with Publons to give reviewers formal recognition for their contribution. In this partnership, reviewers can elect to have their transparent reviews automatically added to their reviewer profile on Publons. This is an optional service to reviewers. Click here for additional details. Peer reviewers are selected for their technical expertise and overview of their specific fields of research interest. If you wish to recruit a colleague to review with you for reasons of mentorship or complementary technical knowledge, please contact the editor before sharing access to the manuscript. Undeclared co-reviewing is incompatible with transparent peer review and prevents us from giving credit to your colleague’s important contribution to open research. Appeals Authors may appeal the journal’s rejection decisions. While there is no limit to the number of appeals, the Journal editors will do their utmost to minimize the submitted paper being re-reviewed multiple times unless substantive changes are made to the submitted manuscripts. Because the reviewer’s time and effort cannot be taken for granted and editorial resources are finite, the Journal will deny appeals on post-review rejection without formal re-review unless the editors view the revision to be convincing and substantive. 1 Manuscript Categories Original Research Research articles are full-length reports of quality current research within any area covered by the journal. Such contributions report new research findings or conceptual analyses that make a significant contribution to the scientific knowledge. There are no strict word or figure limits on this type of article. Authors should present the material clearly and completely, in the most concise and direct form possible. The introduction should be brief, and the discussion should be restricted to issues directly relevant to the results. The authors should provide sufficiently detailed information in the Materials and Methods section for the observations to be critically evaluated and, if necessary, repeated. Original research articles will be peer reviewed and every attempt will be made to bring the acceptable research article to a rapid publication. Editors will evaluate the submission and compare against the existing literature to determine what was shown before and what does the new submission add. Technical Report While JNR does not publish papers of a purely technical or methodological nature (so-called “methods papers”), certain research articles may include, as a major component of the work, a novel technological development not previously reported, and presented as a crucial part of the methods and results. Such papers will follow the usual layout of a standard research paper (see above) with an extended Materials and Methods that provides all of the necessary details of the novel technology, including description of algorithms and validation experiments, to make it accessible to the readership. Such papers will be marked as Technical Report papers to reflect their particular contents. Note that simple improvements on established methodologies do not befit this format. Registered Reports Registered Reports are designed to eliminate publication bias and incentivize best scientific practice. Registered Reports are a form of empirical article in which the methods and proposed analyses are pre-registered and reviewed prior to research being conducted. This format is designed to minimize bias, while also allowing complete flexibility to conduct exploratory (unregistered) analyses and report serendipitous findings. The cornerstone of the Registered Reports format is that authors submit as a Stage 1 manuscript an introduction, complete and transparent methods and the results of any pilot experiments (where applicable) that motivate the research proposal, written in the future tense. These proposals will include a description of the key research question and background literature, hypotheses, experimental design and procedures, analysis pipeline, a statistical power analysis and full description of planned comparisons. Submissions, which are reviewed by editors, peer reviewers, and our statistical editor, meeting the rigorous and transparent requirements for conducting the research proposed, are offered an in-principle acceptance, meaning that the journal guarantees publication if the authors conduct the experiment in accordance with their approved protocol. Following data collection, authors prepare and resubmit a Stage 2 manuscript that includes the introduction and methods from the original submission plus their obtained results and discussion. The manuscript will undergo full review; referees will consider whether the data test the authors’ proposed hypotheses by satisfying the approved outcome-neutral conditions, will ensure authors adhered precisely to the registered experimental procedures, and will review any unregistered post hoc analyses added by the authors to confirm they are justified, methodologically sound and informative. At this stage, authors must also share their data (see also Wiley’s Data Sharing and Citation Policy) and analysis scripts on a public and freely accessible archive. Additional details, including template reviewer and author guidelines can be found by clicking the link to the Open Science Framework from the Center for Open Science (see also Chambers et al. 2014) or in our Registered Reports Author Guidelines. Review and Mini-Review JNR publishes two types of Review articles: full-length reviews and mini-reviews. Focused, critical reviews of a wide range of forefront areas of neuroscience will be considered for publication. The preferred format for Reviews is that of a focused, topical paper that helps specialists remain up to date with the information published in their subject while being informative for the non-specialist. As such, reviews should focus on recent developments in a given field, describe current trends and as applicable methodologies, and provide a critical opinion intended for broad readership. Authors of reviews should avoid concentrating solely or preferentially on their own work. There are no limits to the number of pages or figures for a review, but mini-reviews must be less than 5,000 words and
Recommended publications
  • TMS Xdata Documentation
    Overview TMS XData is a Delphi framework that allows you to create HTTP/HTTPS servers that expose data through REST/JSON. It is highly integrated into TMS Aurelius in a way that creating XData services based on applications with existing Aurelius mappings are just a matter of a few lines of code. XData defines URL conventions for adressing resources, and it specifies the JSON format of message payloads. It is heavily based on the OData standard. Such conventions, with the benefit of existing Aurelius mapping, allow building a full REST/JSON server with minimum writing of code. TMS XData uses TMS Sparkle as its core communication library. TMS XData product page: https://www.tmssoftware.com/site/xdata.asp TMS Software site: https://www.tmssoftware.com TMS XData is a full-featured Delphi framework that allows you to create REST/JSON servers, using server-side actions named service operations, and optionally exposing TMS Aurelius entities through REST endpoints. Consider that you have an Aurelius class mapped as follows: [Entity, Automapping] TCustomer = class strict private FId: integer; FName: string; FTitle: string; FBirthday: TDateTime; FCountry: TCountry; public property Id: Integer read FId write FId; property Name: string read FName write FName; property Title: string read FTitle write FTitle; property Birthday: TDateTime read FDateTime write FDateTime; property Country: TCountry read FCountry write FCountry; end; With a few lines of code you can create an XData server to expose these objects. You can retrieve an existing TCustomer
    [Show full text]
  • TR-069 CPE WAN Management Protocol V1.1
    TECHNICAL REPORT TR-069 CPE WAN Management Protocol v1.1 Version: Issue 1 Amendment 2 Version Date: December 2007 © 2007 The Broadband Forum. All rights reserved. CPE WAN Management Protocol v1.1 TR-069 Issue 1 Amendment 2 Notice The Broadband Forum is a non-profit corporation organized to create guidelines for broadband network system development and deployment. This Technical Report has been approved by members of the Forum. This document is not binding on the Broadband Forum, any of its members, or any developer or service provider. This document is subject to change, but only with approval of members of the Forum. This document is provided "as is," with all faults. Any person holding a copyright in this document, or any portion thereof, disclaims to the fullest extent permitted by law any representation or warranty, express or implied, including, but not limited to, (a) any warranty of merchantability, fitness for a particular purpose, non-infringement, or title; (b) any warranty that the contents of the document are suitable for any purpose, even if that purpose is known to the copyright holder; (c) any warranty that the implementation of the contents of the documentation will not infringe any third party patents, copyrights, trademarks or other rights. This publication may incorporate intellectual property. The Broadband Forum encourages but does not require declaration of such intellectual property. For a list of declarations made by Broadband Forum member companies, please see www.broadband-forum.org. December 2007 © The Broadband
    [Show full text]
  • Do Neuroscience Journals Accept Replications? a Survey of Literature
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by HKU Scholars Hub Do Neuroscience Journals Accept Replications? A Survey of Title Literature Author(s) Yeung, WKA Citation Frontiers in Human Neuroscience, 2017, v. 11, p. 468 Issued Date 2017 URL http://hdl.handle.net/10722/247231 This Document is Protected by copyright and was first published by Frontiers. All rights reserved. It is reproduced with Rights permission.; This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License. ORIGINAL RESEARCH published: 20 September 2017 doi: 10.3389/fnhum.2017.00468 Do Neuroscience Journals Accept Replications? A Survey of Literature Andy W. K. Yeung* Oral and Maxillofacial Radiology, Applied Oral Sciences, Faculty of Dentistry, The University of Hong Kong, Hong Kong, Hong Kong Background: Recent reports in neuroscience, especially those concerning brain-injury and neuroimaging, have revealed low reproducibility of results within the field and urged for more replication studies. However, it is unclear if the neuroscience journals welcome or discourage the submission of reports on replication studies. Therefore, the current study assessed the explicit position of neuroscience journals on replications. Methods: A list of active neuroscience journals publishing in English was compiled from Scopus database. These journal websites were accessed to read their aims and scope and instructions to authors, and to assess if they: (1) explicitly stated that they accept replications; (2) did not state their position on replications; (3) implicitly discouraged replications by emphasizing on the novelty of the manuscripts; or (4) explicitly stated that they reject replications.
    [Show full text]
  • Central Nervous System Manifestations in COVID‐19 Patients
    Received: 30 July 2020 | Revised: 23 November 2020 | Accepted: 20 December 2020 DOI: 10.1002/brb3.2025 REVIEW Central nervous system manifestations in COVID-19 patients: A systematic review and meta-analysis Shahrzad Nazari1 | Amirhossein Azari Jafari2 | Seyyedmohammadsadeq Mirmoeeni2 | Saeid Sadeghian3 | Mohammad Eghbal Heidari4 | Siavash Sadeghian5 | Farhad Assarzadegan6 | Seyed Mahmoud Puormand7 | Hamid Ebadi8 | Davood Fathi9,10 | Sahar Dalvand11 1Department of Neuroscience and Addiction Studies, School of Advanced Technologies in Medicine, Tehran University of Medical Sciences, Tehran, Iran 2Student Research Committee, School of Medicine, Shahroud University of Medical Sciences, Shahroud, Iran 3Department of Paediatric Neurology, Golestan Medical, Educational, and Research Centre, Ahvaz Jundishapur University of Medical Sciences, Ahvaz, Iran 4Students Scientific Research Center, Tehran University Medical Science, Tehran, Iran 5Ahvaz Jundishapur University of Medical Sciences, Ahvaz, Iran 6Department of Neurology, Imam Hossein Hospital, Shahid Beheshti University of Medical Sciences, Tehran, Iran 7Imam Hossein Hospital, Shahid Beheshti University of Medical Sciences, Tehran, Iran 8Department of Clinical Neurosciences, University of Calgary, Calgary, AB, Canada 9Brain and Spinal Cord Injury Research Center, Neuroscience Institute, Tehran University of Medical Sciences, Tehran, Iran 10Department of Neurology, Shariati Hospital, Tehran University of Medical Sciences, Tehran, Iran 11Functional Neurosurgery Research Center, Shohada Tajrish Comprehensive Neurosurgical Center of Excellence, Shahid Beheshti University of Medical Sciences, Tehran, Iran Correspondence Sahar Dalvand, Functional Neurosurgery Abstract Research Center, Shohada Tajrish Background: At the end of December 2019, a novel respiratory infection, initially Comprehensive Neurosurgical Center of Excellence, Shahid Beheshti University of reported in China, known as COVID-19 initially reported in China, and later known Medical Sciences, Tehran, Iran. as COVID-19, led to a global pandemic.
    [Show full text]
  • Version Indication & Negotiation
    SIF Infrastructure Specification 3.3: Version Indication & Negotiation www.A4L.org Version 3.3, May 2019 SIF Infrastructure Specification 3.3: Version Indication & Negotiation Version 3.3, May 2019 Preface ...................................................................................................................................... 4 Disclaimer ................................................................................................................................. 4 Permission and Copyright ....................................................................................................... 5 Document Conventions ........................................................................................................... 5 Terms and Abbreviations .......................................................................................................... 5 Notations ..................................................................................................................................... 6 1. Context ............................................................................................................................... 7 2. Problem Statement ........................................................................................................... 8 3. Method ................................................................................................................................ 9 3.1 Schema Identification .......................................................................................................
    [Show full text]
  • HTTP Working Group M. Nottingham Internet-Draft Akamai Intended Status: Standards Track P
    HTTP Working Group M. Nottingham Internet-Draft Akamai Intended status: Standards Track P. McManus Expires: September 9, 2016 Mozilla J. Reschke greenbytes March 8, 2016 HTTP Alternative Services draft-ietf-httpbis-alt-svc-14 Abstract This document specifies "Alternative Services" for HTTP, which allow an origin’s resources to be authoritatively available at a separate network location, possibly accessed with a different protocol configuration. Editorial Note (To be removed by RFC Editor) Discussion of this draft takes place on the HTTPBIS working group mailing list ([email protected]), which is archived at <https://lists.w3.org/Archives/Public/ietf-http-wg/>. Working Group information can be found at <http://httpwg.github.io/>; source code and issues list for this draft can be found at <https://github.com/httpwg/http-extensions>. The changes in this draft are summarized in Appendix A. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on September 9, 2016. Nottingham, et al. Expires September 9, 2016 [Page 1] Internet-Draft HTTP Alternative Services March 2016 Copyright Notice Copyright (c) 2016 IETF Trust and the persons identified as the document authors.
    [Show full text]
  • 3 Protocol Mappings
    Standards Track Work Product Specification for Transfer of OpenC2 Messages via HTTPS Version 1.0 Committee Specification 01 11 July 2019 This version: https://docs.oasis-open.org/openc2/open-impl-https/v1.0/cs01/open-impl-https-v1.0-cs01.md (Authoritative) https://docs.oasis-open.org/openc2/open-impl-https/v1.0/cs01/open-impl-https-v1.0-cs01.html https://docs.oasis-open.org/openc2/open-impl-https/v1.0/cs01/open-impl-https-v1.0-cs01.pdf Previous version: https://docs.oasis-open.org/openc2/open-impl-https/v1.0/csprd02/open-impl-https-v1.0- csprd02.md (Authoritative) https://docs.oasis-open.org/openc2/open-impl-https/v1.0/csprd02/open-impl-https-v1.0- csprd02.html https://docs.oasis-open.org/openc2/open-impl-https/v1.0/csprd02/open-impl-https-v1.0- csprd02.pdf Latest version: https://docs.oasis-open.org/openc2/open-impl-https/v1.0/open-impl-https-v1.0.md (Authoritative) https://docs.oasis-open.org/openc2/open-impl-https/v1.0/open-impl-https-v1.0.html https://docs.oasis-open.org/openc2/open-impl-https/v1.0/open-impl-https-v1.0.pdf Technical Committee: OASIS Open Command and Control (OpenC2) TC Chairs: Joe Brule ([email protected]), National Security Agency Duncan Sparrell ([email protected]), sFractal Consulting LLC Editor: open-impl-https-v1.0-cs01 Copyright © OASIS Open 2019. All Rights Reserved. 11 July 2019 - Page 1 of 29 Standards Track Work Product David Lemire ([email protected]), G2, Inc. Related work: This specification is related to: Open Command and Control (OpenC2) Language Specification Version 1.0.
    [Show full text]
  • The OWASP Foundation Tweaking to Get Away from Slowdos
    Tweaking to get away from SlowDOS Tweaking to get away from SlowDOS Sergey Shekyan, Senior Software Engineer June 2nd, 2012 OWASP Kansas City June 21st, 2012 Copyright 2012 © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the OWASP License. The OWASP Foundation http://www.owasp.org Sunday, June 24, 12 1 Denial of Service Attacks OWASP 2 Sunday, June 24, 12 2 Types of attack There is a variety of forms aiming at a variety of services: Traffic consuming attacks (DNS, firewall, router, load balancer, OS, etc.) Application Layer attacks (web server, media server, mail server) OWASP 3 Sunday, June 24, 12 3 What is low-bandwidth attack? Slowloris GET Flood 400 300 Mbps/sec 200 100 0 0 10 20 30 40 Seconds OWASP 4 Sunday, June 24, 12 4 Network Layer attacks OWASP 5 Sunday, June 24, 12 5 Application Layer attacks OWASP 6 Sunday, June 24, 12 6 DDoS economics DDoS attacks are affordable (from $5/hour) DDoS attack is a great way to promote your start-up (attacks on Russian travel agencies are 5 times as frequent in high season) Longest attack detected by Kaspersky DDos Prevention System in the second half of 2011 targeted a travel agency website and lasted 80 days 19 hours 13 minutes 05 seconds Akamai reports DDoS attack incidents soar 2,000 percent in the past three years OWASP 7 Sunday, June 24, 12 7 Screenshot of a “company” offering DDoS services OWASP 8 Sunday, June 24, 12 8 Marketing HTTP Flood, UDP flood, SYN flood On-demand modules (for example, e-mail flooder) Multiple targets Pay from any ATM Money back guarantee OWASP 9 Sunday, June 24, 12 9 Application Layer DoS attacks Slow HTTP headers attack (a.k.a.
    [Show full text]
  • Meter Reading Web Services Data Exchange Specification
    Meter Reading Web Services Data Exchange Specification Version 2.0 2017 ISO New England Inc. ISO-NE PUBLIC Change Summary Revision Date Comments Version 1.0 June 2016 Initial release Version 2.0 November 2017 Changes for PFP/PRD Version 3.0 July 2020 Changes for FRM/Upgrade ISO-NE PUBLIC About this document The Meter Reading Web Services Data Exchange Specification document describes the REST messages and the Authentication and Authorization process used to exchange meter reading data between a Meter Reader and the Meter Reading application through web services. It also describes the upload and download files used to exchange meter reading data through a Meter Reader’s web browser and the “Submit Meter Reading” user interface provided by the SMD Site for ISO Applications. The user interface upload/download files and the web service REST messages share the same data format. This document explains how to access the Meter Reading web services, lays out the format and construction of REST messages used to exchange data, and briefly describes the Authentication and Authorization methods used to ensure security. This guide is designed to assist Meter Readers develop personal interfaces that interact and exchange meter reading data with the Meter Reading web services. It will help Meter Readers comprehend and construct the meter reading data messages essential for data exchange with the Meter Reading application. It can also help Meter Readers develop software that generates upload files for use with the Meter Reading user interface, or software that parses download files obtained from the Meter Reading user interface. Scope and prerequisite knowledge This document is offered to ISO New England Meter Readers as an aid in developing new interfaces as well as assisting in the upgrade/re-design of existing interfaces.
    [Show full text]
  • Biotechniques Author Guidelines
    Version: 04/03/2020 BioTechniques Author Guidelines This document outlines how to prepare articles for submission. We recommend you read these guidelines in full before submitting your article or making an article proposal. Table of Contents Journal aims & scope .............................................................................................................................. 3 Audience ................................................................................................................................................. 3 At-a-glance article formatting checklist .................................................................................................. 4 Search engine optimization .................................................................................................................... 5 Article types ............................................................................................................................................ 6 Benchmarks, Reports and Letters to the Editor .................................................................................. 6 Reviews & Practical Guides ................................................................................................................. 8 Interviews............................................................................................................................................ 9 Expert Opinions ................................................................................................................................
    [Show full text]
  • IHE IT Infrastructure Technical Framework Supplement Mobile
    Integrating the Healthcare Enterprise 5 IHE IT Infrastructure Technical Framework Supplement 10 Mobile access to Health Documents (MHD) ® 15 FHIR DSTU2 Trial Implementation 20 Date: June 2, 2016 Author: IHE ITI Technical Committee Email: [email protected] 25 Please verify you have the most recent version of this document. See here for Trial Implementation and Final Text versions and here for Public Comment versions. Copyright © 2016: IHE International, Inc. IHE IT Infrastructure Technical Framework Supplement – Mobile access to Health Documents (MHD) ______________________________________________________________________________ Foreword This is a supplement to the IHE IT Infrastructure Technical Framework V12.0. Each supplement 30 undergoes a process of public comment and trial implementation before being incorporated into the volumes of the Technical Frameworks. This supplement is published on June 2, 2016 for trial implementation and may be available for testing at subsequent IHE Connectathons. The supplement may be amended based on the results of testing. Following successful testing it will be incorporated into the IT Infrastructure 35 Technical Framework. Comments are invited and may be submitted at http://www.ihe.net/ITI_Public_Comments. This supplement describes changes to the existing technical framework documents. “Boxed” instructions like the sample below indicate to the Volume Editor how to integrate the relevant section(s) into the relevant Technical Framework volume. 40 Amend Section X.X by the following: Where the amendment adds text, make the added text bold underline. Where the amendment removes text, make the removed text bold strikethrough. When entire new sections are added, introduce with editor’s instructions to “add new text” or similar, which for readability are not bolded or underlined.
    [Show full text]
  • Web Services Description Language (WSDL) Version 2.0 Part 0: Primer W3C Candidate Recommendation 6 January 2006
    Table of Contents Web Services Description Language (WSDL) Version 2.0 Part 0: Primer W3C Candidate Recommendation 6 January 2006 This version: http://www.w3.org/TR/2006/CR-wsdl20-primer-20060106 Latest version: http://www.w3.org/TR/wsdl20-primer Previous versions: http://www.w3.org/TR/2005/WD-wsdl20-primer-20050803 Editors: David Booth, W3C Fellow / Hewlett-Packard Canyang Kevin Liu, SAP Labs This document is also available in these non-normative formats: PDF, PostScript, XML, and plain text. Copyright © 2006 World Wide Web ConsortiumW3C ® (Massachusetts Institute of TechnologyMIT, European Research Consortium for Informatics and MathematicsERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply. Abstract This document is a companion to the WSDL 2.0 specification (Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language [WSDL 2.0 Core [p.83] ], Web Services Description Language (WSDL) Version 2.0 Part 2: Adjuncts [WSDL 2.0 Adjuncts [p.83] ]). It is intended for readers who wish to have an easier, less technical introduction to the main features of the language. This primer is only intended to be a starting point toward use of WSDL 2.0, and hence does not describe every feature of the language. Users are expected to consult the WSDL 2.0 specification if they wish to make use of more sophisticated features or techniques. Finally, this primer is non-normative. Any specific questions of what WSDL 2.0 requires or forbids should be referred to the WSDL 2.0 specification. 1 Status of this Document Status of this Document This section describes the status of this document at the time of its publication.
    [Show full text]