[Moims-ipr] comments on XFDU
Giaretta, DL (David)
moims-ipr@mailman.ccsds.org
Tue, 30 Sep 2003 13:39:08 +0100
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C3874F.D6FC617A
Content-Type: text/plain
Comments on XML Structure and Construction Rules dated 25th Aug 2003
D Giaretta
Section 2.1, para before figure 2: mentions BLUE line - not helpful in black
and white print - change line style.
Section 3.1 - the order of the bullet points should match the order in which
they are discussed in the following sub-sections
Section 3.2.5 - in the para after the bullets the statement " ... but is not
supported by most XML parsers." - suggest we append "at the time of writing"
after "parsers", to make it clear that this situation may change. The same
applies to the following paragraph in the discussion of Java tools. I agree
that it makes sense to constrain ourselves to things which existing tools
support, as long as we can see a way to include the better methods later.
Section 3.3.1 - most of the bullets are pretty clearly true in the text, but
the first bullet about SFDU and and Control Authority concepts is not. We
should have some text that show whether or not this is true - perhaps in an
appendix.
Section 5.4 - bullet 2 - do we want to define a standard vocabulary for use
in the environment section. My answer would be yes but not in this version.
So we should begine with free text but design it to be extensible later.
Section 12.3.2 (misnumbered in the doc) "Java-Based mechanism" - just
specifying a Java class is almost certainly not enough. ONe needs something
akin to the JNLP information i.e. specify what version of the JVM is needed
etc.
Section 14 - Example XFDU - there is a <dmdMD> tag which does not appear in
the Schema
Section 15.2 - it should be made clear here whether or not XFDU is
compatible with METS i.e. is an XFDU object also a METS object? This is
especially important if we use the same tag names as METS.
Overall I think that this docuemnt is fine. My only concern is that it is
complex and I'll feel happier when we walk through some examples and maybe
see some code working.
...David
------_=_NextPart_001_01C3874F.D6FC617A
Content-Type: text/html
<html>
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 10 (filtered)">
<style>
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:Arial;}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle17
{font-family:Arial;
color:windowtext;}
@page Section1
{size:595.3pt 841.9pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-GB link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'>Comments
on XML Structure and Construction Rules dated </span></font><font
size=2><span style='font-size:10.0pt'>25th Aug 2003</span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'> </span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'>D
Giaretta</span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'> </span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'>Section
2.1, para before figure 2: mentions BLUE line - not helpful in black and white
print - change line style.</span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'> </span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'>Section
3.1 - the order of the bullet points should match the order in which they are
discussed in the following sub-sections</span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'> </span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'>Section
3.2.5 - in the para after the bullets the statement " ... but is not
supported by most XML parsers." - suggest we append "at the time of
writing" after "parsers", to make it clear that this situation
may change. The same applies to the following paragraph in the discussion of
Java tools. I agree that it makes sense to constrain ourselves to things which
existing tools support, as long as we can see a way to include the better
methods later.</span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'> </span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'>Section
3.3.1 - most of the bullets are pretty clearly true in the text, but the first
bullet about SFDU and and Control Authority concepts is not. We should have
some text that show whether or not this is true - perhaps in an appendix.</span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'> </span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'>Section
5.4 - bullet 2 - do we want to define a standard vocabulary for use in the
environment section. My answer would be yes but not in this version. So we
should begine with free text but design it to be extensible later.</span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'> </span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'>Section
12.3.2 (misnumbered in the doc) "Java-Based mechanism" - just
specifying a Java class is almost certainly not enough. ONe needs something
akin to the JNLP information i.e. specify what version of the JVM is needed
etc.</span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'> </span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'>Section
14 - Example XFDU - there is a <dmdMD> tag which does not appear in the
Schema</span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'> </span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'>Section
15.2 - it should be made clear here whether or not XFDU is compatible with METS
i.e. is an XFDU object also a METS object? This is especially important if we
use the same tag names as METS.</span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'> </span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'>Overall
I think that this docuemnt is fine. My only concern is that it is complex and
I'll feel happier when we walk through some examples and maybe see some code
working.</span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'> </span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'>...David</span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'> </span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt'> </span></font></p>
</div>
</body>
</html>
------_=_NextPart_001_01C3874F.D6FC617A--