summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndreas Stöckel <astoecke@techfak.uni-bielefeld.de>2015-04-22 23:05:50 +0200
committerAndreas Stöckel <astoecke@techfak.uni-bielefeld.de>2015-04-22 23:05:50 +0200
commit2366c2098734ffbfe710fc0cb33fcfc90ec4479e (patch)
tree457b71506db9642a62d161d13659307b3dd59925
parentd972594a61e1b4b9833b687e599d4568c7138d78 (diff)
applied patch supplied by Daniel Stöckel: Some grammatical and stylistical improvements
-rw-r--r--index.osml10
1 files changed, 5 insertions, 5 deletions
diff --git a/index.osml b/index.osml
index 549f749..12eb66e 100644
--- a/index.osml
+++ b/index.osml
@@ -58,14 +58,14 @@ development. Features include:
\section{About}
-Ousía Framework aims at coupling Semantic Web techniques with structured data.
+The Ousía Framework aims at coupling Semantic Web techniques with structured data.
This is not only of interest to the research community but to the end user as
well, due to:
\dl{
\item{Re-usability}
Allow to reuse of content, concepts and styles across documents
- \item{Separation of Presentation and Content}
+ \item{Separation of presentation and content}
Layout is indepentend of the document, allowing authors to focus on content
rather than form.
@@ -95,8 +95,8 @@ order, highly incomplete and subject to change):
\item{JavaScript API}
Internally we already maintain method and property information about
“managed” objects in the document graph. Additionally, a prototype binding
- to MozJs already exists. Time to stick the two together and – in a first
- step – allowing user defined parsing and validation functions for
+ to MozJs already exists. Time to stick the two together and – as a first
+ step – allow user defined parsing and validation functions for
structures. This can e.g. be used to parse and verify E-Mail addresses, BICs
or IBANs.
@@ -106,7 +106,7 @@ order, highly incomplete and subject to change):
publish the current version on this Website.
\item{Output transformation}
- Implement the output transformation pipeline. This goal is as of now
+ Implement the output transformation pipeline. This goal is, as of now,
somewhat fuzzy, but the goals are to have an API that allows partial
template matching as in XSLT to allow online updating of the output,
chaining of transformations and both a C++ and JavaScript API.