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

 


Help: OASIS Mailing Lists Help | MarkMail Help

regrep-cc-review message

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


Subject: [Fwd: Re: [Ebxmlrr-tech] ObjectType: Core Component]



This email describes the need for CC Review TN to describe the canonical 
ObjectType for CoreComponents
within the ebXML Registry. BTW you may want to consider the WSRP - ebXML 
Registry TN as an input template
for the eventual TN produced by this SC. Notice it has an appendix for 
Caninical Metadata where this sort of info
is placed.

-------- Original Message --------
Subject: 	Re: [Ebxmlrr-tech] ObjectType: Core Component
Date: 	Fri, 27 Feb 2004 11:20:57 -0500
From: 	Farrukh Najmi <farrukh.najmi@sun.com>
To: 	Richard Lessard <Richard.Lessard@pwgsc.gc.ca>
CC: 	List Ebxmlrr-Tech (E-mail) <ebxmlrr-tech@lists.sourceforge.net>
References: 
<E343AA8326D32A419E3BA87675FFE41A1ACC1A@mb-ncr-026.ad.pwgsc-tpsgc.gc.ca>



Richard Lessard wrote:

>Thanks Farrukh,
>
>One issue I want to raise though, since Core Components are an actual part of the ebXML specifications, will an ObjectType be defined by the freebxml community, and stored in the registry? If it remains a "user defined" type, then sharing Core Components may be an issue for people who have different ObjectTypes defined for these Objects.
>  
>
Excellent point Richard.

This should be addressed by the CC Review SC of ebXML Registry TC.
They are defining how Core Components are published, managed and
discovered in an ebXML Registry. Part of that work should include
defining the canonical metadata (e.g. new ObjectTpes). needed by
the Core Components.

I will forward this email to the CC review SC on your behalf.

-- 
Regards,
Farrukh




-- 
Regards,
Farrukh




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