From no-reply@arXiv.org Tue Feb 17 21:55:06 2009 Date: Tue, 17 Feb 2009 15:52:14 -0500 Message-Id: <200902172052.n1HKqELX021635@arxiv1.library.cornell.edu> From: no-reply@arXiv.org To: wirth@logic.at Subject: RE: hput pdfforarXiv.tex -> 0902.2997.gz (0902.2997, 47kb) Reply-To: cs@arXiv.org To verify abstract and postscript, use http://arXiv.org/abs/0902.2997 Article-id: 0902.2997, Article password: 52gpr (access still password restricted) Abstract will appear in mailing scheduled to begin at 20:00 Tuesday US Eastern time (i.e., Wed 18 Feb 09 01:00:00 GMT). Your title and abstract will appear in the next mailing exactly as below. (Except possibly for the NUMBER which IS NOT OFFICIAL until the next mailing of abstracts [20:00 US Eastern time (EDT/EST) Sun - Thu] -- it cannot be used to cross-list to other archives [e.g., from cs to math or physics] until after that time.) To correct any problems, you MUST replace NOW. Replacements on the same day (until the 16:00 US Eastern time deadline Mon-Fri) do not generate a revised date line, so do not hesitate to replace submission until everything is perfect (including removal of any extraneous files). ------------------------------------------------------------------------------ \\ arXiv:0902.2997 From: Claus-Peter Wirth Date: Tue, 17 Feb 2009 20:52:11 GMT (47kb) Title: ASF+ --- eine ASF-aehnliche Spezifikationssprache Authors: Ruediger Lunde, Claus-Peter Wirth Categories: cs.AI cs.SC Comments: iv + 58 pages Report-no: SEKI Working-Paper SWP-94-05 License: http://creativecommons.org/licenses/by/3.0/ \\ Maintaining the main aspects of the algebraic specification language ASF as presented in [Bergstra&al.89] we have extend ASF with the following concepts: While once exported names in ASF must stay visible up to the top the module hierarchy, ASF+ permits a more sophisticated hiding of signature names. The erroneous merging of distinct structures that occurs when importing different actualizations of the same parameterized module in ASF is avoided in ASF+ by a more adequate form of parameter binding. The new ``Namensraum''-concept of ASF+ permits the specifier on the one hand directly to identify the origin of hidden names and on the other to decide whether an imported module is only to be accessed or whether an important property of it is to be modified. In the first case he can access one single globally provided version; in the second he has to import a copy of the module. Finally ASF+ permits semantic conditions on parameters and the specification of tasks for a theorem prover. \\ Contains: pdfforarXiv.tex: 167550 bytes Stored as: 0902.2997.gz (47kb) Warnings: Author 1: Ruediger Lunde Author 2: Claus-Peter Wirth -> Number of authors = 2 PS files: 0902.2997.ps.gz (114kb) ------------------------------------------------------------------------------ Successful submission to the archives can be a significant source of pride and accomplishment. It entails many serious responsibilities: if you cannot check off on all of the items below, then you should replace your submission. (Note: *do not* resubmit, instead *replace*) ___ The Title/Author fields above are correct. ___ The abstract is complete, correct, and wrapped correctly. ___ Capitalization in title correct (we automatically lower case titles with excessive use of upper case, but we get some acronyms incorrect -- replace with uppercase letters only where they should be). ___ The authors are listed in `Firstname Lastname' order. ___ any anonymous ftp or http pointers to additional files are given in standard url format (e.g. ftp://myhost.domain/path/filename.ext or http://mywwwhost.domain/path/filename.html) ___ Periods are separated by a space from the end of any URL's ___ Any Journal-ref is a complete bibliographic reference to an already published version (includes volume and page number info in the case of a print journal). ___ All files including any figures were included. ___ This paper has not been submitted to any other arXiv.org e-print archives. ___ The full text of the paper itself is available directly from the archive. ___ The submission can be retrieved uncorrupted (TRY IT). Submitters who repeatedly leave errors uncorrected may lose submission privilege to the archives. (Replace using the current tentative paper number unless notified otherwise.) If your abstract is improperly wrapped, note that abstract linefill stops at whitespace indentation (e.g. a blank line or a line indented with space(s) denotes a new paragraph,and won't be wrapped). For further hints, keep reading or see http://arXiv.org/help/ . Guidelines for a proper title and abstract preparation are given at http://arXiv.org/help/prep . If you have not already read this, please read it now to ensure that you have followed the guidelines. It is an abuse of valuable archive admin time to edit abstracts by hand. If you need to replace this paper, then use the `replace' facility at http://arxiv.org/replace. Your entry will not officially appear in the listings until the next mailing goes out (and thus cannot yet be accessed via the search or the daily listings), and your paper number may be changed until that time, so it is necessary to wait a day before cross-listing, etc. DO NOT UNDER ANY CIRCUMSTANCES MAKE A DUPLICATE SUBMISSION OF THIS PAPER. A resubmission is treated as a separate submission, and given a new number, which will have to be removed by hand (and could result in loss of future submission privileges). Instead use the replace facility (see http://arxiv.org/help/replace). DO NOT UNDER ANY CIRCUMSTANCES MAKE A DUPLICATE SUBMISSION TO LIST THIS PAPER TO ANOTHER ARCHIVE within the arXiv system, since the system needs to know that it is one submission and not multiple. Instead use the cross-list facility (see http://arXiv.org/help/cross) to generate a cross-listing for it. ***NOTES*** 1) Avoid excessive cross-listings: cross-listings of a paper on archive-x to archive-y are intended for subjects of *direct* interest to subscribers of archive-y. Those subscribers of archive-y who have peripheral or direct interest in the subjects of archive-x are already subscribed to archive-x and neither need nor desire multiple receipt of the same abstract. (In particular, it is exceedingly unlikely that you could decide what is of direct interest to readers of archive-y if you yourself are not an active reader of archive-y.) 2) Common sense suggests that `replaced' papers are not immediately re-requested so if your intent is to communicate correct research it is in your interest to submit a final version in the first place, i.e. *avoid premature submissions*. If you later need to replace the submission, it would be helpful to indicate in the Comments: field (i.e. below Authors: ) how serious is the revision (e.g. v2: major conceptual changes, v3: minor grammatical changes, etc.), and include as a commented header in the revised version of the paper a guide to the changes for posterity.