<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
When I said that MIF was based on XML, I was taking that from this
page:<br>
<a class="moz-txt-link-freetext" href="http://www.ringholm.com/docs/03060_en_HL7_MIF.htm">http://www.ringholm.com/docs/03060_en_HL7_MIF.htm</a><br>
<b>"</b><b>The Model Interchange Format (MIF) is a set of XML
formats used to support the storage and exchange of HL7 version 3
artefacts as part of the HL7 Development Framework."</b><br>
I'm really not an expert on MIF or XML, but the syntax highlighting
in SciTE when I selected XML was much better than no highlighting at
all. <br>
<br>
--<br>
Shmuel Wolfson<br>
Technical Writer<br>
052-763-7133<br>
<br>
<br>
<div class="moz-cite-prefix">On 05-Oct-14 5:06 PM, Fred Ridder
wrote:<br>
</div>
<blockquote cite="mid:SNT150-W31FE82F0F2AFCB7830D27DBAA40@phx.gbl"
type="cite">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr">Sorry, Shmuel, but this is incorrect on a couple of
levels. <br>
<br>
First of all, it's simply impossible for MIF to have been *based
on* XML. MIF has existed since the very beginning of FrameMaker
in 1986. XML, on the other hand, was initially defined (XML 1.0
first edition) in 1998, 12 years after MIF was first included in
a released product. <br>
<br>
Second, the syntax may look similar, but the similarity extends
no deeper than the use of angle brackets as delimiters. <br>
In MIF, both the property/parameter name and its value or values
(which may themselves be bracket-delimited properties) are
contained inside the brackets. The end of each element is marked
by a simple right angle-bracket. This is not a problem in
simple, single-value elements that begin and end on the same
line; but to accommodate multi-line elements have multiple
properties nested within it, it is necessary to include a
commentary string that identifies what element is closed by the
immediately preceding bracket since all brackets have identical
appearance. <br>
In XML, on the other hand, the angle brackets only contain the
name of the element type. The content (e.g., the value of the
property or parameter) is *outside* the angle brackets,
delimited by a bracketed start tag (e.g., <elementX>) and
a corresponding explicitly named end tag (e.g.,
</elementX>) .<br>
<br>
When your text editor highlights it as XML, it would highlight
the opening angle bracket and parameter name string as if they
were XML start tags. But the parameter values would not be
highlighted because they appear in a location where XML does not
allow text. Depending on your editor, numerical parameter values
might be highlighted just because they are numerical. This
degree of highlighting might be useful, but it is essentially
accidental rather than by design.<br>
<br>
-Fred Ridder<br>
<br>
<div>> From: <a class="moz-txt-link-abbreviated" href="mailto:shmuelw1@gmail.com">shmuelw1@gmail.com</a><br>
> To: <a class="moz-txt-link-abbreviated" href="mailto:framers@lists.frameusers.com">framers@lists.frameusers.com</a><br>
> Subject: Re: What free Windows text editor should I use
to look at MIF files?<br>
> <br>
> MIF is based on XML, so select XML highlighting in the
text editor. I <br>
> just tried it in SciTE and it looks good after selecting
XML. It may <br>
> also work in NotePad++ but I didn't try it.<br>
> <br>
> --<br>
> Shmuel Wolfson<br>
> Technical Writer<br>
> 052-763-7133<br>
<br>
</div>
</div>
</blockquote>
<br>
</body>
</html>