Hi Tim,
Well, the Element/Attribute index creation pages are pretty explicit that they want a namespace uri and a localname, in separate fields. So, no, I guess you won’t benefit from Path Namespaces there. I don’t think you will benefit from those Path namespace declarations from within XQuery code either, actually. You can provide those at Group and Appserver level under Namespaces. I could be wrong, but to my knowledge those Path Namespaces are only to declare prefixes you use in XPath expressions for Path indexes.. Kind regards, Geert *Van:* [email protected] [mailto: [email protected]] *Namens *Timothy W. Cook *Verzon**den:* donderdag 12 december 2013 14:47 *Aan:* MarkLogic Developer Discussion *Onderwerp:* [MarkLogic Dev General] Namespace URIs in admin UI If I define a Namespace for a database under Path Namespaces: prefix: mlhim243 namespace uri: http://www.mlhim.org/xmlns/mlhim2/2_4_3 Should I / may I, use the prefix when when defining Element Range Indexes and other things in the admin UI? The help for Path Namespaces only talks about XQueries: *Namespaces** specifies a set of global prefix to URI XML namespace mappings. Web applications can freely use the configured prefixes without the need for defining the namespace prefix in the XQuery prolog.* Basically I am asking if I can just use the prefix mlhim243 anywhere I am addressing this database or do I still need the entire uri in some places? Thanks, Tim -- MLHIM VIP Signup: http://goo.gl/22B0U ============================================ Timothy Cook, MSc +55 21 94711995 MLHIM http://www.mlhim.org Like Us on FB: https://www.facebook.com/mlhim2 Circle us on G+: http://goo.gl/44EV5 Google Scholar: http://goo.gl/MMZ1o LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook
_______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
