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

 


Help: OASIS Mailing Lists Help | MarkMail Help

search-ws message

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


Subject: Re: [search-ws] Describing an abstract model using UML


Hi All

Sorry to be absent from the calls at the moment.  Will be back as soon as I can.

I just read the notes of the meeting and am pleased to read the recommendation to develop an abstract model.   Just to support Farrukhs recomendation to use UML diagrams (and the textual, and even tabular descriptions that accompany them),  the IMS have been using this format for their specifications for a number of years now and I find it a really useful way of producing and reading a specification once you get used to it! 

Regards
Kerry




On 08/12/2007, at 11:12 PM, Farrukh Najmi wrote:


Please see Figure 1 and Figure 2 in the regrep-rim-3.0.1-cd3.pdf in particular for use of UML to describe the infomodel.

Farrukh Najmi wrote:

It describes a detailed information model in abstract using UML and textual descriptions without a concrete XML Schema.
It provides an example of how one can describe an abstract model without having to use concrete schemas and wsdl etc.
Similarly the companion regrep-rs-3.0.1-cd3.pdf illustrates how protocols can be expressed in asbtract without needing WSDL.

As Buddha said to achieve enlightenment one must open their minds eye ;-)

LeVan,Ralph wrote:
Well, I waded through the first 60 pages of that 120 page document
(cd3.pdf) and saw nothing enlightening.

Farrukh, could you provide a little more accurate pointer to what you
think we should be seeing?

Thanks!

Ralph
-----Original Message-----
From: Farrukh Najmi [mailto:farrukh@wellfleetsoftware.com] Sent: Friday, December 07, 2007 4:14 PM
Subject: Re: [search-ws] Groups - Teleconference modified

...
 
The base specification will probably be relatively easy, the hard part
    
will be figuring out how to make Explain represent this abstract model.
 
      

This is actually quite easy. The solution is to use UML diagrams to
describe infomodel classes and their relationships and textual
descriptions to describe attributes of classes and any constraints on
them. See regrep-rim-3.0.1-cd3.pdf in following for an example:

.zip

I realize some find UML unfamiliar. This can easily be addressed by
adding 3-4 pages of boiler plate description that we can borrow from
other specs.
With that blueprint it is a lot more obvious and familiar.

  




-- 
Regards,
Farrukh Najmi




---------------------------------------------------------------------
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:

Kerry Blinco
e-Framework and Standards Manager, Link Affiliates, University of Southern Queensland; and
Technical Standards Adviser to the Department of Education Science and Training (DEST).  Australia.
Email:     kblinco@powerup.com.au
Phone:   +61 7 3871 2699             
Ph (Mobile) :    +61 419 787 992

The information contained in this e-mail message and any files may
be confidential information, and may also be the subject of legal professional privilege. 
If you think you may not be the intended recipient, or if you have received this e-mail in error,
please contact the sender immediately and delete all copies of this e-mail. If you are not the intended
recipient, you must not reproduce any part of this e-mail or disclose its contents to any other party.

This email represents the views of the individual sender, except where the sender expressly states otherwise.






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