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] ebXML Registry tutorial - update


Peter,

I think that is the whole point!?!  ; -)

It's a painting by numbers assembly kit - where
you insert your own painting....

Vague and obtuse is meant to intrigue and draw
the reader in....?  Unless of course Application Profile
Frameworks are the latest in vogue rage thing and
we're just not hip enough to realize that, eh?

"Application Profile Frameworks" - you have to
admit it sounds amazing - whatever it is!!

DW

----- Original Message ----- 
From: "Peter Kacandes" <pkacande@adobe.com>
To: <regrep@lists.oasis-open.org>
Sent: Monday, May 02, 2005 1:46 PM
Subject: RE: [regrep] ebXML Registry tutorial - update


"ebXML Registry Application Profiling Framework"

Is still completely meaningless.

What kinds of applications? For what purposes?

Profiling of what?

pk

-----Original Message-----
From: Farrukh Najmi [mailto:Farrukh.Najmi@Sun.COM]
Sent: Monday, May 02, 2005 7:13 AM
To: regrep@lists.oasis-open.org
Subject: Re: [regrep] ebXML Registry tutorial - update

Matthew MacKenzie wrote:

> I think that it is important for us to address external perception of
> who and what we are...so I more or less agree with Peter.
>
> Spend the time.  What is our rush?  4.0 should only appear in about 2
> years, so spend some time here on PR.

I think the cause for confusion here is the title of the thread and the lack
of context that some of the TC members have from the recent f2f meeting.

At the f2f meeting we decided that the current ebXML Registry tutorial was
misnamed and to repurpose the document to be a specification for how new
application specific profiles MUST be defined for ebXMl Registry.
The repurposed document is not meant to be a tutorial. The feeling was the
it is the most important technical document after the specs that the TC
delivers.

I supportthe need for a tutorial document but the current tutorial with its
content is the wrong document for that purpose and that is why we felt it
ought to be renamed and repurposed.

So far I still like the following title best for the repurposed document:

"ebXML Registry Application Profiling Framework"

Thanks.

>
> -Matt
>
> On 2-May-05, at 6:50 AM, BEDINI Ivan RD-BIZZ-CAE wrote:
>
>> 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.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
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> - 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]