Hi Ray -
My thinking here is that SIA V1 is using UCDs for its UTYPE values, and what governs in this case is what makes sense for UCDs. If UCDs want to be case-insensitive values (probably so) then this is how they should be used in SIA V1 as well.
As you say, it can matter for clients. It might make sense for a validator to issue a warning in this case (here is usage which might break a simple client) , but not insist on a case-sensitive match.
On Mon, 12 Feb 2007, Ray Plante wrote:
> Hi Doug,
>
> Randy and I were discussing the use of UCDs in SIAP v1.0 compliant
> implementation and whether they are case-sensitive, particularly the "VOX:"
> UCDs. Although UCD1+ specifically states that UCD names are case
> insensitive, I don't think there was any definitive statement regarding the
> original UCDs in the available documentation when SIA was first written (all
> the official UCDs were published as all upper-case). The SIA spec uses mixed
> case for the VOX UCDs; consequently, I wrote my validator to insist on a
> case-sensitive match. Do you think this is an overly strict interpretation?
>
> It mainly makes a difference to clients. If we all understand these to be
> case-insensitive, then clients will need to transform the UCDs to a single
> case before comparing them.
>
> thanks,
> Ray
>
Received on 2007-02-12Z15:28:58