OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

regrep message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [regrep] Web Site update request


<Quote>
mm1: Whether or not it follows the recommendations of ebXML Reg/Rep 
should not devalue the work that was done nor its relevance as a 
Registry/Repository implementation. If you used this entrance criteria, 
many projects could not be communicated to the community.
</Quote>

I completely disagree. We should not be sending mixed messages about the
recommendations that we make. The information in the Case Study
blatantly contradicts in some cases the approaches that we are taking,
with particular regard to our level of adoption of the UN/CEFACT Core
Components work. I won't continue with this debate, and will take it up
privately with Kathryn if necessary.

Joe

Monica Martin wrote:
> 
> Chiusano Joseph wrote:
> 
> >I have the following concerns with posting the Case Study paper on our
> >site:
> >
> >(1) The paper is not an OASIS product, yet it uses the OASIS and ebXML
> >logos and format. It is also listed as being copyright OASIS, which is
> >incorrect (at an extreme, it can be considered fraud - not accusing
> >anyone of that though).
> >
> >
> mm1: The paper was submitted as you see by the LoMakeFi project (OASIS
> did not complete this case study).  We have also opted with other case
> studies to provide a copyright if the originator requested it (such as
> for Apelon with SAGE project).
> 
> If you note the work submission, the project team is going to donate
> their work to ebxmlrr or into the Reg/Rep effort.
> 
> I would suggest you get more information prior to inferring what you
> indicated above which raises undue concerns or confusion.
> 
> >(2) The paper describes approaches to implementation of Core Components
> >in ebXML registry that are not necessarily in line with the approaches
> >that we will be proposing as part of the Technical Note (in fact I can
> >tell you that there are contridictions). As Chair of the Core Components
> >Review Subcommittee, I request that this paper not be listed on our
> >site.
> >
> >
> mm1: Whether or not it follows the recommendations of ebXML Reg/Rep
> should not devalue the work that was done nor its relevance as a
> Registry/Repository implementation. If you used this entrance criteria,
> many projects could not be communicated to the community.
> 
> >Respectfully,
> >Joe
> >
> >
> 
> To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.php.
begin:vcard 
n:Chiusano;Joseph
tel;work:(703) 902-6923
x-mozilla-html:FALSE
url:www.bah.com
org:Booz | Allen | Hamilton;IT Digital Strategies Team
adr:;;8283 Greensboro Drive;McLean;VA;22012;
version:2.1
email;internet:chiusano_joseph@bah.com
title:Senior Consultant
fn:Joseph M. Chiusano
end:vcard


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]