public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Boris Daix <Boris.Daix@insa-lyon.fr>
To: blinux-list@redhat.com
Subject: Re: UML via XML ?
Date: Wed, 30 Oct 2002 17:42:08 +0100	[thread overview]
Message-ID: <87u1j3vpy7.fsf@pulsar.resi.insa-lyon.fr> (raw)
In-Reply-To: <Pine.LNX.4.21.0210262304390.612-100000@keynes.cs.toronto.edu> (Neil Graham's message of "Sat, 26 Oct 2002 23:21:27 -0400")

Hi,

   And thank you for advice and remarks.  I'll tell you when I'll find
good solution, if any :-) 

bye

Neil Graham <neil@cs.toronto.edu> writes:

> Hi Boris,
>
> On Sat, 26 Oct 2002, Boris Daix wrote:
>
>> I feel the solution is not so far... I can say
>> that, for sure, the software you mentionned can export UML works in
>> XML-like formats, that's already a not-so-bad thing.
>
> So if I understand your plan, you're planning to figure out the
> (indirect) mapping from UML to XMI, then use an SGML editor to write XMI
> documents that you'll then feed to a UML generator.  Evidently, this is
> indeed possible.  
>
>> Well, psgml is an emacs-mode, not a parser.  But anyway, I've read
>> that SGML parser can read XML, as HTML : the Python modules for SGML
>> are often used to parse HTML, as it's a "tag-fashion" language too.
>
> HTML is an SGML language; XML is not.  The trouble with using an SGML
> editor to generate XML is that you're very likely to generate an
> ill-formed XML document, which will cause an XML processor--like the one
> that must underlie the UML generator--to barf all over your shoes.  I'm
> certain emacs will have some kind of native XML mode, and equally that
> emacspeak will support it well (TV Raman helped develop VoiceXML, so I
> daresay he'll have completely solved this problem.  :) )  But this is
> an anthill compared with the mountain of the core problem...
>
>> He he...  I believe that if I say to my teatchers "Hey, look, with
>> GNU/Linux, I'm able to work with UML (via XML)", I'm sure Open Software
>> would be clapped for hours ! :-)
>
> No question.  If I were you though, I think I'd unearth my manual tactile
> diagram-drawing tools and crank UML out that way.  That's how I did
> digital circuit diagrams way back when and it worked well enough; but then
> everyone else was working manually too, so my disadvantage wasn't
> acute.  But I'd analogize the XMI-to-UML solution to writing Java by using
> a binary editor to produce bytecode, then using a disassembler to induce
> Java from it...  In fact, that'd probably be much easier since bytecode
> maps naturally back to Java, whereas XMI only maps to UML via the indirect
> route of the MOF.  :)
>
> Anyway, best of luck!  I dunno about other folks, but I'd love to hear how
> you end up solving this problem; it's one more and more of us will face in
> the future, no doubt about it.
>
> Cheers,
> Neil
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
>

-- 
Boris Daix

	"Feel free to be Free, or not to be..."




      reply	other threads:[~ UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Boris Daix
 ` Neil Graham
   ` Boris Daix
     ` Neil Graham
       ` Boris Daix [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87u1j3vpy7.fsf@pulsar.resi.insa-lyon.fr \
    --to=boris.daix@insa-lyon.fr \
    --cc=blinux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).