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: [Fwd: ObjectRef and RegistryObject need common base type]


It seems that the regrep-comments list is now requiring that the sender 
be subscribed? This does not seem right. Should we not allow an external 
commenter to send comments unimpeded? I could not even figure out how to 
tell Mei Zhao to subscribe. Kathryn, could you please look into a 
solution to this recurring problem.

In any event the issue/suggestion below seems to make good sense from an 
OO stand point.


-------- Original Message --------
Subject: 	failure notice
Date: 	Thu, 25 Sep 2003 15:46:31 -0700 (PDT)
From: 	Mei-Xing Zhao <Mei-Xing.Zhao@sun.com>
Reply-To: 	Mei-Xing Zhao <Mei-Xing.Zhao@sun.com>
To: 	farrukh.najmi@sun.com



Hi Farrukh,

Seems like the mail got bounced back using 
"regrep-comment@lists.oasis-open.org". Is this email address correct?

Mei


------------- Begin Forwarded Message -------------

Date: 25 Sep 2003 22:25:19 -0000
From: MAILER-DAEMON@mail.oasis-open.org
To: Mei-Xing.Zhao@sun.com
Subject: failure notice

Hi. This is the qmail-send program at mail.oasis-open.org.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<regrep-comment@lists.oasis-open.org>:
Sorry, only subscribers may post. If you are a subscriber, please forward this 
message to regrep-comment-owner@lists.oasis-open.org to get your new address 
included (#5.7.2)

--- Below this line is a copy of the message.

Return-Path: <Mei-Xing.Zhao@Sun.COM>
Received: (qmail 18997 invoked by uid 60881); 25 Sep 2003 22:25:19 -0000
Received: from Mei-Xing.Zhao@Sun.COM by hermes by uid 0 with qmail-scanner-1.15 
 (spamassassin: 2.55.  Clear:SA:0(0.0/7.0):. 
 Processed in 0.187736 secs); 25 Sep 2003 22:25:19 -0000
Received: from unknown (HELO brmea-mail-3.sun.com) (192.18.98.34)
  by mail.oasis-open.org with SMTP; 25 Sep 2003 22:25:19 -0000
Received: from phys-hanwk16-1.ebay.sun.com ([129.149.1.5])
	by brmea-mail-3.sun.com (8.12.10/8.12.9) with ESMTP id h8PMQBkv011017
	for <regrep-comment@lists.oasis-open.org>; Thu, 25 Sep 2003 16:26:12 
-0600 (MDT)
Received: from mrhappy (mrhappy.SFBay.Sun.COM [129.149.182.90])
	by phys-hanwk16-1.ebay.sun.com (8.11.7+Sun/8.10.2/ENSMAIL,v2.1p1) with 
SMTP id h8PMQA624846;
	Thu, 25 Sep 2003 15:26:11 -0700 (PDT)
Message-Id: <200309252226.h8PMQA624846@phys-hanwk16-1.ebay.sun.com>
Date: Thu, 25 Sep 2003 15:26:10 -0700 (PDT)
From: Mei-Xing Zhao <Mei-Xing.Zhao@Sun.COM>
Reply-To: Mei-Xing Zhao <Mei-Xing.Zhao@Sun.COM>
Subject: ObjectRef and RegistryObject need common base type
To: regrep-comment@lists.oasis-open.org
Cc: Mei-Xing.Zhao@Sun.COM
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 3uWnPlezE/mFD7l3h/Utgw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.6_06 SunOS 5.8 sun4u sparc 
X-Spam-Status: No, hits=0.0 required=7.0
	tests=none
	version=2.55
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)

Dear ebXML TC,

During our implementation of the ebXML Registry version 2.5 
specification we came across a minor limitation in the rim.xsd schema 
and would like to suggest a simple improvement to make implementation 
easier.

Currently the rim.xsd schema has the RegistryObjectType and 
ObjectRefType defined. Both these types have an id and home attributes 
defined. In many situations during implementation it is desirable to 
treat an ObjectRef and RegistryObject symmetrically. This is currently 
not possible because the current schema does not provide a common base 
type for RegistryObjectType and ObjectRefType.

The enhancement we would like to propose is to add a common base type 
called IdentifiableType from which we derive both RegistryObjectType and 
ObjectRefType :
                                 
                               IdentifiableType
                                      |
                         ----------------------------
                         |                          |
                 RegistryObjectType            ObjectRefType


In such an approach factor out the id and home attributes that are 
common to both RegistryObjectType and ObjectRefType and put them in the 
new IdentifiableType.

Regards,
Mei


********
Mei-Xing Zhao                     
Enterprise Messaging & Integration, CSSIT   
Sun Microsystems, Inc.           
(510) 936-3520 
x13520 (internal)
     

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE:  This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged
information.  Any unauthorized review, use, disclosure or
distribution is prohibited.  If you are not the intended
recipient, please contact the sender by reply email and destroy
all copies of the original message.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



------------- End Forwarded Message -------------


********
Mei-Xing Zhao                     
Enterprise Messaging & Integration, CSSIT   
Sun Microsystems, Inc.           
(510) 936-3520 
x13520 (internal)
     

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE:  This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged
information.  Any unauthorized review, use, disclosure or
distribution is prohibited.  If you are not the intended
recipient, please contact the sender by reply email and destroy
all copies of the original message.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~




-- 
Farrukh




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