Publication websiteWebsite of the publication
Publications for the Open Web Platform: The vision and technological challenge
Our dreams are of a universe in which the Internet is a prime source of literature and all types of publication. Magazines, company announcements, magazines, journals, novels, educational manuals, magazines, newsletters, magazines, etc. - you can find them everywhere. Web Publication, a forward-looking view of what will happen in today's information society, is presented in this paper. It is built on a fully natural way of presenting information within the Open Web Platform.
Published web content can be packed and transportable. Internet publishing works either on-line or off-line. Published material can be available, linked and annotated. In this section, the current state of the publication of this report is described. Others may replace this one. It is a general guideline and should not be regarded as a general engineering requirement.
Instead, the aim is to sketch out this visions and possible technological trends and reflect the debates that have taken place in the Digital Publishing Interest Group. Specifically, this paper discusses some of the technological impacts and possible resolutions resulting from the Digital Publishing Interest Group's use cases and needs, documenting them in an accompanying URL document[pwp-ucr].
For a more detailled and rigorous set of specifications, a separate committed working group should be established in the near term; the definitive text of this paper will be issued as a stakeholder note. The Digital Publishing Interest Group has released this paper as a stakeholder note. It is a design that can be up-dated, superseded or obsolete by other documentation at any moment.
There is no point in describing this as any other documents than those in work. Publications 1. 1 What is a web publication? These " pages " have since developed into websites and web apps, with ever smaller and smaller contents, increasingly created by more and more people, more and more interactive data bases.
These different forms of appearance can be defined as "publications": bound issues of useful mediums that are published. Our belief is that it is of great value to combine this older tradition - wearable, bound publication - with the ubiquitous availability, addressing and networking of the Open Web Platform. And we believe that the Internet has allowed everyone to communicate without having to formally check, so that individuals will be able to ad hoc post their work.
The purpose of this paper is to examine the technological viability of this approach and some of the issues arising from our use cases described in "PWP Use Cases and Requirements"[pwp-ucr]. Publications 1. 1 What is a web publication? Web publication (WP) is a set of one or more constitutive ressources organised in a clearly identified grouping that can be presented using common Open Web Platform technology.
Web publication is not just a compilation of links - the act of publication consists of procuring and organising ressources in a publication that must be "manifested" (in the meaning of FRBR[frbr]) by making the ressources available on a web serve. In this way, the publishers provide an origins for the WP and a unique identifiable link to this event.
Web publications must deliver a standard order of priority order for your initial ressources, but this order can be modified by either operator intervention or scripts. Readers must also be able to directly address any source of information via the navigational tools provided by the publication itself or the users agents. You can package a Web publication (and become a PWP-packed Web publication) by combining some or all of its constitutive assets into a unified one.
Especially the relatives URLs within the publication may not be changed. Credentials related to a publication should stay the same. In our opinion, the unpacked state of a web publication is something of a canon. The package provides a convenience for transferring and storing a publication, but users' operators are not obliged to view, comment on or refer to such contents in boxed state.
Web publication can be mobile and it can be harbored elsewhere. However, PWP must retain information about its initial source and identification so that reference to a wearable copy can be matched against the initial publication. There must be the possibility of making web publications available to a wide spectrum of users with different needs and abilities.
Web publication profiling can also be specified with stricter publication access criteria. Web publication must be available and operational while the subscriber is off-line. As far as possible, a given subscriber should have a smooth interaction with a web publication, regardless of their networking connections.
In the definition of web publications, we make no difference between on-line and off-line. Web publication that has an identity and character that goes beyond its constitutive ressources has at its disposal subordinates that describe the publication as a whole. Furthermore, we present the abstracted conception of a manifesto that transports information about the constitutive ressources of the publication.
Metro data and the Manifesto also contain information about the order and representation of the contents. In this early phase we do not define how web publications should be packed, how they should be identifiable or how we should save information about the publication as a whole. An additional, more detailled use case letter[pwp-ucr] is attached to this work.
The digital publication is at a turning point. The added complexities of producing, disseminating and displaying publication have slowered the acceptance of EPUB and, in many cases, resulted in the open web offering much more functionality than EPUB usually offers. In the case of non-traditional (or ad-hoc) publication formats, there is a dichotomy between the need to create easy to distribute and consume contents (e.g. via PDF) and the user's wish to make use of the web's diverse presentation and interaction possibilities.
Decreasing or bridging the gaps between publication requirements and web capabilities will significantly decrease the level of complication for both authorization and publication. Most of the use cases described in [pwp-ucr], such as page layout or handling a resource set, are also of relevance for many document-oriented web contents.
Publishing houses have also been developing workflow, editing, typographic and creative capabilities that could have a positive impact on the overall development of webmasters. Our vision for Packaged Web Publications is similar to the objectives and technologies of Progressive Web Apps: crossing the borders between websites and portable applications, emphasizing "offline" paradigms, so on.
It' s timeto extend the extent and strength of the web to cover releases. The following definition forms the basis of this paper. As used by the Web audience, this paper uses the word operator, such as WAIlossary. Publishers often use the word "reading system" for about the same concept; although there are fine distinctions, it is better to adhere to a common concept for the purpose of this work.
Web publication (WP) is a set of one or more constitutive ressources organised in a clearly identified grouping that can be presented using common Open Web Platform technology. Packaged Web Publication (PWP) is a Web publication whose constitutive assets are aggregated into a unified redistributable resource using a common packing style.
Manifesto in this paper relates to an abstracted means of containing information necessary for sound administration, reproduction and so on of publication. In contrast, there are meta data containing information about the contents of the publication, such as name of the originator, date of publication, etc. Exact formats of how such a manifesto is saved are not taken into account in this work.
Locators are the means by which a human agents is able to localize a constituting WP resources. Because a WP can be on-line or off-line, packed or unpacked, it may take more than a single WebResolution. In this section, some of the areas of engineering work that should be addressed for a more accurate and detailled web publication specifications are covered.
Its most important meaning is that of web publications: the fact that a WP, i.e. a Web resource, identified a set of Web resources that convey the "narrowness" that characterises a publication (e.g. a volume or article). There are several things a Web Publications Operator must do when dealing with Web Publications:
Make some kind of on-premises memory or WP contents memory available. In order to do this, the agents must intercept the HTTP(S) request from the rendering engines and possibly retrieve the contents from their own memory or from the files. This means that the operator must act as a net proxies.
Being able to dissolve a locator to the constituent ressources of a WP, independent of the state of the WP.... State-of-the-art web worker [web-workers] and web worker [service-workers] browsers make it possible to develop such a solution. At the same time, they offer a highly customizable and programable way to effectively deploy Web resource locally cached.
As a result, the browser's rendering engines no longer know whether a given asset comes from the built-in or directly from the network: in fact, these are some of the fundamental features that a Web publishing application needs to offer in order to edit Web publications. A publication should be clearly identifiable, e.g. for libraries catalogs or archives, and a resources locator should be available so that the users can retrieve the contents.
That is, a Web publication should contain both one and possibly more identifiers and locations. They may be the same, but may also be different: for example, an identifying marker may relate to a particular publication of a publishing house (e.g. using an ISBN), while the localiser may reference a copy of that publication which the proprietor is free to comment on for his or her use.
Scientifically published information is a case in point for the use of an identification that goes beyond the necessity of a location. IDs appended to web publications should provide robust quotes. No universally acceptable means exists for the identification of a publication between the different types of documents (electronic or printed).
For example, within the scientific publishers sector, DOI and CROSSREF have tackled this challenge, while traditionally "commercial" publishers are more dependent on ISBN-related service provision. Web publication should be defined without regard to its precise name; this subject is entrusted to specialised departments and professional organisations.
From an architectural point of view, the only identifier requirements are that a web publication must contain one or more descriptors and that these should be robust, e.g. when the publication is copied or when its position on the web is altered. As a general principle, the entry in (1) should only be amended by the competent authority and MUST be part of the WP Manifesto.
Web publication is a whole that can be made up of many parts. A way is needed to describe this whole thing, a place where information about the publication and its elements can be stored. Manifesto is the word we use to describe a vessel's content in a paper. The manifesto may contain the following:
Publish your mead data, directly or by referencing. This is a listing of publication ressources and information about them. This is the standard order of the initial publishing component. Links to alternate forms of publication. Information for the member agents on the presentation of the publication. Several of these additional Manifestmembers have already been examined in the work "Browser Friendly Format" of XPUB3.
Considering the wide variety of applications we imagine for web publications, there may even be several options for mass producing the information needed in a manifesto. The entire digitale publication sector uses sophisticated methadata terminology and its series. Thus ONIX[ONIX] has achieved a dominating position within the retail sector as a set of published data that usually does not depend on the publication (in HTML format) and contains not only bibliographical data but also commercial information such as prices.
Scientific publication, on the other paper, often uses different derivates of the omnipresent terminology of BeibTeX. Web Publications does not conflict with the apparent use cases for out-of-line repositories as used by editors, merchants, and librarians, but must provide a set of underlying in-line repository descriptors that are generic to the publication state.
Although Web Publications is anticipated to provide a minimum definition of a necessary subset of relevant information (see Section 2.1. 2 Addressing and Identification), the evolution and incorporation of other words into Web Publications is likely to be considered outside the range. This means that the domain-specific requests for information are for the individual domain itself, which can be specified via a profile scheme or similar means yet to be determined.
Using HTML as a means of presenting published grade publication grade methadata (i.e. using RDFa[html-rdfa] and/or Microdata[microdata] for methadata such as author or title) would have the added advantage of better IM18N representation than using either HTML or JSON-format. Accessing the Web Publications functions using the programmer-API is a very important characteristic when it comes to Web applications that use Web Publications.
In fact, their specifications require a different degree of expert knowledge than most of those described in this paper. Today, certain kinds of Web resources used in a Web publication (such as HTML or SVG) can be programmatically accessible via the Doc-O-Matic API, which provides attribute and method information to fully navigate the tree-like nature of, for example, HTML contents, different attribute levels, or text contents.
A web publication, however, is a set of ressources; therefore, a number of surgeries for this set as a whole should be possible. Possible applications include: full-text searching across the entire web publication, ensuring a continual section, listing, spreadsheet, etc. Numbers if the corresponding web resource is continually viewed, i.e. as part of the web publication; these actions can be carried out via the actual default interface, but each of these programs would need to build and maintain a set of such documents interface.
Callers should also have in-depth knowledge of the state and packing models (if any) used for the WP. Therefore, it would be necessary to redefine such a document collection interface together with a number of appropriate attribute and method definitions. A lot of Web Publications' programming is based on the interaction of single ressources and information, which are saved elsewhere, e.g. in the Web Publication Manifesto.
This includes creating the Document Collection Interface for the Web Publication itself, accessing the various elements of journal data (such as the publication title), and making information about the publication's semiantic structure available. The definition of a default model and API, representing a Web publication, makes the retrieval of information from the manifesto and associated subdirectories fully interoperable across deployments that use different philosophies.
The Open Web Platform in general and CSS in particular still lack a solution to meet publishers' expectation of a satisfying typeface and design of electronic publishing, as stated in[dpub-latinreq] or[dpub-css-priorities]. Although enhanced adherence to presentations will be of utmost importance for the overall impact and acceptance of web publishing, it is clear that many of these topics will be dealt with on a case-by-case bases by the Working Group over a longer timeframe.
For example, STM publication, in which the true presentation and reproduction of e.g. formulas of mathematics or chemistry is of the utmost importance, has particularly high demands that must be met by Open Web Platform technology. Similarly, the browser no longer supports native page navigation of reflow-enabled contents, forcing user agents to perform page navigation using a variety of ad hoc strategies, all of which place a significant burden on design cost, power, and robustness.
While it is expected that stakeholder groups will propose indigenous page navigation assistance (in either or both CSS and the DOM) as a crucial part of web publishing, the completion of web publishing may be subject to the provision of a indigenous page navigation paradigm for web contents. Personalisation - i.e. the possibility for the user to customise the layout to his needs - is of great importance when it comes to scanning long-drawn (and sometimes business-critical) documents.
Whilst technology such as CSS Media Queries has come a long way in customizing contents to device, this is not the same as customizing to a single end-customer. Today, functions for controlling presentations are available in various publication agent versions. Unfortunately, today's deployments are fragile and finite since there is no basic frameworks that support explicit customization.
Transferring, saving, splitting, or archival of a web publication is simpler if it can be summarized as a separate one. There are several such packing types today that often use RIP together with an HTML-Manifesto. Neither is generally accepted and endorsed in any published or web environment. It is expected that packing will not be closely linked to the web publication design, so different packing sizes can be used for different uses.
However, if this is adopted by default Web browser environments, we anticipate that it will be supported as a default Packaged Web Publications package as well. Web site authentication, which is primarily rooted in the policies of source and "site", does not cover mobile devices because the term "source" is rooted in HTTP characteristics that are invalidated/not present when a device moves from its on-line state to its mobile state.
WebPublishing must include a Web Publishing vulnerability management framework that sets policies for both on-line and mobile states and conforms to WebPakaging. In order to be design-oriented, web publishers must be able to accept all types of publication from all areas and use all available web technology. But in order to meet the needs of their members and rationalise the production and exchange of publication in their eco-systems, certain areas or stakeholders may take advantage of restricting the available choices or demanding certain functions that would be strictly necessary for web publishing in general.
This would lead to web publication profiling that would be fully applicable to web publications, but with special adaptations made in a particular way to obtain these advantages. As an example, the present EPUB-based publication delivery pipeline is benefiting from needs such as a particular packing size, navigational functions and meets data that are likely to be a part of the possibilities available to web publications in general.
What is currently an EPUB may be desired to become a particular kind (and thus a profile) of Packaged Web Publication. However, such a section can specify a packing size or the precise serialisation systax for its manifold (possibly in accordance with the latest version of the EPUB specification). Similarly, there could be an education-optimised profiling that requires certain functions for access and optimisation of inter-operability with Learning Management Systems (LMSs) or Virtual Learning Environment (VLEs), or a profiling for academic publication that requires quotes in a specific manner and optimised for publication of information.
Describes a blueprint for achieving greater interoperability between the Open Web Platform and handheld content, while promoting and extending the current eco-system for digitally published content. When the Publication Manifesto is on a Web App Manifesto, this should actually be deleted and based on what this specifies.
It is the aim of this encryption algorithms to obtain the PWP Manifesto on the basis of the value of the stateless L location. This encryption algorithms is executed by the operator agents, usually when initializing with the stateless L location of a particular PWP entity. It gets the PWP Manifesto from L on the basis of the HTTP(S) replies to an HTTP GET requirement. If the end User Agents already has the buffered publication, it is likely that it will dominate (modulo aache state) and there must be no HTTP at all.
When this answer is successfully received, the algorithms will stop by giving the calling party the reply text as a PNP Manifesto. Manifested (to be defined) by its medium types, the algorithms stop by giving the calling party the answer contents back to them as a PNP-Manifesto. This is a compressed copy of a CWP entity (identified by the medium to be specified for the compressed state of a CWP):
Unzip the packet and fetch the Manifesto included in the packet as specified by the packaged state of a PWP. When the HTML contents contain a declared contents encapsulated in a item, it is seriatized into one of the acceptable PWP manifest serializations: Get the contents of the item and analyze it.
Once parenting is completed successfully, the algorithms will stop by sending the analyzed contents of the Manifest back to the calling program as a PWP-Manifesto. When the HTML contents contain a in the header: When the answer is successfully received, the encryption algorithms will stop by sending the answer text back to the calling party as a PWP-Manifesto.
You should then adjust the behavior of the algorithms by inserting an appropriate fork (e.g. the SVG specifications include items that can be used to mount a Manifesto, but have no item). The HTML may contain several items, each related to a specific Manifesto.
When permitted by a PWP spec, the corresponding stage could be changed by considering all linking items and looking at the Manifest file in order in the documents sequence to obtain the Manifesto. Similarly, if a PWP spec allows multiple different types of dualization syntax for the manifests, the UAE should be able to detect and analyze them.
It is expected that the different possible mass comparisons MUST mass comparisons the same contents, i.e. they do not affect the outcomes. It does not disclose the detail of how to retrieve a Manifesto from a packet. Whether a Manifesto should be located at a known place within a packet, whether there could be multiple Manifesto entities within a packet, etc., determines whether a Manifesto should be located at a known place within a packet.
It uses the constants manifold, also used by the Web App manifold, to display the relation between a given asset and its manifold. When outputting an HTTP GET, the UTA CAN insert an Accept headers (see[rfc7231]) to indicate its preferred state, e.g. for a packaged state of a CWP over a declared paysload or for a particular serialisation of the declared state.
Thoughts, feedbacks, review, content, critique, and inputs were key contributors to this document: