[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [regrep] ebXML Registry tutorial - update
So, instead of Industry Specific, use Domain Specific. Applies equally well to CCTS. Pk -----Original Message----- From: BEDINI Ivan RD-BIZZ-CAE [mailto:ivan.bedini@francetelecom.com] Sent: Monday, May 02, 2005 3:51 AM To: Peter Kacandes Cc: regrep@lists.oasis-open.org Subject: RE: [regrep] ebXML Registry tutorial - update Peter, Respectfully I disagree with this proposition. Sincerely I think that it will take us more time than necessary and it doesn't give us the attended feedback. IMO only public results are really interesting for others TCs. So it will ask more time for other people to understund and to find the good target -> more point of view for us that we have to consider -> more complexity added to the final solution. (all this work only for a title :-P) May be that it could take more sense to ask directly if there's more specific content that we could add to the document for better helps and simply acquire enough ackitances about registry application's implementation. I think that all basis for this doc are: 1. build a pragmatic documents for a *qick easy early* of a ebXML registry. (IMO the specification that we build here are especially for ebXML registry implementors and not for applications based on a registry, final user point of view) a. give a simple and efficient way to map a specific Information Model to the RIM (How effectively using ebRIM specification) b. give an example about how applications can simply implement the registry services defined into the ebRS specifications: - Defining Content Management Services - Defining Domain Specific Queries - Defining federation service - Using the Event Notification Feature - Defining Access Control (How effectively using ebRS specification) So, IMHO the candidates could be: 1. "Building applications using ebXML Registry" (IMO we can leave the decision to the future if we'll apply this document anly to "real world" ;-) 2. "ebXML Registry Application Profiling Framework" 3. "A Guide for Developing Applications using the ebXML Registry/Repository (IMO without "Industry Specific" because for example the CCTS profile isn't that...) 4. "Defining ebXML Registry Application Profiles" (Simply I don't put "content" here, only because a registry can be used only for a specific service, for example manage access control for another application...) IMO the problem with pt 4 is that it may be not clear what is a "profile" for a registry. After that I'm open to your proposition too :) thoughts?!? Regards, Ivan Le lundi 02 mai 2005 à 01:00 -0700, Peter Kacandes a écrit : > So I have an idea. So far it has been suggested that the material is > highly technical and is intended for a highly technical audience. > Personally, I think the title is meaningless and nobody will know what > it's about from the title. > > So, what I'd like to suggest is we ask a random sampling of people > from other approriate TCs what they think would be in a document with > such a title without giving them any other information beyond the title itself. > > Barring that, how about something like: > > Primer for Consistent Mapping from Domain Specific Information Models > to ebXML Registry Information Model > > At least that tells you something about the actual content of the document. > > Pk > > -----Original Message----- > From: Farrukh Najmi [mailto:Farrukh.Najmi@Sun.COM] > Sent: Sunday, May 01, 2005 6:57 AM > To: regrep@lists.oasis-open.org > Subject: Re: [regrep] ebXML Registry tutorial - update > > David Webber (XML) wrote: > > >I know this might be a bit retro' - and technobabbly free - but > > > >"Building real world applications using ebXML Registry" > > > > > Above title would be great for a paper of presentation on ebXML > Registry (hint, hint David) but not for the proposed Profiling Framework document. > > The proposed Profiling Framework document is a highly technical > document for a highly technical audience. > The audience is expected to be even more technical than that of the > RIM and RS specs. The key concepts it is covering are "Profile", > "Framework", "Application". > > So far I like the following best: > > "ebXML Registry Application Profiling Framework" > > Thanks. > > >DW > > > >----- Original Message ----- > >From: "Richard Martell" <rmartell@galdosinc.com> > >To: "'BEDINI Ivan RD-BIZZ-CAE'" <ivan.bedini@francetelecom.com>; > ><regrep@lists.oasis-open.org> > >Sent: Friday, April 29, 2005 1:28 PM > >Subject: RE: [regrep] ebXML Registry tutorial - update > > > > > > > > > >>Some more suggestions: > >> > >>"ebXML Registry Profiling Framework" > >>"Defining ebXML Registry Application Profiles" > >> > >> > >>-- > >>Richard > >> > >> > >> > >> > >>>-----Original Message----- > >>>From: BEDINI Ivan RD-BIZZ-CAE > >>>[mailto:ivan.bedini@francetelecom.com] > >>>Sent: Friday, 29 April, 2005 08:12 > >>>To: regrep@lists.oasis-open.org > >>>Subject: Re: [regrep] ebXML Registry tutorial - update > >>> > >>>Hi, > >>>What is the better title for the *tutorial* technical note? > >>> > >>>after the yesterday meeting we have proposed something like: > >>>"ebXML Registry Profile Development Guide" > >>> > >>>So please if someone of you has a better suggestion or some > >>>negative point for the new title, speak up now :) > >>> > >>>Many thanks, > >>>Ivan > >>> > >>> > >> > >>-------------------------------------------------------------------- > >>- To unsubscribe from this mail list, you must leave the OASIS TC > >>that generates this mail. You may a link to this group and all your > >>TCs in > >> > >> > >OASIS > > > > > >>at: > >>https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.p > >>hp > >> > >> > >> > >> > > > > > >--------------------------------------------------------------------- > >To unsubscribe from this mail list, you must leave the OASIS TC that > >generates this mail. You may a link to this group and all your TCs > >in OASIS > >at: > >https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.ph > >p > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. You may a link to this group and all your TCs in > OASIS > at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. You may a link to this group and all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]