An XQuery Module For Simplifying Semantic Namespaces by Kurt Cagle.
From the post:
While I enjoy working with the MarkLogic 8 server, there are a number of features about the semantics library there that I still find a bit problematic. Declaring namespaces for semantics in particular is a pain—I normally have trouble remembering the namespaces for RDF or RDFS or OWL, even after working with them for several years, and once you start talking about namespaces that are specific to your own application domain, managing this list can get onerous pretty quickly.
I should point out however, that namespaces within semantics can be very useful in helping to organize and design an ontology, even a non-semantic ontology, and as such, my applications tend to be namespace rich. However, when working with Turtle, Sparql, RDFa, and other formats of namespaces, the need to incorporate these namespaces can be a real showstopper for any developer. Thus, like any good developer, I decided to automate my pain points and create a library that would allow me to simplify this process.
The code given here is in turtle and xquery, but I hope to build out similar libraries for use in JavaScript shortly. When I do, I’ll update this article to reflect those changes.
…
If you are forced to use a MarkLogic 8 server, great post on managing semantic namespaces.
If you have a choice of tools, something to consider before you willingly choose to use a MarkLogic 8 server.
I first saw this in a tweet by XQuery.
is your objection to Marklogic that it is commercial, or something else? Genuinely curious.
Comment by miklo — December 24, 2015 @ 4:40 pm
No objection to MarkLogic because it is commercial. I charge commercial vendors for standards writing/editing and they can hardly pay for that unless they are making money.
No, my objection to MarkLogic is two-fold.
First, for any newly announced database paradigm, MarkLogic resounds with “Me Too! And I was first!” Ahem, that’s one way to see it. (Not that I credit claims of new database paradigms, graphs for instance.)
Second, and I apologize for not having a ready example, MarkLogic has over the years created system specific calls which make replicating a MarkLogic XML database elsewhere overly difficult. Think of it as taking an open standard, XML, and creating a vendor wall around it.
I’m sure you can cite other vendors who have done the same thing but the subject of this post was a routine written for MarkLogic.
Hope you are having a Merry Christmas!
Patrick
Comment by Patrick Durusau — December 24, 2015 @ 8:01 pm