Enterprise Mashup Markup Language

EMML, or Enterprise Mashup Markup Language, is an XML markup language for creating enterprise mashups, which are software applications that consume and mash data from variety of sources. These applications often perform logical or mathematical operations as well as present the data.

Mashed data produced by enterprise mashups are presented in graphical user interfaces as mashlets, widgets, or gadgets. EMML can also be ^[1] considered a declarative mashup domain-specific language (DSL). A mashup DSL eliminates the need for complex, time-consuming, and repeatable procedural programming logic to create enterprise mashups. EMML also provides a declarative language for creating visual tools for enterprise mashups.

The primary benefits of EMML are mashup design portability and interoperability of mashup solutions. These benefits are expected to accelerate the adoption of enterprise mashups by creating transferable skills for software developers and reducing vendor lock-in.

The introduction of EMML is expected to help accelerate the trend toward the integration of web-based applications and service-oriented architecture (SOA) technologies. ^[2] Bank of America was a high-profile early supporter of EMML. ^[3] Other prominent early supporters included Hewlett-Packard, Capgemini, Adobe Systems, and Intel. ^[4]

EMML history

Raj Krishnamurthy (chief architect at JackBe Corporation) and Deepak Alur (VP engineering at JackBe Corporation) started working on EMML in 2006. Their objective was to enable user-oriented and user-enabled mashups by creating what was then a new type of middleware called an Enterprise Mashup Platform. Raj Krishnamurthy became the chief language designer and implementer of EMML and also led the team to create an Eclipse-based EMML IDE called Mashup Studio. ^[5] This work evolved into the EMML reference implementation that was donated to the Open Mashup Alliance. Raj Krishnamurthy continues to be one of the key contributors to EMML through the Open Mashup Alliance.

EMML features

EMML language provides a rich set of high-level mashup-domain vocabulary to consume and mash a variety of web data-sources in flexible ways. EMML provides a uniform syntax to invoke heterogeneous service styles: REST, WSDL, RSS/ATOM, RDBMS, and POJO. The EMML language also provides the ability to mix diverse data formats: XML, JSON, JDBC, JavaObjects, and primitive types.

High-level EMML language features include:

• Filter and sort data coming from heterogeneous services.
• Join data across heterogeneous services and data formats.
• Group and aggregate data using assorted functions.
• Annotate original service data to enrich its semantic meaning.
• Merge multiple data streams into consolidated datasets
• Split datasets to select individual data fields.
• Embedded scripting support for JavaScript, JRuby, Groovy, XQuery
• Web clipping to scrape data from HTML pages.
• Conditional statements - If/Then/Else, While, ForEach
• Parallel syntax for concurrent processing

EMML is primarily an XML-based declarative language, but also provides the ability to encode complex logic using embedded scripting engines. XPath is the expression language used in EMML.

Directinvoke statement

directinvoke ^[6] provides ability to invoke and consume a variety of data services. These data services may be REST, RSS/ATOM, or SOAP services. directinvoke also supports Web clipping by allowing HTML pages to be specified as service endpoints. HTTP GET, POST, PUT, and DELETE protocols are supported in directinvoke. HTTP Header and cookie support is also available thus providing the capability to consume a wide variety of REST/SOAP Web services. It is possible to use directinvoke with a proxy server.

Code sample of passing attributes as parameters to a service:

<directinvokeendpoint="http://www.myCompany.com/rest-services/getItems"method="GET"outputvariable="$result"query="items=all"appID="67GYH30N25"/><directinvokeendpoint="http://www.svcsltd.com/getReservation"method="GET"outputvariable="$news"xmlns:sc="http://www.svcltd.com/"sc:date="20070515"sc:nights="3"/>

Filter statement

The filter ^[7] statement filters the content of a variable using an XPath expression and places the result in a new variable.

Code sample for filtering west-coast customers using region data-item:

<filterinputvariable="$queryResult"filterexpr="/customers[region='West']"outputvariable="$westCoastOnly"/>

Sort statement

The sort ^[8] statement sorts the content of a document-type variable or variable fragment based on key expressions and places the result in another variable.

Code sample that sorts tickets based on created date and customer:

<sortinputvariable="$troubleTickets"sortexpr="ticket"sortkeys="xs:date(created) descending, customer ascending"outputvariable="$troubleTickets"/>

Groupby statement

groupby ^[9] provides the ability to group and aggregate data sets. Standard XPath aggregation operations can be used and there is an extension mechanism for adding user-defined functions. Nested Grouping of hierarchical data sets are also supported. There is a Having clause to filter Group attributes.

Code sample that groups books by genre and computes total copies for each genre:

<groupby="$catalog//book/genre"outputvariable="$groupResult"><res:genrename="{$group_key}"copiessold="{sum(copiessold)}"/></group>

Merge statement

merge ^[10] provides ability to combine various data sources including RSS/ATOM feeds, XML, JSON payload formats. The merge feature is similar to SQL UNION functionality but merges hierarchical document structures.

Code sample that merges Yahoo! News, Financial News, and Reuters feeds:

<mergeinputvariables="$YahooRSS, $FinancialNewsRss, $ReutersRSS"outputvariable="$NewsAggregate"/>

Annotate statement

annotate ^[11] provides ability to enrich the semantic meaning of source service data with microformat-like elements/attributes. These data annotations can be used by mashlets or gadgets to provide richer visual user interfaces.

Code sample for annotating vendor payload with geo-coordinates:

<annotatevariable="$vendors"expr="/vendor/site"> elementgeo:lat{$georesult//y:Latitude/string()}, elementgeo:long{$georesult//y:Longitude/string()}</annotate>

Join statement

The join ^[12] statement defines how disparate, hierarchical data formats are joined and is comparable to inner joins for relational databases.

Code sample where output variable contains a <res:recommendations> element with a repeating set of <res:movie> children, which are the repeating items. Each <res:movie> contains a <res:movietitle> child with data from the variable named movies and <res:rating> and <res:comment> children with data from the variable named reviews:

<joinoutputvariable="$joinResult"joincondition="$movies/movie/@id = $reviews/review/movie/title"><selectname="res:recommendations"><res:movie><res:movietitle>{$movies/title}</res:movietitle><res:rating>{$reviews/rating}</res:rating><res:comment>{$reviews/comment}</res:comment></res:movie></select></join>

Scripting in EMML

EMML is a declarative language, but provides programmatic scripting ^[13] extensions for performing complex mashup logic. JavaScript, JRuby, Groovy, POJO, XQuery scripting environments are supported. Data flows seamlessly between EMML and scripting environments.

Code sample where JavaScript snippet is used to extract authentication token that is required for subsequent calls "result" variable that gets propagated to JavaScript environment:

<scripttype="text/javascript"><![CDATA[varr=newString(result)varar=r.split("=");auth=ar[ar.length-1];auth=auth.slice(0,-1)]]></script>

References

1. "Software AG". documentation.softwareag.com. Retrieved 2023-04-08.
2. "Where Is The Future of SOA Headed? Where The Web Goes". 17 November 2015.
3. "Why Bank of America Joined the Open Mashup Alliance". Archived from the original on 2009-10-01. Retrieved 2009-09-28.
4. "Enterprise mashup proponents start organizing". Archived from the original on 2009-10-03. Retrieved 2009-09-28.
5. "JackBe announces free enterprise mashup software". 17 November 2015.
6. "EMML Documentation Directinvoke chapter". Archived from the original on 2009-09-30. Retrieved 2009-10-11.
7. "EMML Documentation Filter chapter". Archived from the original on 2009-10-17. Retrieved 2009-10-11.
8. "EMML Documentation Sort chapter". Archived from the original on 2009-09-29. Retrieved 2009-10-11.
9. "EMML Documentation Groupby chapter". Archived from the original on 2009-09-29. Retrieved 2009-10-11.
10. "EMML Documentation Merge chapter". Archived from the original on 2009-09-29. Retrieved 2009-10-11.
11. "EMML Documentation Annotate chapter". Archived from the original on 2009-09-30. Retrieved 2009-10-11.
12. "EMML Documentation Join chapter". Archived from the original on 2009-09-29. Retrieved 2009-10-11.
13. "EMML Documentation Scripting chapter".{{cite web}}: Missing or empty |url= (help)