Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[mdt-sbvr.dev] RE: mdt-sbvr.dev Digest, Vol 2, Issue 5 Solid simplicity is an option

Title: mdt-sbvr.dev Digest, Vol 2, Issue 5
 


Van: mdt-sbvr.dev-bounces@xxxxxxxxxxx namens mdt-sbvr.dev-request@xxxxxxxxxxx
Verzonden: za 5-4-2008 18:00
Aan: mdt-sbvr.dev@xxxxxxxxxxx
Onderwerp: mdt-sbvr.dev Digest, Vol 2, Issue 5

Send mdt-sbvr.dev mailing list submissions to
        mdt-sbvr.dev@xxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
        https://dev.eclipse.org/mailman/listinfo/mdt-sbvr.dev
or, via email, send a message with subject or body 'help' to
        mdt-sbvr.dev-request@xxxxxxxxxxx

You can reach the person managing the list at
        mdt-sbvr.dev-owner@xxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of mdt-sbvr.dev digest..."


Today's Topics:

   1. RE: Wiki page for SBVR requirements (Stan Hendryx)


----------------------------------------------------------------------

Message: 1
Date: Fri, 4 Apr 2008 21:20:34 -0700
From: "Stan Hendryx" <stan@xxxxxxxxxxxxxxxx>
Subject: RE: [mdt-sbvr.dev] Wiki page for SBVR requirements
To: "'SBVR developer list'" <mdt-sbvr.dev@xxxxxxxxxxx>
Message-ID: <03a301c896d4$652bedb0$220110ac@Sirius>
Content-Type: text/plain;       charset="us-ascii"

Dave,

You wrote:
> In general, a considerable amount of work is needed to
> specify mappings between SBVR, UML, ODM, or others. 

Yes.

[Sjir (2008-04-05-1809 AMS time): If properly derived using proven methodological steps it is my experience is that this is much less than a considerable amount of time.] 



> I believe that this Eclipse project can help by providing
> reference implementations of mappings related to SBVR.

Absolutely. My suggestion is to do a mapping to OWL first, then use the ODM
mapping from OWL to UML to get to UML. By then, the IMM committee may have
the ER metamodel and the ER mapping to OWL added to ODM.

> SBVR focuses on business concerns, while ODM and UML target other needs.

This sentence from the Date-Time RFP indicates an all-to-common, and
unfortunate, misconception about the domain of SBVR. Some of us feel SBVR is
mis-named, that the name implies a limitation or focus on commercial
endeavors, such as the above, that was not intended by the OMG and that is
in fact not a limitation of SBVR at all. [Sjir (20087-04-05-1809 AMS time): I could not agree more.] I've heard suggestions to rename
SBVR to avoid the pigeon-hole effect of its name. The Business Semantics of
Business Rules RFP, to which SBVR is the adopted response, says, "The term
'business' [mass noun] is used here in its core sense, "a person's regular
occupation, profession, or trade," and refers to any kind of organized,
purposeful human work activity." [br/2003-06-03 6.1.1, p.21]. This is the
broad sense in which the term "business" should be considered when reading
SBVR. Certainly the drafters of the Date-Time RFP did not mean to imply that
ODM and UML are not targeted to business concerns (in any sense of the
word)!

What is different about ODM, UML, and SBVR are their forms of representation
and their communication targets. They are each capable of rendering
different, but isomorphic, representations of certain semantics. OWL (the
centerpiece of ODM) is machine readable. UML is readable by people fluent in
the UML notation language, and machines. SBVR is readable by people in their
own natural language, and machines. [Sjir (2008-04-05-1809 AMS time (emphasis added)

As such, SBVR provides a semantic bridge
between ordinary people and machines.
The logics and semantic
representational capabilities of SBVR are a superset of those of UML or OWL,
making SBVR more expressive than either of the others. [Sjir (2008-04-05-1809 AMS time: I am happy that this is finally in this project.] The combination of
its readability and its logical expressivity make SBVR well suited for
application in any domain that needs to capture a precise meaning of natural
language inscriptions and process these semantics with machines. Ability to
convert between SBVR representations and OWL or UML forms will greatly
magnify the usefulness of all of them. [Sjir (2008-04-05-1809 AMS time: Indeed, let us explain this, based on a solid framework and methodology and using intuitive yet significant examples starting in the world of the reader and that is - for the vast majority of persons who want to learn SBVR -not the generic conceptual schema.]

> The date and time vocabulary solicited in this document
> will serve as a study example for analyzing what model "equivalence"
means.

Certainly a good choice for a study example. To me, semantic equivalence of
dates and times is a given. What needs to be analyzed are the
representational mappings that preserve meaning, not what "equivalence"
means.


Stan


Stan Hendryx
Hendryx & Associates
Sunnyvale, California

phone: 408 773-8089
mobile: 408 218-9455




------------------------------

_______________________________________________
mdt-sbvr.dev mailing list
mdt-sbvr.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-sbvr.dev


End of mdt-sbvr.dev Digest, Vol 2, Issue 5
******************************************


Back to the top