dedoc/paragraph_dataset huggingface dataset:
templates, that contains all multiple section templates, and
fragments, that are manual parts, legal paragraphs or tech-
nical product descriptions. The user can filter templates by
categories or search by name as well.
Note that templates can be included in both documents
and other templates. In fact, the right side of SSE constantly
shows the list of available templates and fragments in tem-
plate editor too. Nested templates can be easily created by the
authors and allow for the creation of composite documents.
After its inclusion in a document, a template keeps being
linked to the original template it comes from. SSE provides
users with an opt-in mechanism: when opening a document,
SSE checks all templates included in that document and
shows the list of the templates that have been modified.
The user can select which content to update and which not.
The user has always the opportunity to update a template
whenever he wants using a toolbar button.
Figure 2 shows template update notification and nested
The user can also use project metadata within templates by
selecting from the project properties list (e.i. name, client, ...).
The template author can see the property label and they will
be substituted by SSE with the values inside the document
editor. This can be useful if you consider that templates are
available on different projects.
Another important feature is that the user can lock sec-
tions or part of text so that the document author cannot
change that parts after including the template. For example
the user wants to insert legal notice that must not be changed
by the document author.
Figures 3 shows two metadata and a locked section inside
a template. Locked sections show a deny icon on the right
top corner and have an azure background. Metadata have a
blue background.
Figure 3: Some of the template features: locked sections and
An author can change all not-fixed sections and blocks
of a template, however if the user updates the template ev-
ery change will be lost. That is why ADF vocabulary also
contains variables. Block variables allow users to insert para-
graphs, sections, tables, etc. Figure 4 shows a template vari-
able inside the document editor.
Figure 4: A template variable (yellow block)
When the template is updated, the instantiated content
of a variable is not affected. An example is shown in Figure
5: the template is up-to-date (the last element of the list is
deleted) but the variable content is the same as before.
Figure 5: the template variable is not affected by template
SSE in written in Node.js and has a typical architecture based
on the MVC (Model View Controller) pattern. As expected,
the most important component is the JS front-end, while
the backend only manages documents storage and format
conversions.
The front-end is based on a customized version of 2 TinyMCE
a WYSIWYG HTML-based editor that can be instantiated
within an existing HTML page. TinyMCE is a large project
(more than 150 contributors) and includes modules for for-
matting, table insertion, image editing, customizable themes.
It is already integrated with frameworks such as JQuery and
Angular.js and highly customizable. This is the main rea-
son why we selected TinyMCE as core component of SSE.
The customization we put in place was mainly to ensure
consistency with our patterns theory.
Last but not least, SSE uses 3 PDX , a DOM extension for
managing the “behavior” of the documents. The term “behav-
ior” indicates how specific aspects of a document element
(style and/or content) are determined by the event happen-
ing to it or to related elements. Consider, for instance, the
frequent action of renumbering a section due to the inser-
tion/deletion of other sections, or numbering a reference
to a table or an image, or updating a template: all these dy-
namic behaviours are described in PDX by annotating the
affected HTML elements and invoking the PDX Javascript li-
brary that modifies the DOM accordingly. In particular, PDX
includes two behaviours: -able elements, hat possess infor-
mation enabling behaviors, and -ing elements, that act based
on the information of connected elements. There are also
-er elements, that provide characteristics of both. Technical
2https://www.tinymce.com/
3http://www.fabiovitali.it/pdx/
details of PDX are not discussed for the sake of brevity but
they are a key component for SSE and templates functioning.
6 DISCUSSION AND CONCLUSIONS
Now ADF and SSE are currently used by a small team of
Alstom users to create and share documents. We are collect-
ing feedback in two ways. On the one hand, SSE includes
a form that authors can use at anytime to signal issues and
suggest improvements. On the other, we organized hands-on
sessions in which we collected feedback from the final users
in form of free text notes.
These sessions include 4-6 testers and comprise two test-
ing methods:
(1) cognitive walkthrough on some common and complex
(2) guerilla user testing, on some simple tasks on average
documents (of around 30 pages)
This preliminary testing phase was not exhaustive but
gave us valuable indications about the applicability of tem-
plates in real scenarios and about main usability issues.
We also stressed SSE application loading and working
some documents with more than 500 pages. This was an
important way to understand the scalability of the frame-
work behind SSE. We have no problems working with big
document but we have found that the data formats converter
(for instance from ADF to .DOCX) is quite slow on that kind
of documents.
In the near future we will focus on testing and stressing
template and subtemplating inclusion.
We briefly list here some aspects that our testers high-
lighted so far, with particular attention to templates:
• the overall interface of SSE is perceived as quite usable,
even if some users consider it a bit overloaded; some
users suggest us to use more menus instead of showing
all available options in the toolbar
• the idea of showing a list of available fragments in the
right sidebar is functional; on the other hand, users
are quite skeptical about the scalability of such an ap-
proach with a large amount of fragments; the presence
of a search toolbar and filteringmechanism – that were
not available in the first version of SSE – is rated as
fundamental though
• templates are considered effective tools to force users
to create documents with a given structure; in particu-
lar, the testers appreciated the possibility of creating
templates with all headings blocked. Since other users
can only fill these sections, but cannot remove them,
consistency is easier tomaintain. This is a critical point:
while ADF allows for complex updating mechanisms
and users can even modify an included content, most
authors did not use these templates but preferred more
constrained ones
• the creation of templates is still considered a difficult
task: in particular, users experienced some difficulties
in managing both plain documents and templates in
the same workspace; our current solution is to provide
two separate environments (highlighted with clear
visual clues) that user can easily switch from/to
• updates of templates are useful operations but they
need to be reinforced by introducing preview mecha-
nisms: currently, SSE only shows a description of the
template being updated but users cannot see in ad-
vance how the document looks like if a template is
• templates are too static; most users suggested that
a document might include some content under given
conditions but this cannot be expressed in ADF, neither
is possible with SSE; this is a very interesting and
promising direction, that we plan to address in the
near future.
In conclusion, the preliminary experiments with ADF and
SSE are promising. The pattern-based model of the language,
and in particular its serialization in HTML and enrichment
with semantic information, proved to be feasible and effective.
On the other hand, extensive and complete usability tests
are still needed.
Some extensions and refactoring are already planned for
both ADF and SSE. ADF is being extended to also handle
conditional templates and more sophisticated controls; also,
we are investigating how tomodel objects outside the railway
domain by exploiting the same approach. SSE is evolving
too: we are working to support multiple tabs, multi-format
conversions (for instance, to export in DITA format and to
import content directly from common word-processors) and
to provide users with a more cohesive environment to work
on documents and templates.
[1] Mark Anderson, Leslie Carr, and David E. Millard. 2017. There and Here:
Patterns of Content Transclusion in Wikipedia. InÂăProceedings of the
28th ACM Conference on Hypertext and Social Media (HT ’17). ACM,
New York, NY, USA, 115-124.
[2] Ja-Ryoung Choi, Sungeun An, and Soon-Bum Lim. 2014. Spatial hy-
pertext modeling for dynamic contents authoring system based on
transclusion. In Proceedings of the 25th ACM conference on Hypertext
and social media (HT ’14).
[3] Ja-Ryoung Choi and Soon-Bum Lim. 2016. A digital publishing system
with open resources transclusion and tracing. In Proceedings of the 4th
International Workshop on Document Changes: Modeling, Detection,
Storage and Visualization (DChanges ’16). ACM, New York, NY, USA, ,
Article 3 , 4 pages.
[4] Francesc Campoy Flores, Vincent Quint, and Irène Vatton. 2006. Tem-
plates, microformats and structured editing. In Proceedings of the 2006
ACM symposium on Document engineering (DocEng ’06). ACM, New
York, NY, USA, 188-197.
[5] M. Garrish, T. Siegman, M. Gylling, S. McCarron, Digital Publishing
WAI-ARIA Module 1.0, W3C Recommendation, https://www.w3.org/
TR/dpub-aria-1.0/, 2017.
[6] A. Di Iorio, S. Peroni, F. Poggi, F. Vitali “Dealing with structural patterns
of XML documents”. Journal of the American Society for Information
Science and Technology, JASIST, vol. 65, no. 9, pp. 1884–1900.
[7] Ali Khalili and SÃűren Auer. 2013. Review article: User interfaces for
semantic authoring of textual content: A systematic literature review.
Web Semant. 22 (October 2013), 1-18.
[8] Lung-Chen Lee, Christof Lutteroth, and Gerald Weber. 2010. Improving
end-user GUI customization with transclusion. In Proceedings of the
Thirty-Third Australasian Conference on Computer Science - Volume
102 (ACSC ’10), Bernard Mans and Mark Reynolds (Eds.), Vol. 102.
Australian Computer Society, Inc., Darlinghurst, Australia, Australia,
163-172.
[9] J. Marsh, D. Orchard, and D. Veillard. XML Inclusions (XInclude) Version
1.0. http://www.w3.org/TR/xinclude/, 2006.
[10] Takehiro Nagatomo, Takahiro Tachibana, Keizo Sato, and Makoto
Nakashima. 2016. Partial Bookmarking: A Structure-independent Mech-
anism of Transclusion for a Portion of any Web Page. In Proceedings of
the 29th Annual Symposium on User Interface Software and Technology
(UIST ’16 Adjunct). ACM, New York, NY, USA, 185-186.
[11] Peroni, S., Osborne, F., Di Iorio, A., Nuzzolese, A.G., Poggi, F., Vitali, F.
and Motta, E., 2017. Research Articles in Simplified HTML: a Web-first
format for HTML-based scholarly articles. PeerJ Computer Science, 3,
p.e132.
[12] T. H. Nelson. Literary Machines. Mindful Press, Sausalito, CA, USA,
[13] Vincent Quint and Irène Vatton. 2007. Structured templates for au-
thoring semantically rich documents. In Proceedings of the 2007 inter-
national workshop on Semantically aware document processing and
indexing (SADPI ’07). ACM, New York, NY, USA, 41-48.
[14] S. De Rose, E. Maler, D. Orchard, and N. Walsh. XML Linking Language
(XLink) Version 1.1. http://www.w3.org/TR/xlink11/, 2001.
[15] Gianmarco Spinaci, Silvio Peroni, Angelo Di Iorio, Francesco Poggi,
and Fabio Vitali. 2017. The RASH JavaScript Editor (RAJE): A Wordpro-
cessor for Writing Web-first Scholarly Articles. In Proceedings of the
2017 ACM Symposium on Document Engineering (DocEng ’17). ACM,
New York, NY, USA, 85-94.
[16] Ingo Stock and Michael Weber. 2006. Authoring technical documenta-
tion using a generic document model. In Proceedings of the 24th annual
ACM international conference on Design of communication (SIGDOC
’06). ACM, New York, NY, USA, 172-179.
[17] N. Meyrowitz. Hypertext|does it reduce cholesterol, too? Pages 287-318,
Для достижения обозначенной цели, поставлены следующие задачи:
1. Провести комплексный теоретический анализ понятия «политическая
коммуникация», обозначив ключевые подходы к его определению;
2. Рассмотреть классификацию политических коммуникаций;
3. Выявить роль субъектов в осуществлении политических
коммуникаций;
4. Провести анализ новых информационных технологий в политических
коммуникациях, в частности, изучить применение технологии WEB
2.0;
5. На основании материалов, опубликованных в зарубежных
информационных источниках и прессе, проанализировать
применение технологии WEB 2.0 на примере США и России;
6. Разработать рекомендации по совершенствованию политических
коммуникаций в Российской Федерации с применением новых
технологий.
Методология и методы исследования.
Методологическую базу исследования составили как общенаучные,