Sharing of namespace for code sets and datatypes

[kleihan]

Namespace for code sets and datatypes share a single namespace in Orchestra v1.0. With Orchestra v1.1 there are now separate attribute for a field having either a datatype or a code set (FIXTradingCommunity/fix-orchestra#170).

Section 3.7 Code sets states the following:

The names of code sets and datatypes share a common namespace and must
be unique within a schema. This constraint is enforced by the XML schema.

Can this paragraph be removed as it no longer holds true?

[patricklucas]

I concur that, following the change in fix-orchestra#171, this paragraph no longer holds true (for Orchestra v1.1).

For what it's worth, a reason this situation arose in the first place is that in many ways, code sets are types. Consider in Java if you created an enum (analogous to an Orchestra code set) named MyEnum. You could declare a variable String foo or MyEnum foo—your enum (code set) is a type, of equal standing with String.

While it's clear that Orchestra has different needs than a programming language in this regard, maybe we could benefit from looking at Orchestra's own type system a bit more formally in future discussions.