Another Word For It Patrick Durusau on Topic Maps and Semantic Diversity

May 20, 2014

<oXygen/> XML Editor 16.0

Filed under: Editor,XML — Patrick Durusau @ 12:51 pm

<oXygen/> XML Editor 16.0

From the post:

<oXygen/> XML Editor 16 increases your productivity for XSLT development with the addition of Quick Fixes and improvements to refactoring actions. Saxon-CE specific extensions are supported and you can apply now XPath queries on multiple files.

If you use Ant to orchestrate build processes then <oXygen/> will support you with a powerful Ant editor featuring validation, content completion, outline view, syntax highlight and search and refactoring actions.

Working with conditional content is a lot easier now as you can set different colors and styles for each condition or focus exclusively on a specific deliverable by hiding all excluded content. You can modify DITA and DocBook tables easily using the new table properties action.

You can customize the style of the <oXygen/> WebHelp output to look exactly as you want using the new WebHelp skin builder.

As usual, the new version includes many component updates and new API functionality.
….

Too many changes and new features to list!

Not cheap and has a learning curve but if you are looking for a top end XML editor, you need look no further.

April 11, 2014

Hemingway App

Filed under: Authoring Topic Maps,Editor,Writing — Patrick Durusau @ 7:10 pm

Hemingway App

We are a long way from something equivalent to Hemingway App for topic maps or other semantic technologies but it struck me that may not always be true.

Take it for a spin and see what you think.

What modifications would be necessary to make this concept work for a semantic technology?

February 26, 2014

Atom

Filed under: Editor,Texts — Patrick Durusau @ 8:13 pm

Atom: A hackable text editor for the 21st Century.

From the webpage:

At GitHub, we’re building the text editor we’ve always wanted. A tool you can customize to do anything, but also use productively on the first day without ever touching a config file. Atom is modern, approachable, and hackable to the core. We can’t wait to see what you build with it.

I can’t imagine anyone improving on Emacs but we might learn something from watching people try. 😉

Some other links of interest:

Support: atom@github.com

Twitter: @AtomEditor

Chat: http://webchat.freenode.net/?channels=##atom

Discuss: http://discuss.atom.io/

Enjoy!

December 31, 2013

Tips on Long Term Emacs Productivity

Filed under: Editor — Patrick Durusau @ 4:19 pm

Tips on Long Term Emacs Productivity by Xah Lee.

There are seven (7) tips:

  1. Everything is a Command
  2. Master Window Splitting
  3. Master Dired
  4. Master Buffer Switching
  5. Remap Most Frequently Used Keys
  6. Master Find/Replace and Emacs Regex
  7. Get A Good Keyboard

The post on drawing suggested warmup exercises. Might not be a bad idea for Emacs as well.

August 17, 2013

AT4AM: The XML Web Editor Used By…

Filed under: Editor,EU,Semantics — Patrick Durusau @ 4:27 pm

AT4AM: The XML Web Editor Used By Members Of European Parliment

From the post:

AT4AM – Authoring Tool for Amendments – is a web editor provided to Members of European Parliament (MEPs) that has greatly improved the drafting of amendments at European Parliament since its introduction in 2010.

The tool, developed by the Directorate for Innovation and Technological Support of European Parliament (DG ITEC) has replaced a system based on a collection of macros developed in MS Word and specific ad hoc templates.

Moving beyond guessing the semantics of an author depends upon those semantics being documented at the point of creation.

Having said that, I think we all acknowledge that for the average user, RDF and its kin, were DOA.

Interfaces such as AT4AM, if they can be extended to capture the semantics of their authors, would be a step in the right direction.

BTW, see the AT4AM homepage, complete with live demo.

July 16, 2013

A Guide to Documentary Editing

Filed under: Editor,Texts — Patrick Durusau @ 9:59 am

A Guide to Documentary Editing by Mary-Jo Kline and Susan Holbrook Perdue.

From the introduction:

Don’t be embarrassed if you aren’t quite sure what we mean by “documentary editing.” When the first edition of this Guide appeared in 1987, the author found that her local bookstore on the Upper West Side of Manhattan had shelved a copy in the “Movies and Film” section. When she pointed out the error and explained what the book was about, the store manager asked perplexedly, “Where the heck should we shelve it?”

Thus we offer no apologies for providing a brief introduction that explains what documentary editing is and how it came to be.

If this scholarly specialty had appeared overnight in the last decade, we could spare our readers the “history” as well as the definition of documentary editing. Unfortunately, this lively and productive area of scholarly endeavor evolved over more than a half century, and it would be difficult for a newcomer to understand many of the books and articles to which we’ll refer without some understanding of the intellectual debates and technological innovations that generated these discussions. We hope that our readers will find a brief account of these developments entertaining as well as instructive.

We also owe our readers a warning about a peculiar trait of documentary editors that creates a special challenge for students of the craft: practitioners have typically neglected to furnish the public with careful expositions of the principles and practices by which they pursue their goals. Indeed, it was editors’ failure to write about editing that made the first edition of this Guide necessary in the 1980s. It’s hard to overemphasize the impact of modern American scholarly editing in the third quarter of the twentieth century: volumes of novels, letters, diaries, statesmen’s papers, political pamphlets, and philosophical and scientific treatises were published in editions that claimed to be scholarly, with texts established and verified according to the standards of the academic community. Yet the field of scholarly editing grew so quickly that many of its principles were left implicit in the texts or annotation of the volumes themselves.

(…)

Even for materials under revision control, explicit principles of documentary editing will someday play a role in future editions of those texts. In part because texts do not stand alone, apart from social context.

Abbie Hoffman‘s introduction to Steal This Book:

We cannot survive without learning to fight and that is the lesson in the second section. FIGHT! separates revolutionaries from outlaws. The purpose of part two is not to fuck the system, but destroy it. The weapons are carefully chosen. They are “home-made,” in that they are designed for use in our unique electronic jungle. Here the uptown reviewer will find ample proof of our “violent” nature. But again, the dictionary of law fails us. Murder in a uniform is heroic, in a costume it is a crime. False advertisements win awards, forgers end up in jail. Inflated prices guarantee large profits while shoplifters are punished. Politicians conspire to create police riots and the victims are convicted in the courts. Students are gunned down and then indicted by suburban grand juries as the trouble-makers. A modern, highly mechanized army travels 9,000 miles to commit genocide against a small nation of great vision and then accuses its people of aggression. Slumlords allow rats to maim children and then complain of violence in the streets. Everything is topsy-turvy. If we internalize the language and imagery of the pigs, we will forever be fucked. Let me illustrate the point. Amerika was built on the slaughter of a people. That is its history. For years we watched movie after movie that demonstrated the white man’s benevolence. Jimmy Stewart, the epitome of fairness, puts his arm around Cochise and tells how the Indians and the whites can live in peace if only both sides will be reasonable, responsible and rational (the three R’s imperialists always teach the “natives”). “You will find good grazing land on the other side of the mountain,” drawls the public relations man. “Take your people and go in peace.” Cochise as well as millions of youngsters in the balcony of learning, were being dealt off the bottom of the deck. The Indians should have offed Jimmy Stewart in every picture and we should have cheered ourselves hoarse. Until we understand the nature of institutional violence and how it manipulates values and mores to maintain the power of the few, we will forever be imprisoned in the caves of ignorance. When we conclude that bank robbers rather than bankers should be the trustees of the universities, then we begin to think clearly. When we see the Army Mathematics Research and Development Center and the Bank of Amerika as cesspools of violence, filling the minds of our young with hatred, turning one against another, then we begin to think revolutionary.

Be clever using section two; clever as a snake. Dig the spirit of the struggle. Don’t get hung up on a sacrifice trip. Revolution is not about suicide, it is about life. With your fingers probe the holiness of your body and see that it was meant to live. Your body is just one in a mass of cuddly humanity. Become an internationalist and learn to respect all life. Make war on machines, and in particular the sterile machines of corporate death and the robots that guard them. The duty of a revolutionary is to make love and that means staying alive and free. That doesn’t allow for cop-outs. Smoking dope and hanging up Che’s picture is no more a commitment than drinking milk and collecting postage stamps. A revolution in consciousness is an empty high without a revolution in the distribution of power. We are not interested in the greening of Amerika except for the grass that will cover its grave.

would require a lot of annotation to explain to an audience that meekly submits to public gropings in airport security lines, widespread government surveillance and wars that benefit only contractors.

Both the Guide to Documentary Editing and Steal This Book are highly recommended.

July 2, 2013

Running Python and R inside Emacs

Filed under: Editor,Programming,Python,R — Patrick Durusau @ 2:45 pm

Running Python and R inside Emacs by John D. Cook.

From the post:

Emacs org-mode lets you manage blocks of source code inside a text file. You can execute these blocks and have the output display in your text file. Or you could export the file, say to HTML or PDF, and show the code and/or the results of executing the code.

Here I’ll show some of the most basic possibilities. For much more information, see orgmode.org. And for the use of org-mode in research, see A Multi-Language Computing Environment for Literate Programming and Reproducible Research.

Not recent (2012) but looks quite interesting.

Well, you have to already like Emacs! 😉

Follow John’s post for basic usage and if you like it, checkout orgmode.org.

June 30, 2013

Log as a Service (Part 1 of 2)

Filed under: Collaboration,Editor,Topic Map Software — Patrick Durusau @ 6:04 pm

Log as a Service (Part 1 of 2) by Oliver Kennedy.

From the post:

Last week I introduced some of the hype behind our new project: Laasie. This week, let me delve into some of the technical details. Although for simplicity, I’ll be using the present tense, please keep in mind that what I’m about to describe is work in progress. We’re hard at work implementing these, and will release when-it’s-ready (tm blizzard entertainment).

So, let’s get to it. There are two state abstractions in Laasie: state land, and log land. I’ll address each of these independently.

See: Laasie: Building the next generation of collaborative applications.

I am partially interested in Laasie because of work that is ongoing to enable ODF markup to support collaborative editing (a special case of change tracking).

I am also interested because authoring topic maps should be a social enterprise, which implies collaborative editing.

Finally, in hopes that collaborative editing will fade the metaphor of a physical document. A “document” will be what we have requested to be displayed at a point in time, populated by particular components and content.

I remain deeply interested in physical texts and their traditions, including transmission.

However, they should not be confused with their simulacra that we make manifest with our computers.

June 24, 2013

Laasie: Building the next generation of collaborative applications

Filed under: Collaboration,Editor,Topic Map Software — Patrick Durusau @ 1:17 pm

Laasie: Building the next generation of collaborative applications by Oliver Kennedy.

From the post:

With the first Laasie paper (ever) being presented tomorrow at WebDB (part of SIGMOD), I thought it might be a good idea to explain the hubbub. What is Laasie?

The short version is that it’s an incremental state replication and persistence infrastructure, targeted mostly at web applications. In particular, we’re focusing on a class of collaborative applications, where multiple users interact with the same application state simultaneously. A commonly known instance of such applications is the Google Docs office suite. Multiple users viewing the same document can simultaneously both view and edit the document.

Do your topic maps collaborate with other topic maps?

June 1, 2013

An introduction to Emacs Lisp

Filed under: Authoring Topic Maps,Editor,Lisp — Patrick Durusau @ 10:30 am

An introduction to Emacs Lisp by Christian Johansen.

From the webpage:

As a long-time passionate Emacs user, I’ve been curious about Lisp in general and Emacs Lisp in particular for quite some time. Until recently I had not written any Lisp apart from my .emacs.d setup, despite having read both An introduction to programming in Emacs Lisp and The Little Schemer last summer. A year later, I have finally written some Lisp, and I thought I’d share the code as an introduction to others out there curious about Lisp and extending Emacs.

(…)

The Task

The task I set out to solve was to make Emacs slightly more intelligent when working with tests written in Buster.JS, which is a test framework for JavaScript I’m working on with August Lilleaas. In particular I wanted Emacs to help me with Buster’s concept of deferred tests.

Yesterday a graph programmer suggested to me some people program in Lisp and but the whole world uses Java.

Of course, most of the world is functionally illiterate too but I don’t take that as an argument for illiteracy.

Not to cast aspersions on Java, a great deal of excellent work is done in Java. (See the many Apache projects that use Java.)

But counting noses is a lemming measure, which is not related the pros or cons of any particular language.

What topic map authoring tasks would you extend Emacs to facilitate?

I first saw this in Christophe Lalanne’s A bag of tweets / May 2013.

May 21, 2013

JSME: a free molecule editor in JavaScript

Filed under: Cheminformatics,Editor,Interface Research/Design,Javascript — Patrick Durusau @ 4:48 pm

JSME: a free molecule editor in JavaScript by Bruno Bienfait and Peter Ertl. (Journal of Cheminformatics 2013, 5:24 doi:10.1186/1758-2946-5-24)

Abstract:

Background

A molecule editor, i.e. a program facilitating graphical input and interactive editing of molecules, is an indispensable part of every cheminformatics or molecular processing system. Today, when a web browser has become the universal scientific user interface, a tool to edit molecules directly within the web browser is essential. One of the most popular tools for molecular structure input on the web is the JME applet. Since its release nearly 15 years ago, however the web environment has changed and Java applets are facing increasing implementation hurdles due to their maintenance and support requirements, as well as security issues. This prompted us to update the JME editor and port it to a modern Internet programming language – JavaScript.

Summary

The actual molecule editing Java code of the JME editor was translated into JavaScript with help of the Google Web Toolkit compiler and a custom library that emulates a subset of the GUI features of the Java runtime environment. In this process, the editor was enhanced by additional functionalities including a substituent menu, copy/paste, drag and drop and undo/redo capabilities and an integrated help. In addition to desktop computers, the editor supports molecule editing on touch devices, including iPhone, iPad and Android phones and tablets. In analogy to JME the new editor is named JSME. This new molecule editor is compact, easy to use and easy to incorporate into web pages.

Conclusions

A free molecule editor written in JavaScript was developed and is released under the terms of permissive BSD license. The editor is compatible with JME, has practically the same user interface as well as the web application programming interface. The JSME editor is available for download from the project web page http://peter-ertl.com/jsme/

Just in case you were having any doubts about using JavaScript to power an annotation editor.

Better now?

December 21, 2012

BaseX. The XML Database. [XPath/XQuery]

Filed under: Editor,XML,XQuery — Patrick Durusau @ 11:08 am

BaseX. The XML Database.

From the webpage:

News: BaseX 7.5 has just been released…

BaseX is a very light-weight, high-performance and scalable XML Database engine and XPath/XQuery 3.0 Processor, including full support for the W3C Update and Full Text extensions. An interactive and user-friendly GUI frontend gives you great insight into your XML documents.

Another XML editor but I mention it for its support of XQuery more than as an editor per se.

We continue to lack a standard query language for topic maps and experience with XQuery may prove informative.

Not to mention its possible role in gathering diverse data for presentation in a merged state to users.

<ANGLES>

Filed under: Editor,Software,XML — Patrick Durusau @ 10:33 am

<ANGLES>

From the homepage:

ANGLES is a research project aimed at developing a lightweight, online XML editor tuned to the needs of the scholarly text encoding community. By combining the model of intensive code development (the “code sprint”) with participatory design exercises, testing, and feedback from domain experts gathered at disciplinary conferences, ANGLES will contribute not only a working prototype of a new software tool but also another model for tool building in the digital humanities (the “community roadshow”).

Work on ANGLES began in November 2012.

We’ll have something to share very soon!

<ANGLES> is an extension of ACE:

ACE is an embeddable code editor written in JavaScript. It matches the features and performance of native editors such as Sublime, Vim and TextMate. It can be easily embedded in any web page and JavaScript application. ACE is maintained as the primary editor for Cloud9 IDE and is the successor of the Mozilla Skywriter (Bespin) project.

<ANGLES> code at Sourceforge.

I will be interested to see how ACE is extended. Just glancing at it this morning, it appears to be the traditional “display angle bang syntax” editor we all know so well.

What puzzles me is that we have been to the mountain of teaching users to be comfortable with raw XML markup and the results have not been promising.

As opposed to the experience with OpenOffice, MS Office, etc., which have proven that creating documents that are then expressed in XML, is within the range of ordinary users.

<ANGLES> looks like an interesting project but whether it brings XML editing within the reach of ordinary users is an open question.

If the XML editing puzzle is solved, perhaps it will have lessons for topic map editors.

December 16, 2012

Collaborating, Online with LaTeX?

Filed under: Authoring Topic Maps,Collaboration,Editor — Patrick Durusau @ 6:17 am

I saw a tweet tonight that mentioned two online collaborative editors based on LaTeX:

writeLaTeX

and,

ShareLaTeX

I don’t have the time to look closely at them tonight but thought you would find them interesting.

If collaborative editing is possible for LaTeX, shouldn’t that also be possible for a topic map?

I saw this mentioned in a tweet by Jan-Piet Mens

November 10, 2012

Behind the Mirror

Filed under: Clojure,Editor — Patrick Durusau @ 4:39 pm

Behind the Mirror by Chris Granger.

Summary:

Chris Granger discusses the need for enhancing the learning tools starting from his own experience watching through a mirror people trying to solve problems at Microsoft.

A compelling presentation about principles for IDEs via TECO, through Visual Studio and ending up with Clojure.

Chris argues we should be able to hide, foreground and manipulate abstractions as part of an IDE.

I see potential for interactive topic map authoring where the state of the map only a round trip to the server behind the user.

October 7, 2012

Emacs Rocks!

Filed under: Editor — Patrick Durusau @ 7:23 pm

Emacs Rocks!

A series of very short (first one I saw was 1 minute, 54 seconds) screen casts of using Emacs.

A communication model to be emulated!

I first saw this at Christophe Lalanne’s A bag of tweets / September 2012

June 6, 2012

A Pluggable XML Editor

Filed under: Editor,XML — Patrick Durusau @ 7:50 pm

A Pluggable XML Editor by Grant Vergottini.

From the post:

Ever since I announced my HTML5-based XML editor, I’ve been getting all sorts of requests for a variety of implementations. While the focus has been, and continues to be, providing an Akoma Ntoso based legislative editor, I’ve realized that the interest in a web-based XML editor extends well beyond Akoma Ntoso and even legislative editors.

So… with that in mind I’ve started making some serious architectural changes to the base editor. From the get-go, my intent had been for the editor to be “pluggable” although I hadn’t totally thought it through. By “pluggable” I mean capable of allowing different information models to be used. I’m actually taking the model a bit further to allow modules to be built that can provide optional functionality to the base editor. What this means is that if you have a different document information model, and it is capable of being round-tripped in some way with an editing view, then I can probably adapt it to the editor.

Let’s talk about the round-tripping problem for a moment. In the other XML editors I have worked with, the XML model has had to quite closely match the editing view that one works with. So you’re literally authoring the document using that information model. Think about HTML (or XHTML for an XML perspective). The arrangement of the tags pretty much exactly represents how you think of an deal with the components of the document. Paragraphs, headings, tables, images, etc, are all pretty much laid out how you would author them. This is the ideal situation as it makes building the editor quite straight-forward.

Note the line:

What this means is that if you have a different document information model, and it is capable of being round-tripped in some way with an editing view, then I can probably adapt it to the editor.

I think that means that we don’t all have to use the same editing view and at the same time, we can share an underlying format. Or perhaps even annotate texts with subject identities, not even realizing we are helping others.

This is an impressive bit of work and as the post promises, there is more to follow.

(I first saw this at Legal Informatics. http://legalinformatics.wordpress.com/2012/06/05/vergottini-on-improvements-to-akneditor-html-5-based-xml-editor-for-legislation/)

May 5, 2012

Building a Web-Based Legislative Editor

Filed under: Editor,Law — Patrick Durusau @ 6:56 pm

Building a Web-Based Legislative Editor by Grant Vergottini.

From the post:

I built the legislative drafting tool used by the Office of the Legislative Counsel in California. It was a long and arduous process and took several years to complete. Issues like redlining, page & line numbers, and the complexities of tables really turned an effort that, while looking quite simple at the surface, into a very difficult task. We used XMetaL as the base tool and customized it from there, developing what has to be the most sophisticated implementation of XMetaL out there. We even had to have a special API added to XMetaL to allow us to drive the change tracking mechanism to support the very specialized redlining needs one finds in legislation.

…With HTML5, it is now possible to build a full fledged browser-based legislative editor. For the past few months I have been building a prototype legislative editor in HTML5 that uses Akoma Ntoso as its XML schema. The results have been most gratifying. Certainly, building such an editor is no easy task. Having been working in this subject for 10 years now I have all the issues well internalized and can navigate the difficulties that arise. But I have come a long way towards achieving the holy grail of legislative editors – a web-based, standards-based, browser-neutral solution.

Not even out in beta, yet, but a promising report from someone who knows the ends and outs of legislation editors.

Why is that relevant for topic maps?

A web-based editor could, not necessarily will, lead to custom editors that are configured for work flows in the production of topic map work products.

If you think about it, we interact with work flows based on our recognition of subjects and taking actions based on the subjects we recognize.

Not a big step for software to record which subjects we have recognized, while our machinery silently adds identifiers, updates indexes of associations and performs other tasks.

PS: I originally saw this mentioned at the Legal Informatics blog.

« Newer Posts

Powered by WordPress