dataesr/scientific-paragraphs-categorization huggingface dataset:
It must provide the right information to the right person throughout the organization. A BI system is a data-driven DSS that primarily supports the querying of a historical database and the production of periodic summary reports  [6]. The product data used by MES Software to generate KPI have high frequency traffic pattern. Also, the shop floor and company departments have their own applications that use and produce data. This generate data heterogeneity problem. It is necessary therefore to provide interfaces between the different databases, important memories size and achieve data codification. We propose, then, to adopt structured approach for Performance Measurement System development. In the next paragraph, we will present the different methods of an integrated production control systems design.
It shows the class attributes, and the relationships among the classes. A product routine is a set of operations that describe the methods used to manufacture a product. An operation is allocated to a resource. A work order WO is associated to a product. The data about WO operations are collected and recorded in a report. Software. The MES Software transfers to the ERP WO reports, that computes and displays performance indicators. As a second step, we propose to adopt a Component-oriented approach for PMS implementation. Indeed, it is necessary to elaborate an integrating infrastructure that allows an interoperability of the distributed system. We propose to adopt Enterprise Application Integration architecture (EAI), for Control system integration and PMS implementation. We propose, therefore, an integrating infrastructure based on computer standards, like XML format, that allows the different heterogeneous applications to communicate by messages sends and receipt.
To implement the PMS, we must integrate it within the control system. Indeed, it should collect the data, from the shop floor control and send the performance indicators to the business information system. We will describe the OEE measures implementation. Firstly, we are going to describe the technical architecture of the system (data collection material). Then, we will present, the software architecture that allow system implementation (products data configuration, BI module deployment). The Manufacturing system is organized around a Transport system which allows a routing of the work-pieces, placed upon work-piece carriers, toward a CNC milling machine. A jointed-arm robot is used to load and unload parts for CNC machine. In the control architecture of the system, a SCADA software (CIROS Control) is installed in the top-level computer.
An Ethernet network is connecting several machine controllers. The CNC machine is equipped with a DNC link based on RS-232 , the robot and Transport system with Ethernet extension. Profibus DP connect stopper boxes to the transport system controller. The strategy of integration was to provide a common software infrastructure (Integration Platform) that would allow a wide variety of application tools to communicate and share data, while minimizing the specific development for each tool. The heart of the Integration platform is SCADA software CIROS Control. It is a real-time, object-oriented development environment. The PMS must communicate with the SCADA software CIROS, it must also communicate with a MES software ICIM Production Manager. Let us consider a work order sent by the ICIM Manager to the cell controller CIROS.
The cell controller will select the production routine of the considered part from the Routine File Figure  4 : The ENSAM Machining Cell database. It will check about the resources status. If all necessary resources are available, it will determine adequate material and start the tasks. To develop reports it is necessary, at first, to extend the ICIM Manager Data Base and add Report Tables. Then we must determine the necessary data site, on the ICIM Manager Data base tables. After then, we must establish computation formulas of the indicators to display. We must also, develop SQL queries to select the data from Data base tables. The reporting tools Crystal Reports allow reports development. It is necessary to connect at first to the ICIM Manager Data base through ODBC server, in order to reach all data that will be used in the reports.
EB 3 is a specification language for information systems. The core of the EB 3 language consists of process algebraic specifications describing the behaviour of the entity types in a system, and attribute function definitions describing the entity attribute types. The verification of EB 3 specifications against temporal properties is of great interest to users of EB 3. We give here an operational semantics for EB 3 programs in which attribute functions are computed during program evolution and their values are stored into program memory. By assuming that all entities have finite domains, this gives a finitary operational semantics. We then demonstrate how this new semantics facilitates the translation of EB 3 specifications to LOTOS NT (LNT for short) for verification of temporal properties with the use of the CADP toolbox.
The verification of EB 3 specifications against temporal properties with the use of model checking has been the subject of some work in the recent years. [9]  compares six model checkers for the verification of IS case studies. The specifications used in  [9]  derive from specific industrial case studies, but the prospect of a uniform translation from EB 3 program specifications is not studied. [6]  casts an IS specification into LOTOS NT (LNT for short)  [5]  that serves as an input language to the verification suite CADP  [11]. In short, the majority of these works treat specific case studies drawn from the information systems domain leading to ad-hoc verification translations, but nonetheless lacking in generalization capability. But the main problem in verifying EB 3 specifications against temporal-logic properties relies in the difficulty to handle the recursive definition of attribute functions if one relies on the classical, trace-based semantics.
We show that this operational semantics is bisimilar with the original, trace-based operational semantics. Furthermore, we explore the implications of this result to the translation of EB 3 specifications into LNT. LNT is a process algebra specification that derived from LOTOS  [4]. As a process algebra, it shares many common features with EB 3 and it is one of the input languages of CADP, a toolbox with state-of-theart verification features. CADP permits the verification of system specifications against action-based temporal properties. Translating EB 3 specifications to LNT is not evident. The fundamental difficulties for designing a compiler from EB 3 into LNT are summarized in  [6]. In particular, LNT does not feature global variables. Accesses to local variables is restricted in parallel processes of the form "par proc 1 || proc 2 end par", so that every variable written in proc 1 cannot be accessed in proc 2.
Although, EB 3 programmers cannot define global variables explicitly, EB 3 permits the use of a single state variable, the system trace, in predicates of guard statements. Attribute functions can express the evolution of entity attributes in time, option which introduces an indirect notion of state to the language. As a result, EB 3 expressions of the form "C (T ) ⇒ E " can be written, where C (T ) is a predicate that refers to the system trace (the history of events) and E is a valid EB 3 expression. We then present how EB 3 specifications can be translated to LNT for verification with CADP through an intuitive example and give some conclusions and lines for future work. The automatic translation of EB 3 specifications into LNT is studied in the companion paper  [18]. We note that the translation of our example into LNT is produced using the tool presented in  [18].
Saaty  [29]  relies on the expertise of the user in order to generate the weights of attributes. It is based on the comparison of pairs of options and criteria. It has found widespread application in decision-making problems, involving multiple criteria in systems of many levels  [30]. Its main advantages are: o consideration of non-tangible subjective attributes, o ability to structure a complex problem, multi-criteria, multi-person and multi-period hierarchically, o capability to investigate each level of the hierarchy separately, and to combine the results as the analysis progresses. o binary comparison of elements (alternatives, criteria and subcriteria), o ease of its IT support. The evaluation of the RL (SimaPro)  [31]. This is pos collaborative platform  [32]  between different software the RL demonstrator.
Task 1: Structure Graph The main transformation in Task 1 is Java2Graph. atl that implements a simple mapping between elements in the JaMoPP and FlowGraph metamodels. The mapping is illustrated in Table The library JavaGetText. atl contains a set of getText attribute helpers, one for each metamodel element, that implement the model-to-text transformation task of the case study. In Listing 1. 4 we show an excerpt of JavaGetText. atl, to illustrate its structure. Each helper is an OCL expression on the source model and the helpers call each other to construct complex concrete syntaxes. The excerpt in Listing 1. 4 contains the necessary code to compute the textual syntax of an assignment of the form a=1;.
Task 2: Control Flow Graph Task 2 is implemented in the transformation Graph2Flow. atl. The transformation uses the refining mode of ATL, allowing the developer to specify only the refinement part. In this case a set of rules adds the cfNext reference that encodes control flow edges. All these rules have the structure shown in Listing 1. 5: elements are matched and a cfNext reference is added by calling a getNext Subtask 3. 2 For the generation of data-flow links we implemented a variation of the algorithm in  [1]. The resulting iterative algorithm calculates for each flow instruction the set of definitions that the program needs when arriving to that point. It proceeds backwards by starting from variable uses, analyzing the successors of each flow instruction and propagating back the need for definitions.
In this way, another partition of SQMMs is considered in this section which maps to languages, such as Trust-Serv  [Skogsrud et al. 2004] ,  PeerTrust [Nejdl et al. 2004 ], WS-Trust  [Nadalin et al. 2007 ], and P3P  [Cranor et al. 2006] , that describe a service quality part which is not described in the rest of the SQSLs. The SQMMs of this type are called security-based SQMMs.
Then, preferred authentication methods will be matched so as to select the most common one for the negotiation. Each language is evaluated according to the number of metanegotiation information it can describe. Thus, if it cannot describe any information, it is evaluated as poor. If it describes only one of the aforesaid information types, it is considered fair. If it describes two metanegotiation information types, it is considered good. Finally, if it describes all possible negotiation information, it is considered rich. The evaluation results are presented in the first row of the Negotiation life-cycle activity of Tables X and XI. The vast majority of the languages are not capable of modelling any metanegotiation information. This result holds also in every partition. Only WS-agreement, TrustCom, and X-Contract determine or can represent negotiation protocols, while QoWL is able to both specify the negotiation protocol and the authentication method to be used for the SLA negotiation.
Processing Time X X X X X X Latency X X X X X X X X Timeliness X X X X Precision X Throughput X X X X X X X X X X --Availability X X X X X X X X X X X Accessability X X X X X X X Accuracy X X X X X X X Reliability X X X X X X X X Capacity X X X X X X Believability X Maintainability X X X X Relative Importance X Complexity X Customer Service X Depandability X X X X X Stability X X X X X X Trust X X Understandability X X Integrability X Interoperability X X Resource Efficiency X Reusability X Scalability X X X X X Cost X X X X X X X X X Security Authentication X X X X X X X X Authorization X X X X X X X X Level X X X Integrity X X X X X X Confidentiality X X X X X X X X X Accountability X X X X X Traceability X X X X X X Non-repudation X X X X X X X X Data Encryption X X X X Isolation X Configuration Virtual Organization X X X Location X X Level of Service X X X X Service Version X Supported Standard X X X X X X X Data Maturity/Age X X X Timeliness X X X Reliability X XCompleteness X X X X ACM Computing Surveys, Vol.
Qualitative analysis A large amount of qualitative data was collected from the experiment. We extracted around three hundred comments from the records made during the second phase of the experiment, the one in which participants were asked to complete the list of tasks. The selected method of analysis was the thematic type  [11]. This method is focused on the answers and comments recorded during the experiment, and classified into categories later on. The aim of the thematic analysis is to group together answers or parts of answers that have the same meaning. The thematic groups were then analyzed to identify the different categories of opinion. The objective is to gather and list all the themes covered by the answers to reflect the widest possible range of opinions, distinguishing the positive ones from the negative ones.
Findings In the first phase of the study we collected the data described in the previous Participants section, and we also found that 16/20 liked new technologies, 17/20 use new technology everyday, and 20/20 have found problems in their use. To face these problems, 11/20 inspect the UI to try to solve them by themselves, 8/20 ask other people about the problem, 15/20 search for solutions in the Internet, and 7/20 use the help provided by the system. The last phase of the study revealed that questions of types How and Where were identified by most of the users (15/20) as useful and helpful with statements such as "it can be very useful in certain situations" or "It could be very helpful for locating all options of the vehicle in a faster way". This last statement refers also to a gain of time, which was also identified as a positive value by a total of 10/20 users with statements such as "It is a gain of time" or "it makes me go faster without losing my time".
At the end of the third phase, when we presented the help UI with all the types of questions together, the study revealed that in general, model-based self-explanatory facilities were identified as "useful" and "helpful" by most of the participants (16/20). The study also revealed question types that were not supported by our current implementation. The analysis of the collected data suggests that our model-based self-explanatory UI, with minor design enhancements for major usability improvements, could have the potential to easily help the users. Next section discusses the possible model-based implications for the types of questions that were not supported. Then, we discuss the usability suggestions extracted from the data for our particular implementation of self-explanatory UIs.
Literature Review Research in cases-reuse for ecodesign (i. e. the estimation of environmental impact of a new product, early in design, based on products with similar characteristics) has been done by Jeong et al. [4]. The authors introduced a case-based reasoning (CBR) with environmental evaluation purposes. CBR is an artificial intelligence technique that imitates the human behavior for problem solving, i. e. finding similar cases in the past and adapting it for solving a new problem  [5]. The case is, here, stored within a database structured using the product model FBSe (function-behavior-structureenvironment). After, similarity is analyzed between the new product and the products' cases stored in a casebase; finally analogy is used to estimate the impact of the new product. Moreover, Devanathan  [6]  conduct LCA into teardown benchmarked products giving an impact to the bill of materials (BOM).
Knowledge Reuse Scenarios The ability to reuse design information is dependent on capture, representation and retrieval mechanisms. The design information is extracted from the design process. It is widely assumed that design is an unstructured and informal process, which produces many data. These data are included in many types of file formats (e. g. email, reports and conversations). It is also important to understand that neither the mind of the designer, nor the process of design, follows a specific structure or sequence  [12]. From the design process, three scenarios are seen for reusing knowledge, as illustrated in figure 2. In the first scenario, design information is manually captured and structured to a formal model. In the second one, the information is automatically captured and structured to a formal model.
Acknowledged through Article 22  [80]  of the Nagoya Protocol, the issue of capacities seems to apply only to the reinforcement of capacities in developing countries. The measures proposed in the same article could-and should-However be used as well in developed user countries such as Belgium: as underscored in the Protocol itself, there is a need for each Party to "identify national capacity needs and priorities trough national capacity self-assessments"  [80]. Previous research has shown that the Convention and its ABS provisions are still little known among certain group of stakeholders in Belgium, particularly private actors in downstream development (i. e. , commercialization)  [45]. Beyond the possible bargaining inequalities within the same national playing field, self-regulatory governance also had an impact on global justice.
Among the multiple options which can be implemented one is the sustainable Supply Chain Management (sSCM). The sSCM is the integration of sustainable considerations into supply chain policies, programs and actions  (Large and Gimenez Thomsen, 2011). One of the issues for sustainable supply chain analysis is the lack of relevant data available. Indeed the data available from the open database are not specific to the compagnies products and processes  (Ketikidis et al. , 2008). A possible solution to assess and improve the sustainable performances of the supply chain is to integrate the Product Lifecycle Management data into the supply chain management analysis. PLM "is defined as a concept for the integrated management of product related information through the entire product lifecycle"  (Schuh et al.
The Court held that the rules for determining a single price by Austria for books from Germany were contrary to Treaties and stated its doctrine:"the protection of books as cultural objects can be considered as an overriding requirement in the public interest capable of justifying measures restricting the free movement of goods, on condition that those measures are appropriate for achieving the objective fixed and do not go beyond what is necessary to achieve it. " (European Court, 2009). Non-competition rules applied to the book market are therefore an exception. Like any exception, their impact has to be limited. In the case of eBooks, the digital access to data or reading devices is a new factor that blurs the traditional assessment by the court of the relevant book market grid. Finally, the hybrid nature of the eBook is a source of discrepancy between the French and the European cultural policies.
" (Linklater, 2012, p. 6)  • The other solution is to consider the book as a database, a text linked to digital services like a search engine offering links to multi media items. "An e-book is a digital object with textual and/or other content, which arises as a result of integrating the familiar concept of a book with features that can be provided in an electronic environment. E-books, typically have in-use features such  [as]  search and cross reference functions, hypertext links, bookmarks. "  (Vasileiou & Rowley, 2008, p. 363). The creators and the supporters of the law have engaged in fierce debates. For some people, the state intervention could curb creativity and innovation in this sector. In fairness, the aim of the legislature has to be seen in context: the law was intended to apply only to a segment of the market, foremost fiction, general publishing and humanities (mainstream publishing), excluding academic works, comics and encyclopaedias.
The law of May 26, 2011, remained relatively vague about it. Article 1 states: "This Act applies to a digital book when it is a work of the mind created by one or more authors and is marketed both in digital form and published in printed form, or when it -due to its content and design -may potentially be printed, with the exception of some related components specific for digital publications" 5  (Legifrance, 2011a, Art. 1). The notion of "related components" is a vague and frail thing. The Enforcement Decree of the Act, published on November 10, 2011, has been a surprise. Instead of reducing the electronic book, the decree sought to emancipate the "homothetic" book (which from now on we will use in the legal sense of an eBook) from the paper. Article 1 of the decree thus clarifies the meaning: the components include "the associated search engine, modalities Liber Quarterly Volume 23 Issue 2 2013 for scrolling or browsing of content elements, as well as additions of text or data belonging to different genres, including sounds, music, pictures or movies, limited in number and importance, complementary to the book and designed to facilitate its understanding" 6  (Legifrance, 2011b, Art.
A fixed and dynamic price The law will create two dissimilar legal regimes for creators. The book in the legal sense is subject to publishing contract requirements, defined by the code of intellectual property (as modified by the law). The 6 th article of the act stipulates that "remuneration resulting from the exploitation of this book is fair and equitable", 7 while enriched works depend on other contractual provisions stemming from database law. Nevertheless, the terms of the law link print and digital versions, introducing the idea of "substitutability" between both supports. For customers, the content remains identical; the costs of production are essentially the same. The homothetic definition of an eBook defines therefore the book market as a single market, in which the total revenue of the publishing industry is preserved: a rise of digital sales will counterbalance a decline of physical sales.
Purchases of eBooks by a university library are therefore subject to this law. Far from facilitating the selection process, a strict application entails a separation of the publishing offer in two parts: on the one hand eBooks with reviews and on the other hand eBooks only. A third part could even be composed of eBooks whose definition does not match with the 1 st Article: e. g. , the juridical nature of an encyclopaedia makes it difficult to characterize it as an eBook or a database with regard to the law's definition. The legal terms involve very fine distinctions. Furthermore, some practices hardly comply with the terms of the decree. For instance, the decree does not specify the status of commercial offers for eBooks hosted on the same platform as magazines, but sold separately from the latter.
Therefore, as soon as a "digital item" is recognized as an eBook, all the legal clauses of the publishing contract would have to be applied, including discussions about the computation of the profit and its sharing, and the duration of the transfer of copyright. • Others accepted. In some cases, the tariff has been separated in two tiers: one part is subjected to the standard rate ("technical fees"), the other is subjected to the reduced rate ("intellectual property fees"). It is almost impossible to compel reluctant providers. The terms of the definition can be interpreted in a very narrow manner, and the simple presence of a hyperlink is enough to give arguments for characterizing the book as part of a database. Of course, the case of package purchases is much more difficult: if a library takes a subscription for a bundle of eBooks, the reduced rate would (normally) not apply.