\documentclass[10pt]{article}

\usepackage{fullpage}
\usepackage{setspace}
\usepackage{parskip}
\usepackage{titlesec}
\usepackage[section]{placeins}
\usepackage{xcolor}
\usepackage{breakcites}
\usepackage{lineno}
\usepackage{hyphenat}





\PassOptionsToPackage{hyphens}{url}
\usepackage[colorlinks = true,
            linkcolor = blue,
            urlcolor  = blue,
            citecolor = blue,
            anchorcolor = blue]{hyperref}
\usepackage{etoolbox}
\makeatletter
\patchcmd\@combinedblfloats{\box\@outputbox}{\unvbox\@outputbox}{}{%
  \errmessage{\noexpand\@combinedblfloats could not be patched}%
}%
\makeatother


\usepackage{natbib}




\renewenvironment{abstract}
  {{\bfseries\noindent{\abstractname}\par\nobreak}\footnotesize}
  {\bigskip}

\titlespacing{\section}{0pt}{*3}{*1}
\titlespacing{\subsection}{0pt}{*2}{*0.5}
\titlespacing{\subsubsection}{0pt}{*1.5}{0pt}


\usepackage{authblk}


\usepackage{graphicx}
\usepackage[space]{grffile}
\usepackage{latexsym}
\usepackage{textcomp}
\usepackage{longtable}
\usepackage{tabulary}
\usepackage{booktabs,array,multirow}
\usepackage{amsfonts,amsmath,amssymb}
\providecommand\citet{\cite}
\providecommand\citep{\cite}
\providecommand\citealt{\cite}
% You can conditionalize code for latexml or normal latex using this.
\newif\iflatexml\latexmlfalse
\providecommand{\tightlist}{\setlength{\itemsep}{0pt}\setlength{\parskip}{0pt}}%

\AtBeginDocument{\DeclareGraphicsExtensions{.pdf,.PDF,.eps,.EPS,.png,.PNG,.tif,.TIF,.jpg,.JPG,.jpeg,.JPEG}}

\usepackage[utf8]{inputenc}
\usepackage[english]{babel}



\usepackage{float}








\begin{document}

\title{Convergence. Are we there yet?}



\author[1]{Mark Parsons}%
\affil[1]{Rensselaer Polytechnic Institute}%


\vspace{-1em}



  
  \date{May 18, 2024}


\begingroup
\let\center\flushleft
\let\endcenter\endflushleft
\maketitle
\endgroup





\selectlanguage{english}
\begin{abstract}
Infrastructure is not truly designed. It evolves. Infrastructure matures
and becomes more ubiquitous, accessible, reliable, and transparent as
`gateways' begin to connect myriad systems {[}1{]}. Often these gateways
that facilitate interconnection are `standards' --- be they formally
defined or tacitly accepted practice. There is a process of convergence
where communities begin to agree not only to use a common standard, but
to use it in a common way. This presentation examines two case-studies
of how standards adoption for data interoperability has progressed over
time: The development of an international Arctic data coordination
network over the last 15 years and work establishing the Research Data
Alliance. Observations suggest that convergence on standards and their
implementation is a dynamic process that works to negotiate and
interpret multiple, sometimes conflicting, concerns. Standards can be
adopted in different ways by different people and organizations and
still enable interoperability. An inclusive, ecological methodology to
system design is more resilient, adaptive, and responsive to
interdisciplinary needs. Overall, maintenance of standards and their
community is essential to their adoption and persistence.%
\end{abstract}%



\sloppy




\selectlanguage{english}
\FloatBarrier
\end{document}

