Hello Adam Thanks for the feedback. A CodeListFactory could be an option (especially for new items defined by authorities other than OGC/ISO). But the current issue is more about using Enum/CodeList than creating them. They share many common methods: name(), ordinal(), etc. If we could insert a common parent class, what would be the name of that class? Enumerated, Inventory, Dictionary, Listing, Catalog, Universe (of discussion), I don't know...
Martin Le 20/11/14 23:38, Adam Estrada a écrit : > Martin, > > Why not make a CodeListFactory? > > Adam > > On Wed, Nov 19, 2014 at 12:58 PM, Martin Desruisseaux > <[email protected]> wrote: >> Hello all >> >> As a side effect of ISO 19115:2014 upgrade, we have an increasing need >> for a common interface between CodeList and the Enum defined by GeoAPI. >> (Reminder: a CodeList is basically an Enum which allow new elements to >> be added at runtime). I have trouble finding a good interface name which >> can be applied to both "true enum" and "extensible enum" (i.e. "code >> list"). We can not use "Enum", "Enumeration" or "CodeList" since they >> are already used. I found "Enumerated" used in some other API (e.g. >> javax.persistence.Enumerated) so I took that name for now: >> >> http://www.geoapi.org/snapshot/javadoc/org/opengis/util/Enumerated.html >> >> However I don't think it is a good name for us, since "enumeration" >> suggest a closed universe (we enumerated all possible elements), while >> "code list" is an open universe. >> >> I though about "Universe", but this is probably too big. Some other >> words are "catalog", "inventory", "register", "dictionary", "listing", >> and more. Does someone has an idea for a better interface name? >> >> Martin >>
