That's exactly what the ValueListURN is for, David,
Well, its actually for a number of other things, as well, but it is
certainly used for this kind of thing at its most readily understandable
level.
Any list you care to use, as long as it is published (URN), and
maintained (versioned as needed) can be used. Down the line, we expect
that the necessity of maintaining these lists will convince folks in a
given domain and or set of jurisdictions, sets of agencies, etc, to come
together on standard lists that will converge to the smallest number of
lists that is needed for the domain. In the meantime, we have something
we can work with, without the hassle of trying to put together master lists.
Cheers,
Rex
David RR Webber (XML) wrote:
> Gary,
> That of course is a horse of a different color.
> What I'm seeing is that we don't want to use value pairs to capture
> the type of structured information content below - which is properly
> represented as reusable components.
> We do not need to repeat the disasters of EDI Z-segments!!!
>
> Thanks, DW
>
>
Original Message --------
> Subject: Re: [emergency] HAVE Conformance vs. Documentation vs.
> Released Schemas
> From: Gary Ham