[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [no subject]
xNAL provides descriptions for every element and attribute, but it is up to
the users how they implement it. Interoperability of xNAL codified documents
depends on the both the parties agreeing on how the codification of the
schemas should be done.
This cannot be emphasized enough! Some examples of the "impedance
mis-match" that can occur without that might be in order. While any that
might be exhibited with regard to certain apparently same (like named)
elements for the standards mentioned in the table starting at line 997 might
be most revealing, it could be politically incorrect (or cooperation
damaging) to do so. Moreover, I at least would not relish poring over each
of those to find any. I suppose an easy one might be the fact that USA USPS
allows "unit" to mean any address subdivision to which that organization
encodes a ZIP+4, which could be a building, a whole floor (basement, lobby),
or some specific suite / apartment; BUT only ONE of those is allowed for
USPS "official" addressing (and ZIP+4 assignment). In other countries,
however, multiple units (more than one with different types and hierarchy)
may be allowed / defined.
I have already included comments on section "8.8 Formatting Names and
Addresses" - specifically with respect to retaining all original data
(punctuation included) and including features that allow formatted addresses
to be represented and then extracted from the encoding as they were
originally presented or "standardized".
I refrained from a "quibble" of mine in the first comments with regard to
section "8.9 Representing types of names and addresses"; but since more
specific / detailed comments have been requested on implementation, I will
digress and "quibble". The typing / naming of names as "first", "middle",
and "last" is problematic in at least two regards -
* "first", "middle", and "last" refer to conventional positional
aspects of name presentation.
* Since positional naming has apparently been avoided in other element
naming OR only had positional identification done as a (sub)type (or maybe
as an attribute?) as in
* "Thoroughfare" rather than "ThoroughfareTrailingType"
* Or <Direction type="Pre">West</Direction> rather than
"Predirectional".
*
------_=_NextPart_001_01C529AA.B61E8600
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40";>
<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
p.MsoBodyText, li.MsoBodyText, div.MsoBodyText
{margin-top:0in;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:.5in;
font-size:10.0pt;
font-family:Arial;}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
p.code, li.code, div.code
{margin-top:0in;
margin-right:.3in;
margin-bottom:0in;
margin-left:.3in;
margin-bottom:.0001pt;
text-align:justify;
background:#D9D9D9;
font-size:9.0pt;
font-family:"Courier New";}
span.EmailStyle18
{mso-style-type:personal;
font-family:Arial;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:601687347;
mso-list-type:hybrid;
mso-list-template-ids:1111638108 67698689 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:849294910;
mso-list-type:hybrid;
mso-list-template-ids:1653115486 67698703 67698689 67698693 67698689 =
67698703 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2
{mso-list-id:1409306214;
mso-list-type:hybrid;
mso-list-template-ids:-1426165948 67698689 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l2:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l3
{mso-list-id:2044477016;
mso-list-type:hybrid;
mso-list-template-ids:1759642224 67698703 67698713 67698693 67698689 =
67698703 67698693 67698689 67698691 67698693;}
@list l3:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l3:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l3:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
</head>
<body lang=3DEN-US link=3Dblue vlink=3Dpurple>
<div class=3DSection1>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>As requested, I will try to make =
some more
specific comments on section “8 Version 3.0 – =
Implementation Considerations
and Guidelines”.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>=
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Both the examples and formal =
diagrams are
good; but one can never have too many examples. Perhaps and =
appendix with
those would be in order. To make those accessible, they should =
probably
begin with very simple examples and proceed to the more complex. =
However,
showing the basic and advanced encoding side by side would probably be =
helpful.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>=
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Especially important for ease of =
use /
accessibility (AND to get folks to use the standard! … =
appropriately!) would
be some sort of chart or spreadsheet that relates some of the examples =
XML encoding
(basic and advanced) to the diagram elements. This helps =
“demystify”
the related elements and will, perhaps, remove any confusion (and maybe =
uncover
some disjunction?) among those =
representations.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>=
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>From lines 930-932, page 38 =
(bolded and
italicized emphasis <b><i><span =
style=3D'font-weight:bold;font-style:italic'>mine</span></i></b>)–=
<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>=
<p class=3DMsoBodyText><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt'>xNAL
provides descriptions for every element and attribute, but it is up to =
the
users how they implement it. <b><i><span =
style=3D'font-weight:bold;font-style:
italic'>Interoperability of xNAL codified documents depends on the both =
the
parties agreeing on how the codification of the schemas should be =
done.</span></i></b><o:p></o:p></span></font></p>
<p class=3DMsoNormal><b><i><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;=
font-style:italic'>This cannot be emphasized =
enough!</span></font></i></b><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'> Some examples of the “impedance =
mis-match” that
can occur without that might be in order. While any that might be
exhibited with regard to certain <i><span =
style=3D'font-style:italic'>apparently
same (like named) </span></i>elements for the standards mentioned in =
the table
starting at line 997 might be most revealing, it could be politically =
incorrect
(or cooperation damaging) to do so. Moreover, I at least would =
not relish
poring over each of those to find any. I suppose an easy one =
might be the
fact that USA USPS allows “unit” to mean any address =
subdivision to
which that organization encodes a ZIP+4, which could be a building, a =
whole
floor (basement, lobby), or some specific suite / apartment; BUT only =
ONE of
those is allowed for USPS “official” addressing (and ZIP+4
assignment). In other countries, however, multiple units (more =
than one
with different types and hierarchy) may be allowed / =
defined.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>=
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I have already included comments =
on
section “8.8 Formatting Names and Addresses” – =
specifically with
respect to retaining all original data (punctuation included) and =
including
features that allow formatted addresses to be represented and then =
extracted
from the encoding as they were originally presented or =
“standardized”.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>=
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I refrained from a =
“quibble”
of mine in the first comments with regard to section “8.9 =
Representing
types of names and addresses”; but since more specific / detailed
comments have been requested on implementation, I will digress and =
“quibble”.
The typing / naming of names as “first”, =
“middle”, and “last”
is problematic in at least two regards =
–<o:p></o:p></span></font></p>
<ul style=3D'margin-top:0in' type=3Ddisc>
<li class=3DMsoNormal style=3D'color:navy;mso-list:l2 level1 =
lfo7'><font size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>“first”,
“middle”, and “last” refer to conventional =
<i><span
style=3D'font-style:italic'>positional </span></i>aspects of name
presentation.<o:p></o:p></span></font></li>
<ul style=3D'margin-top:0in' type=3Dcircle>
<li class=3DMsoNormal style=3D'color:navy;mso-list:l2 level2 =
lfo7'><font size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Since
positional naming has apparently been avoided in other <i><span
style=3D'font-style:italic'>element </span></i>naming OR only had =
positional
identification done as a (sub)type (or maybe as an attribute?) as =
in<o:p></o:p></span></font></li>
<ul style=3D'margin-top:0in' type=3Dsquare>
<li class=3DMsoNormal style=3D'color:navy;mso-list:l2 level3 =
lfo7'><font size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>“Thoroughfare”
rather than “</span></font><font size=3D2 =
face=3DArial><span
lang=3DEN-IE =
style=3D'font-size:10.0pt;font-family:Arial'>ThoroughfareTrailingType=
221;</span></font><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></=
li>
<li class=3DMsoNormal style=3D'color:navy;mso-list:l2 level3 =
lfo7'><font size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Or
<Direction type=3D”Pre”>West</Direction> =
rather
than “Predirectional”.<o:p></o:p></span></font></li>
</ul>
<li class=3DMsoNormal style=3D'color:navy;mso-list:l2 level2 =
lfo7'><font size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><o:p> </o:p></span></f=
ont></li>
</ul>
</ul>
<p class=3DMsoNormal style=3D'margin-left:1.0in'><font size=3D2 =
color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p> </o:p=
></span></font></p>
</div>
</body>
</html>
------_=_NextPart_001_01C529AA.B61E8600--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]