[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CDM Governanance

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: CDM Governanance
  • Date: Wed, 11 Dec 2013 19:13:03 +0000
Thanks.

The software application isn¹t called CDM - we defined a Common/Canonical
Data Model (CDM) for the application and we¹ve grown the CDM over 3 years.
We are at a point where we are trying to standardize further to include
governance outside of our current project - because we have a
producer/consumer relationship with other projects that leverage this CDM.
Managing changes to the CDM now is critical.

I am surprised that you don¹t have a governance model for your CDM, given
the groups exchanging data.

No further questions.

Greg


On 12/11/13, 1:33 PM, "John Caron" <address@hidden> wrote:

>Hi Greg:
>
>So you have some other software that just happens to be called CDM?
>
>To answer your question, we dont have an explicit governance model. The
>software is free OSS on github that anyone can fork, with an MIT
>license. Mostly people give us pull requests which we accept if there
>are no conflicts. Issues are submittted on the public email list, the
>private support webapp, or on JIRA issue tracking.
>
>Unidata "owns" the project and we decide on priorities for our own
>development. We have a steering committee to help us set priorities.
>There have been significant contributions by other groups, especialy for
>THREDDS, which is the server that uses the CDM.
>
>CDM is a software library used by other projects, but controlled by
>Unidata. We use XSD for validating XML and use REST APIs in THREDDS, but
>not WSDL.
>
>John
>
>On 12/11/2013 9:08 AM, John Caron wrote:
>> On 12/11/2013 8:33 AM, Greg Monahan wrote:
>>> Sorry, CDM = Common Data Model.
>>>
>>> I saw that you edited the Unidata's Common Data Model Version 4 page at
>>> http://www.unidata.ucar.edu/software/thredds/current/netcdf-java/CDM/
>>>
>>> and was wondering what governance model you used to manage change/risk
>>> while providing interoperability/growth. This can be as detailed as
>>> XSD versioning all the way up to WSDL and requirements vetting.
>>> Any/all ideas are desired.
>>>
>>> Thanks,
>>> Greg Monahan
>>>
>>>
>>> From: John Caron <address@hidden
>>><mailto:address@hidden>>
>>> Date: Wednesday, December 11, 2013 at 10:17 AM
>>> To: Greg Monahan <address@hidden <mailto:address@hidden>>
>>> Subject: Re: CDM Governanance
>>>
>>> On 12/11/2013 8:12 AM, Greg Monahan wrote:
>>>> Mr. Caron:
>>>>
>>>> We are in the process of constructing governance for managing
>>>> change/risk in our CDM. What governance processes/standards are
>>>> Unidata using to manage your CDM?
>>>>
>>>> Thanks in advance,
>>>>
>>>> Greg Monahan
>>>> Federal Solutions Group
>>>> Life Cycle Engineering <http://www.lce.com>
>>>> Best Places to Work <http://www.lce.com>
>>>>
>>>> 4360 Corporate Road | Charleston,SC 29405
>>>> Phone: | Mobile: (843) 696-5242
>>>>
>>>> Website <http://www.lce.com> | Map
>>>> 
>>>><https://maps.google.com/maps?f=q&amp;hl=en&geocode=&q=4360+corporate+r
>>>>oad,+charleston,+sc+29405&sll=32.836886,-80.019704&sspn=0.040818,0.0658
>>>>32&ie=UTF8&ll=32.836941,-80.018642&spn=0.010204,0.016458&t=h&z=16&msa=0
>>>>&msid=105530030240863834900.000453f43ef47b7f895da>
>>>> | Email <mailto:address@hidden> | LinkedIn Profile
>>>> <http://www.linkedin.com/in/gregmonahan/>
>>>>
>>>> 
>>>><https://www.facebook.com/LifeCycleEngineering><http://www.linkedin.com
>>>>/company/life-cycle-engineering><https://twitter.com/LCE_Today>
>>>>
>>>
>>> what is your "CDM?"
>>
>> So when you say "your CDM", do you mean that you have a fork of "my
>> CDM", or something else?