Remove org.genxdm.names.PrefixResolver

[GoogleCodeExporter]

The org.genxdm.names.PrefixResolver interface duplicates the functionality of 
org.genxdm.xs.resolve.PrefixResolver.  That's confusing; plus, it isn't used.

Eric suggested nuking the entire org.genxdm.names package.  Here's a quote from 
his email:

For the o.g.names package, I think we could get rid of it. The changes as 
follows:

    * NameSource: within the API JAR, it is used by both the AtomBridge & MetaBridge, so I would move it to the o.g.typed.types package.
    * NamespaceBinding: Only used within the API by Informer & NodeInformer, so move to the package o.g.nodes
    * NamespaceResolver: Only used by the MetaBridge in the API, so this could move to o.g.typed.types.
    * PrefixResolver: Nuke it - use the one in o.g.xs.resolve (although perhaps it should move to o.g.typed.types, because it is used by AtomBridge, and isn't specific to schema resolution.

Original issue reported on code.google.com by joe.bays...@gmail.com on 7 Apr 2011 at 8:50

[GoogleCodeExporter]

I would much, much, much rather see the schema-specific prefix resolver go 
away.  And I find myself violently antipathetic to a proposal that takes 
abstractions from one allegedly-miscellaneous (but in my opinion, name- and 
namespace-related) package and uses them to turn two other packages into 
miscellanies related only by call graph.

I'm tempted to mark this as a duplicate of 39, but these issues are not 
specifically called out in that issue.

Original comment by aale...@gmail.com on 7 Apr 2011 at 9:05

[GoogleCodeExporter]

actually, removed org.genxdm.xs.resolve.PrefixResolver.  Left the one in 
org.genxdm.names.  Makes more sense, since prefix resolution certainly isn't 
schema-specific (even if the only implementations are in the schema parser and 
validator).

Original comment by aale...@gmail.com on 29 Aug 2011 at 7:33

• Changed state: Fixed