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

I would suggest you get more information prior to inferring what you 
indicated above which raises undue concerns or confusion.

Monica: First of all, I would like a public apology for your completely
unprofessional behavior and false accusation.

Second of all, the Abstract says the following:

"Republica's LomakeFi Form Assembler tool is one of the results of a
project that aimed to produce electronic forms for the Finnish
Government based on existing paper forms. It uses the ebXML Core
Component approach to define the form parts and relies on ebXML Registry
to store information about these parts. This case study presents this
tool, the registry-based environment behind it and the work developed by
Republica Ltd for this project."

The word "donate" does not even appear anywhere in the document.

Third of all, I have no idea what LomakeFI is, so I could not have been
aware of anything that your speaking of.


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
> >
> >
tel;work:(703) 902-6923
org:Booz | Allen | Hamilton;IT Digital Strategies Team
adr:;;8283 Greensboro Drive;McLean;VA;22012;
title:Senior Consultant
fn:Joseph M. Chiusano

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