uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marshall Schor <...@schor.com>
Subject Re: Website welcome should include the first few paragraphs of our revised proposal to the Incubator
Date Fri, 03 Nov 2006 18:51:49 GMT
+1.  Please update.  Here's how:

Edit the file in uimaj-website in the xdoc directory where the page is 
(probably index.xml).
Write in XHTML (matching closing tags, all tags lower case, and all 
attributes followed by
an equal sign and a quoted string).

When Jira is up, we should probably tag all changes to a Jira issue.


Adam Lally wrote:
> It seems to me that our initial website is making the same mistakes
> that our initial Incubator proposal did.  It leads with the mention of
> the OASIS standard, which doesn't mean anything to readers and may
> cause them to stop reading at that point thinking this is too
> confusing.
> I'd like to see this paragraph from our proposal, before any mention 
> of OASIS:
> Unstructured Information Management applications are software systems
> that analyze large volumes of unstructured information in order to
> discover knowledge that is relevant to an end user. UIMA is a
> framework and SDK for developing such applications. An example UIM
> application might ingest plain text and identify entities, such as
> persons, places, organizations; or relations, such as works-for or
> located-at. UIMA enables such an application to be decomposed into
> components, for example "language identification" -> "language
> specific segmentation" -> "sentence boundary detection" -> "entity
> detection (person/place names etc.)". Each component must implement
> interfaces defined by the framework and must provide self-describing
> metadata via XML descriptor files. The framework manages these
> components and the data flow between them. Components are written in
> Java or C++; the data that flows between components is designed for
> efficient mapping between these languages. UIMA additionally provides
> capabilities to wrap components as network services, and can scale to
> very large volumes by replicating processing pipelines over a cluster
> of networked nodes.
> -Adam

View raw message