Hi, Florent: Point well taken that it's an issue with document serialization.
I don't, however, think the serialization issue can be solved at the HTTP level because a service can return multiple documents (via multipart/mixed), each of which might need to declare a different document type. Erik Hennum ________________________________________ From: [email protected] [[email protected]] On Behalf Of Florent Georges [[email protected]] Sent: Friday, November 16, 2012 8:58 AM To: MarkLogic Developer Discussion Subject: Re: [MarkLogic Dev General] REST API doctype extension Erik Hennum wrote: Hi, > I checked the XQuery 3.0 recommendation > http://www.w3.org/TR/xquery-30/#id-documentConstructors > but didn't find anything about document type expressions. Well, this is not related to constructing XDM document nodes, as those do not keep that property, but is related to their serialization. And XQuery 3.0 defines how to set serialization parameters for a query: http://www.w3.org/TR/xquery-30/#id-serialization IMHO, an implementation allowing to return an HTTP response to a client should always provide the user to specifiy his/her own serialization parameters (even on a per-HTTP-part basis in case of multipart), even if it provides some intuitive and cover-most- cases defaults. I don't know the details of the REST API, but if it returns the result of the query as the entity content of the HTTP response, and if MarkLogic 6 supports the serialization parameters, then it is worth giving them a try... Regards, -- Florent Georges http://fgeorges.org/ http://h2oconsulting.be/ _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
