Good ideas, Geert. That's helpful. You mentioned avoiding the http protocol format for module URIs. I would think that it might be a good idea to use that format for module URIs if there's any chance in the module being used elsewhere (for example, if you plan to open-source some part of your work). Otherwise, I was thinking along the same general lines.
Karl On Thu, Jan 28, 2010 at 10:53 AM, Geert Josten <[email protected]> wrote: > Hi Karl, > >> I'd like to ask the group two specific questions about this topic: >> (1) Do you use internal naming conventions for MarkLogic URIs >> at your organization? If so, how's it working out? > > I personally adopted some simple rules with respect to uri's in MarkLogic > Server. For documents I tend to add a prefix to all paths, something like > '/{department}/{project}/docs/'. For modules I tend to add > '/{department}/{project}/modules/'. (Note that I don't use http protocol in > these uri's.) For collections I usually use something like > 'http://{organisation}.{countrycode}/{department}/{project}/{documentclassification}' > or sometimes something like > 'http://{organisation}.{countrycode}/marklogic/{documentclassification}'. > >> (2) Do you see value in having such conventions (realize that >> I'm not suggesting hard-and-fast rules, just naming >> guidelines. Deviations from the conventions would be fine as >> long as they are justified.)? > > It is possible to put documents and modules in the same database, so I would > prefer to be able to distiguish between the two on basis of uri only. With > collections you can't really get conflicts, but you could add the word > 'collection' in between somewhere, just for the sake of completeness if you > like. I am not very rigid about this, the uri's tend to get rather long when > you persist on always using such patterns. > > Moreover, I started out putting lot's of different projects together in the > default databases of MarkLogic Server, but came to the conclusion that you > often want to customize the configuration for a particular project which then > interferes with the other projects. Think about Triggers on documents, > Triggers on modules, CPF with conversion option or not, or no CPF at all, > various kinds of indexes that may or may not apply, word index tweaking, > etc.. Nowadays I mostly tend to creating dedicated databases and app servers > for each project. I have some scripts that help me with deployment.. > > When talking about naming conventions, you might also want to take into > account the naming of App Servers, Databases, Forests, Roles, Permissions, > etc. With regard to these I take the naming conversions of Mark Logic into > consideration, I personally like names that look more or less similar to the > already present ones, but I do prefer always appending 'Database' to Database > names for instance, contrary to Mark Logic... > > A few of my thoughts from the top of my head.. > > Kind regards, > Geert > > > > Drs. G.P.H. Josten > Consultant > > > http://www.daidalos.nl/ > Daidalos BV > Source of Innovation > Hoekeindsehof 1-4 > 2665 JZ Bleiswijk > Tel.: +31 (0) 10 850 1200 > Fax: +31 (0) 10 850 1199 > http://www.daidalos.nl/ > KvK 27164984 > De informatie - verzonden in of met dit emailbericht - is afkomstig van > Daidalos BV en is uitsluitend bestemd voor de geadresseerde. Indien u dit > bericht onbedoeld hebt ontvangen, verzoeken wij u het te verwijderen. Aan dit > bericht kunnen geen rechten worden ontleend. > > > > _______________________________________________ > General mailing list > [email protected] > http://xqzone.com/mailman/listinfo/general > _______________________________________________ General mailing list [email protected] http://xqzone.com/mailman/listinfo/general
