Michael F.,
I completely agree.
The use of whitespace should be deliberate and determined.
A particular unicode character should be used rather than simply a
"space" (which to most means & #x20;).
This could server as a delimiter(s) for certain order of information.
This would solve the "character" versus "byte" problems that may
occur when strings are cut.
Mike Ferrando
Library Technician
Library of Congress
Washington, DC
202-707-4454
--- "Fox, Michael" <[log in to unmask]> wrote:
> There's no problem, only that it would be helpful as people write
> tools
> to exploit this information that the data be encoded consistently.
> Software is typically matching on text strings where the difference
> between
>
> encodinganalog="110 2_ $a"
> encodinganalog="110 2 $a"
>
> and
>
> encodinganalog="1102_$a"
> encodinganalog="1102 $a"
>
> and
>
> encodinganalog="110$a"
> encodinganalog="110$a"
>
> may be significant or at least a major headache to the programmer
> who
> has to account for a whole range of possibilities.
>
> Michael
>
>
>
> -----Original Message-----
> From: Encoded Archival Description List [mailto:[log in to unmask]] On
> Behalf
> Of MicheleR
> Sent: Wednesday, August 24, 2005 5:34 PM
> To: [log in to unmask]
> Subject: encoding analog format
>
>
> >> So, how does one represent
> >>
> >> 110 2_ $aMinnesota Historical Society
> >>
> >> in an encodinganalog in <origination><corpname> where the
> underscore
> >> represents a blank space?
>
> Maybe I'm missing something obvious but both these options seem to
> parse
>
> just fine.
>
> encodinganalog="110 2_ $a"
> encodinganalog="110 2 $a"
>
> What's the problem with the underscore or the space?
>
> Michele
>
____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
|