<?xml version="1.0" encoding="UTF-8"?><StrategicPlanCore StartDate="2005-06-30" EndDate="" Date="2007-11-12"><Submitter FirstName="Owen" LastName="Ambur" PhoneNumber="" EmailAddress="Owen.Ambur@verizon.net"/><Source>https://www.niso.org/about/secure/Documents/BOD977.pdf</Source><Organization><Name>National Information Standards Organization</Name><Acronym>NISO</Acronym></Organization><Mission>Foster the development and maintenance of standards that facilitate the creation, persistent management, and effective interchange of information so that it can be trusted for use in research and learning.</Mission><Value><Name>Quality</Name><Description>NISO standards are proven, reliable, useful, and effective</Description></Value><Value><Name>Collaboration</Name><Description>NISO encourages participation of all stakeholders in its standards processes which are themselves conducted in a manner that is fair, open, and transparent</Description></Value><Value><Name>Agility and Vision</Name><Description>NISO moves quickly and imaginatively to identify, define, and address standards challenges and standards needs</Description></Value><Value><Name>Integrity</Name><Description>NISO earns trust through honesty and fairness</Description></Value><Goal>
									<SequenceIndicator>2.1.1</SequenceIndicator>
									<Name>Insersecting Communities of Interest</Name>
									<Description>Work with intersecting communities of interest.</Description>
									<Stakeholder>
										<Name></Name>
										<Description></Description>
									</Stakeholder>
									<Objective>
										<SequenceIndicator></SequenceIndicator>
										<Name></Name>
										<Description></Description>
										<Stakeholder>
											<Name></Name>
											<Description></Description>
										</Stakeholder>
										<OtherInformation></OtherInformation>
									</Objective>
									<OtherInformation>NISO understands that its work cannot be limited to a single type of institution.Information services cross institutional boundaries, and NISO will work with allparticipating communities in its efforts, and will actively engage thosecommunities and any representative standards organizations to achieve its goals</OtherInformation>
								</Goal><Goal>
									<SequenceIndicator>2.1.2</SequenceIndicator>
									<Name>Standards Life Cycle</Name>
									<Description>Work across the entire life cycle of an information standard.</Description>
									<Stakeholder>
										<Name></Name>
										<Description></Description>
									</Stakeholder>
									<Objective>
										<SequenceIndicator></SequenceIndicator>
										<Name></Name>
										<Description></Description>
										<Stakeholder>
											<Name></Name>
											<Description></Description>
										</Stakeholder>
										<OtherInformation></OtherInformation>
									</Objective>
									<OtherInformation>NISO's standards work will range from identifying need for a new standard tomaintaining a mature one. In this regard, NISO will:• act as a standards incubator helping to identify and articulate the need fornew information standards, and selecting the most promising for furtherdevelopment• identify nascent standards developed elsewhere and provide the supportnecessary to grow them into fully mature standards that are widelyimplemented• provide maintenance support that allows standards to change in concertwith evolving need• provide support for communities that wish to develop and maintain theirown standards in a manner that ensures their quality, integrity, reliability,and useWork at each of these stages will include education and support activities asnecessary to effective and inclusive standards development and use.</OtherInformation>
								</Goal><Goal>
									<SequenceIndicator>2.1.3</SequenceIndicator>
									<Name>Strategic Map</Name>
									<Description>Focus and prioritize its efforts in relation to a strategic map.</Description>
									<Stakeholder>
										<Name></Name>
										<Description></Description>
									</Stakeholder>
									<Objective>
										<SequenceIndicator></SequenceIndicator>
										<Name></Name>
										<Description></Description>
										<Stakeholder>
											<Name></Name>
											<Description></Description>
										</Stakeholder>
										<OtherInformation></OtherInformation>
									</Objective>
									<OtherInformation>To do this NISO will maintain a strategic map of the information landscape thatpinpoints features of the landscape most critical for the creation, persistentmanagement and exchange of trusted information in support of research andlearning. Decisions about which standards initiatives to invest in will be madewith reference to this strategic map, and with a view of NISO’s mission, itsmembers’ interests, and an awareness of those areas where NISO brings a uniqueperspective to the problem area. NISO will be guided by its mission and thestrategic map while moving into new areas of activity and when making life cycledecisions about standards the organization may want to divest itself of.</OtherInformation>
								</Goal><Goal>
									<SequenceIndicator>2.1.4</SequenceIndicator>
									<Name>Sustainable Standards</Name>
									<Description>Ensure that standards efforts are economically and organizationally sustainable.</Description>
									<Stakeholder>
										<Name></Name>
										<Description></Description>
									</Stakeholder>
									<Objective>
										<SequenceIndicator></SequenceIndicator>
										<Name></Name>
										<Description></Description>
										<Stakeholder>
											<Name></Name>
											<Description></Description>
										</Stakeholder>
										<OtherInformation></OtherInformation>
									</Objective>
									<OtherInformation>NISO understands that the resource commitment for standards increases as theymove through the lifecycle. NISO reviews standards at critical points in the lifecycle to determine if the expected benefit from the standard warrants continuedinvestment. NISO exits standards activities that provide insufficient benefit nomatter the stage of the lifecycle. This means that not every NISO initiative willresult in the development of a standard and that NISO may withdraw its effort orseek an alternate venue for a standard that reaches a point of diminishing returns.</OtherInformation>
								</Goal><Goal><SequenceIndicator>4.1</SequenceIndicator><Name>Development and Deployment</Name><Description>Rapid development and deployment of information standards</Description><Stakeholder/><Objective><Description/><Stakeholder/></Objective><OtherInformation>This change forces fundamental reconsideration of the very deliberate process of
standards creation that worked so well for NISO and its members in the past. NISO
must emerge as a nimble organization able quickly and effectively to identify, define,
and support adoption of key information standards. In the past, Standard
Development Organizations (SDO) were chartered at the national level and worked
through well-defined processes to progress standards from national to an international
level. NISO is very much a traditional SDO. The standards world of today is
populated by a growing variety of non-traditional organizations like specialized
standard setting consortia, ad hoc groups that spring up to create a single standard,
and other groups like open source consortia. The increasing range of standards
organizations is matched by an increasing array of standards formats and processes.</OtherInformation></Goal><Goal><SequenceIndicator>4.2</SequenceIndicator><Name>Functionality</Name><Description>Fundamental focus on functionality</Description><Stakeholder/><Objective><Description/><Stakeholder/></Objective><OtherInformation>In the largely static print world, libraries were the primary providers of access to the
information used in research and learning. In focusing its standards development
around libraries and the tightly knit community of information and service providers
who supported them, NISO had a logical and cost-effective means of developing
useful information standards. In the increasingly chaotic digital world, researchers
and learners acquire information from a wide variety of providers − only some of
which are libraries. Libraries themselves are increasingly managers of a wide variety
of information much of which they do not own in the way that they own their
traditional print collections. To continue to fulfill its historic mission, NISO must
focus on standards that support the greatest use and reuse of digital information and
that allow users to trust the authenticity of that information − regardless of who
creates or owns it A focus on functionality calls for NISO to provide leadership in
addressing the fundamental issues of providing access to trusted information in
today's environment, both to its dues-paying membership and to the wider community
that engages with NISO on selected projects. NISO must shape a view of the
information landscape and facilitate discussion amongst all the stake holders,
members and the wider community in order to build the support necessary to ensure
that the standards it helps to develop and maintain are adopted and implemented
effectively by the broadest possible community.</OtherInformation></Goal><Goal><SequenceIndicator>4.3</SequenceIndicator><Name>Other Standards Bodies</Name><Description>Review relations with other standards bodies</Description><Stakeholder/><Objective><Description/><Stakeholder/></Objective><OtherInformation>The production, management, and exchange of trusted research and learning
information with which NISO is centrally concerned is itself dependent upon the
deployment of standards in other parts of the information landscape that are governed
by other agencies, for example, by the World Wide Web Consortium (W3C), the
Internet Engineering Task Force (IETF), or the IMS Global Learning Consortium.
The evolving complexity of the information landscape and the extent and variety of
stakeholders acting upon it also requires that NISO be able to work across the entire
standards life cycle, though not necessarily with every standard. Communities of
information providers are increasingly emerging to define, create, or maintain
standards that are specifically relevant to their constituents. NISO needs to work with
these communities, leveraging distinctive strengths and applying respective efforts in
ways that are complementary and mutually beneficial. In many cases, NISO is likely
to find itself maturing or maintaining standards developed by others, and/or locating
responsibility for maintaining standards developed by NISO in third-party
organizations.</OtherInformation></Goal><Goal><SequenceIndicator>4.4</SequenceIndicator><Name>Core Standards</Name><Description>Determine its priorities and engage with standards activities that
advance the core mission</Description><Stakeholder/><Objective><Description/><Stakeholder/></Objective><OtherInformation>In a relatively static print-based world with few information providers of any real
significance, NISO could make decisions early in the standards cycle to see a few
standards through to their completion and ongoing maintenance. In a rapidly evolving
world with many information providers of significance, NISO must evaluate each
standards activity against the needs of the changing landscape. When a standard no
longer serves NISO's mission, NISO will act as a bridge and find a more appropriate
organization to maintain it and to extend it if appropriate.</OtherInformation></Goal><Goal><SequenceIndicator>5.1</SequenceIndicator><Name>Standards Development Process</Name><Description>Replicable Standards Development Process</Description><Stakeholder/><Objective><Description/><Stakeholder/></Objective><OtherInformation>For any of the products/processes above pertaining to standards development, this
document would be designed to help another organization, wishing to feed their
potential standard or guideline to NISO for certification/trial-use/maintenance to
understand the steps to be taken to facilitate that process. These documents would be
designed to provide a roadway by which any organization, group of interested
individuals or other standard developing group, could understand how to develop the
product/process to ensure that no substantial barrier is created that would prevent the
work from migrating to NISO. These documents are designed to be used by Product
Managers and software and standards developers.</OtherInformation></Goal><Goal><SequenceIndicator>5.2</SequenceIndicator><Name>Z39</Name><Description>Z39 Standards</Description><Stakeholder/><Objective><Description/><Stakeholder/></Objective><OtherInformation>Standards that are added to the Z39 series are developed through a formal standards
process and are accorded the status of ANSI/NISO standards. The process includes
the issuance of Draft Standards for Trial Use and a trial period of testing and analysis.
Formal standards are reviewed every five years and either renewed, modified or
retired. NISO standards in the Z39 series are available without charge on the NISO
web site.</OtherInformation></Goal><Goal><SequenceIndicator>5.3</SequenceIndicator><Name>Standards Maintenance</Name><Description>Standards Maintenance</Description><Stakeholder/><Objective><Description/><Stakeholder/></Objective><OtherInformation>A variety of maintenance activities may be required for the ongoing use of a
standard. This can include the registration of profiles, shared services, discussion
lists, and other features needed by the community using the standard. Although
NISO may outsource any of these features, it oversees the maintenance function
over key products.</OtherInformation></Goal><Goal><SequenceIndicator>5.4</SequenceIndicator><Name>Certification</Name><Description>Certification Program</Description><Stakeholder/><Objective><Description/><Stakeholder/></Objective><OtherInformation>Some standards organizations have the capability to certify that technology meets the
needs of a particular set of standards. The information community has some
certification programs, and NISO may contract with agencies that wish to create
certification for NISO standards.</OtherInformation></Goal><Goal><SequenceIndicator>5.5</SequenceIndicator><Name>Strategic Map</Name><Description>Strategic Map</Description><Stakeholder/><Objective><Description/><Stakeholder/></Objective><OtherInformation>The Strategic Map is one of the most essential and important products of NISO.
Developed from the recommendation of the Blue Ribbon Panel for a "synthesizing
framework" to guide NISO's decision-making, it is a publication used both internally
to the organization and externally by the membership to understand the information
landscape and how products/solutions interface and interoperate and where standards
exist and/or are needed to facilitate the interoperability of products. This document is
designed to be used by all levels of members’ staff, from the CEO/President to the
software engineers. It provides a context and understanding of what exists, what
doesn’t and where opportunities exist for both products and standards. The document
would be the result of NISO convening key, leading thinkers both from within the
NISO membership and outside, to serve on a development/review committee. This
document would likely be reviewed and/or revised quarterly, minimally every six
months.</OtherInformation></Goal><Goal><SequenceIndicator>5.6</SequenceIndicator><Name>White Papers</Name><Description>White Papers</Description><Stakeholder/><Objective><Description/><Stakeholder/></Objective><OtherInformation>NISO White Papers are contributed or solicited papers that address an issue that has implications for standards development. White Papers can be viewed as a prestandardization activity. A NISO White Paper might define and explore some of the questions that come into play before formal standardization work is started. Or a NISO White Paper might identify areas that are opportunities for standards development and suggest possible approaches. All White Papers are posted on the NISO website and published in hardcopy by NISO Press.</OtherInformation></Goal><Goal><SequenceIndicator>5.7</SequenceIndicator><Name>Best Practices</Name><Description>Best Practices</Description><Stakeholder/><Objective><Description/><Stakeholder/></Objective><OtherInformation>NISO Best Practices are utilized in scenarios where librarians, publishers, product
managers and developers are seeking an understanding of the most appropriate way to
utilize a standard or conduct a process within the context of the market in which they
function. Specifically, a Product Manger uses a best practices document when faced
with a variety of options within a standard, and seeks to know and/or understand
under a specific set of circumstances dictated by the market, or users requires
implementation of the options in select configurations. A best practices document
may also pertain to a process, and as such, may consist of recommendations
concerning how to conduct a process, write a proposal or other similar activities.</OtherInformation></Goal><Goal><SequenceIndicator>5.8</SequenceIndicator><Name>Profiles</Name><Description>Profiles</Description><Stakeholder/><Objective><Description/><Stakeholder/></Objective><OtherInformation>A profile is used when an organization developing a product that is written to comply
with a standard, but the standard contains sufficient complexity and/or vagaries so as
to make the final working compliance of the product uncertain if, for instance, valid
but incompatible parameters are selected. In these cases a “profile” is established to
outline a particular set of configuration options to ensure that products interfacing via
the standard perform as expected. These documents are typically going to be used by
programmers, product managers, and potentially customer service staff, all who are
involved in configuring a product for testing and/or use by customers. It provides
substantial value in that it enables the product to be moved to a demonstrable
production status quickly with minimum delays in testing and/or configuration.</OtherInformation></Goal><Goal><SequenceIndicator>5.9</SequenceIndicator><Name>Technical Reports and/or Guidelines</Name><Description>Technical Reports and/or Guidelines</Description><Stakeholder/><Objective><Description/><Stakeholder/></Objective><OtherInformation>Technical Reports and/or Guidelines are documents designed to provide useful
information for those trying to achieve a specific technical task. These can cover a
broad range of topics, for example the content, organization, and presentation of
indexes. The document will go into extensive detail about the subject, including areas
that need to be thought about and functionality that should be planned and/or
included. The document will provide enough detail for the user to be able to proceed
in developing or enhancing the applicable product.</OtherInformation></Goal><Goal><SequenceIndicator>5.10</SequenceIndicator><Name>Education</Name><Description>Education Programs (Pre and Post Standardization)</Description><Stakeholder/><Objective><Description/><Stakeholder/></Objective><OtherInformation>Educational Programs are designed for all types of people functioning within the
markets served by NISO and their primary purpose is sub-categorized depending
upon if it is a pre or post standardization program.
• Pre-Standardization. In this phase the focus of an educational program centers
on the objective of bringing together key players that face a problem that
could be solved through standardization, and, in a neutral forum, to scope
what that standardization process would need to encompass to provide a
solution.
• Post-Standardization. Once a standard is released, a critical component of the
standard being accepted and used is to educate the marketplace about the
availability of the standard, the means of implementation, and the resources
available to help in those areas.
• General Presentations to Organizations. As part of the NISO Educational
Programs, NISO will also arrange for general educational presentations to
organizations for a fee on any of the products and services produced. It is
generally expected that this type of training would be done on a subcontracting
basis with qualified personnel recruited on the topic of the
presentation.</OtherInformation></Goal><Goal><SequenceIndicator>5.11</SequenceIndicator><Name>Advocacy</Name><Description>Advocacy</Description><Stakeholder/><Objective><Description/><Stakeholder/></Objective><OtherInformation>Advocacy consists of representing the cause and/or need for standards where such
representation furthers the cause of NISO and its membership. NISO advocates for
standards in a wide variety of venues, including professional conferences, meetings
related to standards, and funding arenas. Examples of advocacy activities are:
• Working with and or becoming a member of other standards organizations.
• Speaking with or before legislative agencies.
• Lobbying NISO membership to support standards seen as critical to the future
success of NISO.
• Speaking at conferences to promote an understanding of the work of NISO
and, when required, specific standards held under the NISO umbrella.</OtherInformation></Goal><Goal><SequenceIndicator>5.12</SequenceIndicator><Name>Intelligence</Name><Description>Intelligence; Scan Of Environment and Explanation to Members</Description><Stakeholder/><Objective><Description/><Stakeholder/></Objective><OtherInformation>Intelligence scans are a service provided to the entire NISO membership, most
importantly to those who are Presidents, CEO’s, or Directors of member
organizations, The scan provides an overview and summary of what is happening in
specific market segments of technology. In particular it would focus on new product
developments and announcements, conference topics of interest, new and emerging
areas where NISO might play a key role. This scan would likely take the form of a
monthly or quarterly e-document, not longer than 5 pages, done in an attractive
graphic format to make for quick scanning.</OtherInformation></Goal></StrategicPlanCore>
