Group items tagged

"HDF (Hierarchical Data Format) technologies are relevant when the data challenges being faced push the limits of what can be addressed by traditional database systems, XML documents, or in-house data formats. Leveraging the powerful HDF products and the expertise of The HDF Group, organizations realize substantial cost savings while solving challenges that seemed intractable using other data management technologies. Many HDF adopters have very large datasets, very fast access requirements, or very complex datasets. Others turn to HDF because it allows them to easily share data across a wide variety of computational platforms using applications written in different programming languages. Some use HDF to take advantage of the many open-source and commercial tools that understand HDF. Similar to XML documents, HDF files are self-describing and allow users to specify complex data relationships and dependencies. In contrast to XML documents, HDF files can contain binary data (in many representations) and allow direct access to parts of the file without first parsing the entire contents. HDF, not surprisingly, allows hierarchical data objects to be expressed in a very natural manner, in contrast to the tables of relational database. Whereas relational databases support tables, HDF supports n-dimensional datasets and each element in the dataset may itself be a complex object. Relational databases offer excellent support for queries based on field matching, but are not well-suited for sequentially processing all records in the database or for subsetting the data based on coordinate-style lookup."

"In this paper we propose the TurboXPath path processor, which accepts a language equivalent to a subset of the for-let-where constructs of XQuery over a single document. TurboXPath can be extended to provide full XQuery support or used to augment federated database engines for efficient handling of queries over XML data streams produced by external sources. Internally, TurboXPath uses a tree-shaped path expression with multiple outputs to drive the execution. The result of a query execution is a sequence of tuples of XML fragments matching the output nodes. Based on a streamed execution model, TurboXPath scales up to large documents and has limited memory consumption for increased concurrency"

"Protostuff is the stuff that leverages google's protobuf. A serialization library with built-in support for forward-backward compatibility (schema evolution) and validation. available formats: protostuff (native) graph (protostuff with support for cyclic references. See SerializingObjectGraphs) protobuf json smile (binary json useable from the protostuff-json module) xml yaml (ser only) kvp (binary uwsgi header) support for messages that are generated by the protostuff-compiler (java_bean) cyclic references via graph format see CompilerOptions for more customized compilation of .proto files support for existing pojos (See runtime schemas) cyclic references via graph format polymorphic (a nested message can be an interface/abstract class or even java.lang.Object) support for existing protoc-generated java messages see the io instructions for json, xml, yaml) no support for cyclic references (limitation of the builder pattern) Interoperability across various mobile platforms android kindle j2me (protostuff-me module) Transcoding support converts one encoding to another. See PipeUsage. Source and Sink protostuff, protobuf, json, json-numeric, smile, smile-numeric, xml Sink only yaml "

Nux is an open-source Java toolkit making efficient and powerful XML processing easy. It is geared towards embedded use in high-throughput XML messaging middleware such as large-scale Peer-to-Peer infrastructures, message queues, publish-subscribe and matchmaking systems for Blogs/newsfeeds, text chat, data acquisition and distribution systems, application level routers, firewalls, classifiers, etc.

XML Binding library for scala

Streaming path filter node factory for continuous queries and/or transformations over very large or infinitely long XML input.

"We present a novel streaming algorithm for evaluating XPath expressions that use backward axes (parent and ancestor) and forward axes in a single document-order traversal of an XML document. Other streaming XPath processors, such as YFilter, XTrie, and TurboXPath handle only forward axes. We show through experiments that our algorithm significantly outperforms (by more than a factor of two) a traditional non-streaming XPath engine. Furthermore, since our algorithm only retains relevant portions of the input document in memory, it scales better than traditional XPath engines. It can process large documents; we have successfully tested documents over 1GB in size. On the other hand, the traditional XPath engine degrades considerably in performance for documents over 100 MB in size and fails to complete for documents of size over 200 MB."

"Our project (titled xstream)  concentrated on evaluation of XPath over XML streams. This research area contains multiple challenges resulting  from both the richness  of the language and the requirement of having only a single  pass over the data. We modified and extended one of the known algorithms, TurboXPath  [4], a tree-based IBM algorithm. We also  provide extensive comparative analysis between  TurboXPath and XSQ [5], currently the most advanced of  finite automata (FA)-based algorithms."

"XSQ evaluates XPath queries over streaming XML data. That is, it makes only pass over the data, in an order determined by the data source"

"ScalaTags is a small XML/HTML construction library for Scala. The core functionality of Scalatags is less than 200 lines of code, and yet it provides all the functionality of large frameworks like Python's Jinja2 or C#'s Razor. It does this by leveraging the functionality of the Scala language to do almost everything. A lot of different language constructs can be used to help keep your templates concise and DRY, and why re-invent them all yourself when you have someone else who has done it before you."

If you need to convert files from one markup format into another, pandoc is your swiss-army knife. Pandoc can convert documents in markdown, reStructuredText, textile, HTML, DocBook, or LaTeX to:  * HTML formats: XHTML, HTML5, and HTML slide shows using Slidy, Slideous, S5, or DZSlides.  * Word processor formats: Microsoft Word docx, OpenOffice/LibreOffice ODT, OpenDocument XML  * Ebooks: EPUB version 2 or 3, FictionBook2  * Documentation formats: DocBook, GNU TexInfo, Groff man pages  * TeX formats: LaTeX, ConTeXt, LaTeX Beamer slides  * PDF via LaTeX  * Lightweight markup formats: Markdown, reStructuredText, AsciiDoc, MediaWiki markup, Emacs Org-Mode, Textile

"Scala DSL on top of Oozie Workflow XML"

Hello everybody, I'm developing a custom authentication module. As part of the process I have to redirect the user to a second site and then the second site redirect the user back to the custom module. For this I'm using the RedirectCallback, but while debugging I noticed that the module gets initialized a second time after the users comes back from the second site. I was wondering if this is the expected behavior or if I'm doing something wrong. This is how the callbacks are defined in the xml.

"The Microsoft Build Engine is a platform for building applications. This engine, which is also known as MSBuild, provides an XML schema for a project file that controls how the build platform processes and builds software. Visual Studio uses MSBuild, but it doesn't depend on Visual Studio. By invoking msbuild.exe on your project or solution file, you can orchestrate and build products in environments where Visual Studio isn't installed."

La api mas copada que conozco para escribir clientes de HTTP... de verdad. Por ejemplo, consultar el servicio de info de Outbox para pedir el listado todos los archivos PDF, parsear el XML de respuesta, extraer del mismo los nombres de todos los archivos e imprimirlos puede ser tan solo así.