[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: Storage of UML models
Probably I missed something in the discussion but I haven't read anywhere that UML was a requirement for ebXML. The only thing that ebXML project teams have to define is behaviour and interfaces. The way a tool vendor will implement RegRep or BP specifications is out of scope. Of course, UML is a good way to define behaviours and interfaces and we will go that way. But what is, at the end of the day, stored in a repository is the implementer's problem; he can store UML models or whatever else he wants. The only mandatory thing for him to do is to expose what he has stored in an XML format compliant with the ebXML metamodel. The same for a BP tool vendor, he can define collaborative processes with whatever paradigm he wants as far as his clients are comfortable with that paradigm. The only mandatory thing for him to do is to publish/read those collaborations in/from an XML format compliant with the ebXML metamodel. So, I am very surprised to see that translation to XML would NOT be a fundamental service. In my opinion, XML exposure, and hence XML translation, is THE fundamental service. Please, correct me if I misinterpret your thoughts. -----Message d'origine----- De : Farrukh Najmi [mailto:Farrukh.Najmi@east.sun.com] Envoyé : mardi 12 septembre 2000 15:29 À : Allen, Terry Cc : ebXML-BP@lists.ebxml.org Objet : Re: Storage of UML models I agree with Terry's assessment that: "Translation to XML is a service implemented on top of a repository and is NOT, repeat NOT, a fundamental function of a repository or a registry.". In fact IMHO, translation from UML to XMI is very likely to be done by off-the-shelf tools (e.g. Together, Rose and IBM's XMI toolkit etc.) When reading the draft Registry Services v0.4 spec keep in mind that it is still in early stages of definition and still evolving. Comments from a BP perspective would be very useful in this formative stage. -- Regards, Farrukh "Allen, Terry" wrote: > It's not really an open issue; of course UML models can be stored > in a repository, and the draft regrep spec assumed so last time I > looked. That means > that the registry needs an appropriate classification scheme for > format (DTD, schema, UML). > > Translation to XML is a service implemented on top of a repository > and is NOT, repeat NOT, a fundamental function of a repository or > a registry. > > regards, Terry Allen > > -----Original Message----- > From: Mark Hale [mailto:mark.hale@ajubasolutions.com] > Sent: Monday, September 11, 2000 3:42 PM > To: ebXML-BP@lists.ebxml.org > Subject: Storage of UML models > > Has there been any more discussion concerning the storage of UML models in > the repository? The last discussion I have had with members of the BP group > was a translation to XML using XMI. We are looking in the POC group to see > which portions we can implement for a small demo for Tokyo. > > Thanks, > > Mark > > ________________________________________________________________________ > Mark A. Hale 650-940-4155 tel > Standards Architect 650-230-4065 fax > Ajuba Solutions mark.hale@ajubasolutions.com > 2593 Coast Avenue http://www.ajubasolutions.com > Mountain View, CA 94043
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC