[OSGeo-Discuss] Defining a GIO position (or attmepting to . . .)
Basques, Bob (CI-StPaul)
bob.basques at ci.stpaul.mn.us
Wed Oct 16 08:34:18 PDT 2013
Vendor lock-in, or rather preventing it, would be a strong second as far as reasons go, but it's not really applicable to describing a positions work items (I don't think) and seems like it might be closer to a policy issue (in my mind).
Thanks for the feedback.
> -----Original Message-----
> From: Arnie Shore [mailto:shoreas at gmail.com]
> Sent: Wednesday, October 16, 2013 10:04 AM
> To: Basques, Bob (CI-StPaul)
> Cc: osgeo-discuss (discuss at lists.osgeo.org)
> Subject: Re: [OSGeo-Discuss] Defining a GIO position (or
> attmepting to . . .)
> Well, adherence to standards is integral to the issue of
> interoperability, a critical project success factor in this
> increasingly interconnected world.
> And, there's no motivation for vendor lock-in, since the revenue
> protection motivation (usually!) doesn't exist. (I can tell you
> re all of the verbiage I've excreted in a prior life justifying
> sole-source procurements.)
> Also, possibly important for the devout among us is that the Good
> Lord must love standards; She made so many of them!
> On 10/16/13, Basques, Bob (CI-StPaul)
> <bob.basques at ci.stpaul.mn.us> wrote:
> > Hi all,
> > I wonder if I could get some feedback on the following
> statement, I'm
> > looking for the other side of the argument (I know it's hard to
> > yourself there :c).
> > "Open Source software enforces standards" ... <snip />
More information about the Discuss