RDA RoDs

I was also thinking of chipping in on this. My favourite is the simplest: “RDA Recommendation” , This complements the simplicity of the ”RDA Discussion Documents”.
Juan.
From: gtlane=***@***.***-groups.org [mailto:***@***.***-groups.org] On Behalf Of Gerry Lane
Sent: 06 January 2014 16:34
To: ***@***.***-groups.org
Cc: parsom3=***@***.***-groups.org
Subject: [rda-outputs-ip] RDA RoDs
Mark.. You asked about a new name for the RDA Recommendations on Data. Just to stimulate this discussion before you provide the next revision of the Policy, I've listed a few obvious alteratives below. Since the documents will address much more than data.. do the following obvious alternatives generate any reaction from you and the team?
RDA Endorsed Document
RDA Endorsed Result
RDA Endorsed Recommendation
RDA Recommendation
RDA Endorsed Working Group Document
RDA Endorsed Working Group Result
RDA Endorsed Working Group Recommendation
Gerry Lane
***@***.***
Director, Open Source and Standards
Office: +1 914-765-4369
Cell: +1 914 714 8676
From: Mark Parsons
<***@***.***>
To: "***@***.***-groups.org" <***@***.***-groups.org>,
Date: 01/05/2014 02:54 PM
Subject: Re: [rda-outputs-ip] Telecon Monday
Sent by: parsom3=***@***.***-groups.org
________________________________
Thanks Larry.
My thoughts on maintenance are that the approach will need to evolve and be rather situational.
Currently, the RoD Criteria and Process says that a maintenance plan should say who does the maintenance: "A demonstrated community interested in the RoD is especially desirable. Possibilities for a maintenance group could include an RDA IG, an affiliate organisation, an ad hoc group that (re)convenes on a periodic schedule (e.g. annually), a new WG, etc.”
We can add to this, but I see this porcess document being maintained by the Secretariat who can update it as needed without afecting the core policy.
talk to y’all tomorrow,
-m. --
Full post: http://www.rd-alliance.org/telecon-monday.html
Manage my subscriptions: http://www.rd-alliance.org/mailinglist
Stop emails for this post: http://www.rd-alliance.org/mailinglist/unsubscribe/1143

I was also thinking of chipping in on this. My favourite is the simplest: “RDA Recommendation” , This complements the simplicity of the ”RDA Discussion Documents”.
Juan.
From: gtlane=***@***.***-groups.org [mailto:***@***.***-groups.org] On Behalf Of Gerry Lane
Sent: 06 January 2014 16:34
To: ***@***.***-groups.org
Cc: parsom3=***@***.***-groups.org
Subject: [rda-outputs-ip] RDA RoDs
Mark.. You asked about a new name for the RDA Recommendations on Data. Just to stimulate this discussion before you provide the next revision of the Policy, I've listed a few obvious alteratives below. Since the documents will address much more than data.. do the following obvious alternatives generate any reaction from you and the team?
RDA Endorsed Document
RDA Endorsed Result
RDA Endorsed Recommendation
RDA Recommendation
RDA Endorsed Working Group Document
RDA Endorsed Working Group Result
RDA Endorsed Working Group Recommendation
Gerry Lane
***@***.***
Director, Open Source and Standards
Office: +1 914-765-4369
Cell: +1 914 714 8676
From: Mark Parsons
<***@***.***>
To: "***@***.***-groups.org" <***@***.***-groups.org>,
Date: 01/05/2014 02:54 PM
Subject: Re: [rda-outputs-ip] Telecon Monday
Sent by: parsom3=***@***.***-groups.org
________________________________
Thanks Larry.
My thoughts on maintenance are that the approach will need to evolve and be rather situational.
Currently, the RoD Criteria and Process says that a maintenance plan should say who does the maintenance: "A demonstrated community interested in the RoD is especially desirable. Possibilities for a maintenance group could include an RDA IG, an affiliate organisation, an ad hoc group that (re)convenes on a periodic schedule (e.g. annually), a new WG, etc.”
We can add to this, but I see this porcess document being maintained by the Secretariat who can update it as needed without afecting the core policy.
talk to y’all tomorrow,
-m. --
Full post: http://www.rd-alliance.org/telecon-monday.html
Manage my subscriptions: http://www.rd-alliance.org/mailinglist
Stop emails for this post: http://www.rd-alliance.org/mailinglist/unsubscribe/1143

I like RDA Recommendation too. I will use this unless I hear an objection or a better idea.
cheers,
-m.
On Jan 6, 2014, at 10:10 AM, JuanBicarregui <***@***.***> wrote:
I was also thinking of chipping in on this. My favourite is the simplest: “RDA Recommendation” , This complements the simplicity of the ”RDA Discussion Documents”.
Juan.
From: gtlane=***@***.***-groups.org [mailto:***@***.***-groups.org] On Behalf Of Gerry Lane
Sent: 06 January 2014 16:34
To: ***@***.***-groups.org
Cc: parsom3=***@***.***-groups.org
Subject: [rda-outputs-ip] RDA RoDs
Mark.. You asked about a new name for the RDA Recommendations on Data. Just to stimulate this discussion before you provide the next revision of the Policy, I've listed a few obvious alteratives below. Since the documents will address much more than data.. do the following obvious alternatives generate any reaction from you and the team?
RDA Endorsed Document
RDA Endorsed Result
RDA Endorsed Recommendation
RDA Recommendation
RDA Endorsed Working Group Document
RDA Endorsed Working Group Result
RDA Endorsed Working Group Recommendation
Gerry Lane
***@***.***
Director, Open Source and Standards
Office: +1 914-765-4369
Cell: +1 914 714 8676
From: Mark Parsons
<***@***.***>
To: "***@***.***-groups.org" <***@***.***-groups.org>,
Date: 01/05/2014 02:54 PM
Subject: Re: [rda-outputs-ip] Telecon Monday
Sent by: parsom3=***@***.***-groups.org
________________________________
Thanks Larry.
My thoughts on maintenance are that the approach will need to evolve and be rather situational.
Currently, the RoD Criteria and Process says that a maintenance plan should say who does the maintenance: "A demonstrated community interested in the RoD is especially desirable. Possibilities for a maintenance group could include an RDA IG, an affiliate organisation, an ad hoc group that (re)convenes on a periodic schedule (e.g. annually), a new WG, etc.”
We can add to this, but I see this porcess document being maintained by the Secretariat who can update it as needed without afecting the core policy.
talk to y’all tomorrow,
-m. --
Full post: http://www.rd-alliance.org/telecon-monday.html
Manage my subscriptions: http://www.rd-alliance.org/mailinglist
Stop emails for this post: http://www.rd-alliance.org/mailinglist/unsubscribe/1143
--
Full post: http://www.rd-alliance.org/rda-rods.html
Manage my subscriptions: http://www.rd-alliance.org/mailinglist
Stop emails for this post: http://www.rd-alliance.org/mailinglist/unsubscribe/1148

On 1/6/14 8:37 PM, Mark Parsons wrote:
> I like RDA Recommendation too. I will use this unless I hear an
> objection or a better idea.
+1 for "RDA Recommendation"
Simple, no fuzz and to the point.
My 2 cents,
Raphael
>
> cheers,
>
> -m.
> On Jan 6, 2014, at 10:10 AM, JuanBicarregui
> <***@***.*** > wrote:
>
>> I was also thinking of chipping in on this. My favourite is the
>> simplest: “RDA Recommendation” , This complements the simplicity of
>> the ”RDA Discussion Documents”.
>>
>> Juan.
>>
>> *From:* gtlane=***@***.***-groups.org
>> [mailto:***@***.***-groups.org] *On
>> Behalf Of *Gerry Lane
>> *Sent:* 06 January 2014 16:34
>> *To:* ***@***.***-groups.org
>>
>> *Cc:* parsom3=***@***.***-groups.org
>>
>> *Subject:* [rda-outputs-ip] RDA RoDs
>>
>> Mark.. You asked about a new name for the RDA Recommendations on
>> Data. Just to stimulate this discussion before you provide the next
>> revision of the Policy, I've listed a few obvious alteratives below.
>> Since the documents will address much more than data.. do the
>> following obvious alternatives generate any reaction from you and the
>> team?
>>
>> RDA Endorsed Document
>> RDA Endorsed Result
>> RDA Endorsed Recommendation
>> RDA Recommendation
>> RDA Endorsed Working Group Document
>> RDA Endorsed Working Group Result
>> RDA Endorsed Working Group Recommendation
>>
>> */ /**/Gerry Lane/*
>> ***@***.***
>> Director, Open Source and Standards
>> Office: +1 914-765-4369
>> Cell: +1 914 714 8676
>>
>>
>>
>>
>> From: Mark Parsons
<***@***.*** >
>> To: "***@***.***-groups.org
>> "
>> <***@***.***-groups.org >,
>> Date: 01/05/2014 02:54 PM
>> Subject: Re: [rda-outputs-ip] Telecon Monday
>> Sent by: parsom3=***@***.***-groups.org
>>
>> ------------------------------------------------------------------------
>>
>>
>>
>> Thanks Larry.
>>
>> My thoughts on maintenance are that the approach will need to evolve
>> and be rather situational.
>>
>> Currently, the RoD Criteria and Process says that a maintenance plan
>> should say who does the maintenance: "A demonstrated community
>> interested in the RoD is especially desirable. Possibilities for a
>> maintenance group could include an RDA IG, an affiliate organisation,
>> an ad hoc group that (re)convenes on a periodic schedule (e.g.
>> annually), a new WG, etc.”
>>
>> We can add to this, but I see this porcess document being maintained
>> by the Secretariat who can update it as needed without afecting the
>> core policy.
>>
>> talk to y’all tomorrow,
>>
>> -m. --
>> Full post: http://www.rd-alliance.org/telecon-monday.html
>> Manage my subscriptions: http://www.rd-alliance.org/mailinglist
>> Stop emails for this
>> post: http://www.rd-alliance.org/mailinglist/unsubscribe/1143
>> --
>> Full post: http://www.rd-alliance.org/rda-rods.html
>> Manage my subscriptions: http://www.rd-alliance.org/mailinglist
>> Stop emails for this
>> post: http://www.rd-alliance.org/mailinglist/unsubscribe/1148
>
>
On 1/6/14 8:37 PM, Mark Parsons wrote:
> I like RDA Recommendation too. I will use this unless I hear an
> objection or a better idea.
+1 for "RDA Recommendation"
Simple, no fuzz and to the point.
My 2 cents,
Raphael

On Jan 6, 2014, at 2:34 PM, raphael <***@***.***> wrote:
Simple, no fuzz and to the point.
One of the things I love working internationally is the different perspectives. No native English speaker would have stated it quite this way (no fuzz), yet it works brilliantly.
I just liked the turn of phrase ;-)
-m.