You do not have permission to edit this page, for the following reasons:

This IP address has been blocked from editing Wikipedia.
This does not affect your ability to read Wikipedia pages.
Most people who see this message have done nothing wrong. Some kinds of blocks restrict editing from specific service providers or telecom companies in response to recent abuse or vandalism, and can sometimes affect other users who are unrelated to that abuse. Review the information below for assistance if you do not believe that you have done anything wrong.

The IP address or range 3.236.0.0/16 has been blocked (disabled) by ‪ST47‬ for the following reason(s):

The IP address that you are currently using has been blocked because it is believed to be a web host provider. To prevent abuse, web hosts may be blocked from editing Wikipedia.
You will not be able to edit Wikipedia using a web host provider because it hides your IP address, much like a proxy or VPN.
We recommend that you attempt to use another connection to edit. For example, if you use a proxy or VPN to connect to the internet, turn it off when editing Wikipedia. If you edit using a mobile connection, try using a Wi-Fi connection, and vice versa. If you are using a corporate internet connection, switch to a different Wi-Fi network. If you have a Wikipedia account, please log in.
If you do not have any other way to edit Wikipedia, you will need to request an IP block exemption.

How to appeal if you are confident that your connection does not use a web host's IP address:
If you are confident that you are not using a web host, you may appeal this block by adding the following text on your talk page: ((unblock|reason=Caught by a web host block but this host or IP is not a web host. My IP address is _______. Place any further information here. ~~~~)). You must fill in the blank with your IP address for this block to be investigated. Your IP address can be determined here. Alternatively, if you wish to keep your IP address private you can use the unblock ticket request system. There are several reasons you might be editing using the IP address of a web host (such as if you are using VPN software or a business network); please use this method of appeal only if you think your IP address is in fact not a web host.

Administrators: The IP block exemption user right should only be applied to allow users to edit using web host in exceptional circumstances, and they should usually be directed to the functionaries team via email. If you intend to give the IPBE user right, a CheckUser needs to take a look at the account. This can be requested most easily at SPI Quick Checkuser Requests. Unblocking an IP or IP range with this template is highly discouraged without at least contacting the blocking administrator.

This block will expire on 06:21, 30 September 2026.

Even when blocked, you will usually still be able to edit your user talk page, as well as email administrators and other editors.

For information on how to proceed, please read the FAQ for blocked users and the guideline on block appeals. The guide to appealing blocks may also be helpful.

Other useful links: Blocking policy · Help:I have been blocked
Your IP address is in a range that has been blocked on all Wikimedia Foundation wikis. The block was made by ‪Jon Kolbert‬. The reason given is Open proxy/Webhost: See the help page if you are affected .
- Start of block: 05:35, 21 February 2024
- Expiry of block: 05:35, 21 February 2029
Your current IP address is 3.236.31.135. The blocked range is 3.236.0.0/16. Please include all above details in any queries you make. If you believe you were blocked by mistake, you can find additional information and instructions in the No open proxies global policy. Otherwise, to discuss the block please post a request for review on Meta-Wiki. You could also send an email to the stewards VRT queue at stewards@wikimedia.org including all above details.

You can view and copy the source of this page:

((short description|System-level specification language))
((refimprove|date=January 2013))
Within [[computing]], the Rosetta [[system]]-level [[specification language]] is a design language for complex, [[Heterogeneous computing|heterogeneous systems]].  Specific language design objectives include:
* [[Constraint programming|Constraint]] representation
* Heterogeneous system representation and specification [[composability]]
* Well-defined [[Semantics (computer science)|formal semantics]] and support for formal analysis
* [[Scalability]] to large designs
Rosetta was undergoing [[standardization]] at various times.

== History ==
The Rosetta effort emerged from a meeting in of the Semiconductor Industry Council's System-Level Design Language committee in 1996.  The objective of the meeting was to define requirements for a next-generation design language that would address perceived shortcomings in existing languages such as [[VHDL]] and [[Verilog]].  Specific concerns included inability to represent constraints, lack of a formal semantics, inability to represent heterogeneous systems, and heavy reliance on [[computer simulation]] for analysis.  In response to these requirements, three major approaches were pursued:
# Extending [[hardware description language]]s including [[VHDL]] and [[Verilog]]
# Extending [[programming language]]s including [[C (programming language)|C]] and [[C++]]
# Defining new languages

The first approach ultimately resulted in [[SystemVerilog]] and extensions to VHDL while the second resulted in [[SystemC]], all of which became [[Institute of Electrical and Electronics Engineers]] (IEEE) standards for the [[semiconductor industry]].
Rosetta's original application domain was [[system on a chip]] semiconductor systems.<ref>((Cite news |title= Rosetta provides support for system-level design |author1=Perry Alexander |author2=David Barton |work= EE Times |date= June 2000 |url= http://www.eet.com/special/special_issues/2000/techtrends/rosetta.html |url-status=dead |archive-url= https://web.archive.org/web/20000816011143/http://www.eet.com/special/special_issues/2000/techtrends/rosetta.html |archive-date= August 16, 2000 |access-date= October 7, 2013 ))</ref>

Rosetta resulted from the third approach with development beginning under the auspices of the Semiconductor Industry Council and the [[Air Force Research Laboratory]].  Originally developed by Perry Alexander and others at the [[University of Kansas]], it was known simply as System-Level Design Language.<ref name="sldl">((Cite web |title= About SLDL and Rosetta |work= Original web site |publisher= University of Kansas |url= http://www.ittc.ukans.edu/Projects/rosetta/ |url-status=dead |archive-url= https://web.archive.org/web/20040318224600/http://www.sldl.org/ |archive-date=March 18, 2004 |access-date= October 7, 2013 ))</ref>
Standardization was transferred to VHDL International by 2000 and renamed Rosetta (after the [[Rosetta Stone]]) to reflect the heterogeneous nature of its specifications.  Eventually, VHDL International and the Open Verilog Initiative merged to form [[Accellera]], an industry sponsored [[consortium]] for [[electronic design automation]] (EDA) standards.  
A draft standard of Rosetta was published in November 2003 through Accellera.<ref>((Cite news |title=Rosetta Design Language On Road To Standardization |date= November 10, 2003 |work= Electronic Design |author= David Maliniak |url= http://electronicdesign.com/boards/rosetta-design-language-road-standardization |access-date= October 7, 2013 ))</ref>
Standardization was transferred to IEEE [[Design Automation Standards Committee]] (DASC) where it was developed by the Rosetta Working Group under IEEE project P1699 starting in March 2007.<ref>((cite web |title= Rosetta WG - Rosetta Systems Level Design Language Working Group |url= http://standards.ieee.org/develop/wg/Rosetta_WG.html |publisher=IEEE Standards Association |access-date= October 7, 2013 ))</ref><ref>((Cite news |title= P1699 - Standard for the Rosetta Systems Level Design Language Definition |publisher= IEEE Standards Association |work= Project approval letter |author= Sherry Hampton |date= March 22, 2007 |url= http://standards.ieee.org/about/sasb/nescom/projects/1699.pdf |access-date= October 7, 2013 ))</ref>
A draft of a language reference manual was published in April 2008, with editor Peter Ashenden of Australia.<ref>((Cite web |title= P1699 Rosetta LRM subcommittee |date= April 22, 2008 |url= http://www.ashenden.com.au/rosetta-std/ |access-date= October 7, 2013 |url-status= dead |archive-url= https://web.archive.org/web/20150610214353/http://www.ashenden.com.au/rosetta-std/ |archive-date= June 10, 2015 ))</ref>
The project was withdrawn in June 2013.<ref>((Cite news |title= Standards Board New Standards Committee (NesCom) Recommendations |publisher= IEEE Standards Association |date= June 14, 2013 |url= http://standards.ieee.org/about/sasb/nescom/13-Jun-2013_NesRec.pdf |access-date= October 7, 2013 ))</ref>

== Structure ==
Rosetta is structured around three sub-languages that support defining various specification elements.  The ''[[Expression (computer science)|expression]] language'' defines basic functions and expressions used as terms and values in specifications.  The expression language is a [[Strict programming language|non-strict]], [[purely functional language|purely functional]], [[Type system|typed]] language in the spirit of [[Haskell (programming language)|Haskell]].  Functions are [[Referential transparency|referentially transparent]], encapsulated expressions and cannot have side effects.  All Rosetta expressions have types that are determined statically.  The type system is based on lifted sets where each type contains at least the bottom or undefined value.  Any set can be used to define a type and any function that returns a set can be used to define a type former.  Because type definitions can contain general Rosetta expressions, the type system is [[Dependent types|dependent]].

The ''facet language'' defines individual specifications and specification composition to define systems. ''Facets'' and ''components'' define system models from one engineering perspective. Each facet is written by extending a ''domain'' that provides vocabulary and semantics for the model. Facets are defined by declaring items and defining properties for those items.  As such, Rosetta is a [[Declarative programming|declarative language]] and constructs cannot be guaranteed to evaluate to a value, although some facets can be evaluated.  Using the design abstractions provided by its domain, a facet describes requirements, behavior, constraints, or function of a system.  Facets are heterogeneous and may be defined using any of the predefined or user defined domains.  The Rosetta semantics denotes each facet to a [[coalgebra]] that defines its model-of-computation.  Because Rosetta is [[Reflection (computer programming)|reflective]], facets can be composed and transformed to define complex systems.  A common specification technique is to write facets for different aspects of a system and then compose those aspects using product and sum operations to define the complete system.

The ''domain language'' defines specification domains otherwise known as specification types.  The collection of domains forms a [[complete lattice]] ordered by [[homomorphism]] with the empty or ''null'' domain as its top element and the inconsistent or ''bottom'' domain as its bottom.  There are three primary domain types.  Units-of-semantics domains define basic units of specification.  For example, the '''state_based''' domain defines the concept of state and next state without constraining the values or properties.  Model-of-computation domains extend unit-of-semantics domains to define general computational models such as '''finite_state''', '''continuous_time''', '''discrete_time''' and '''frequency'''.  Engineering domains extend model-of-computation domains to provide specification capabilities for specific engineering domains.

Since its early days, Rosetta expanded to include design domains such as hydraulic and  mechanical systems, networking systems, security and trust, and software defined radios.

==Further reading==
Rosetta was influenced heavily by the non-strict, purely functional language [[Haskell (programming language)|Haskell]], the [[Larch Shared Language|Larch]] family of specification languages, and [[Prototype Verification System]] (PVS). A book devoted to the language was published in November 2006.<ref>((cite book |author= Perry Alexander |title= System Level Design with Rosetta |year= 2006|publisher= Morgan Kaufmann |isbn= 978-1-55860-771-2 |url=http://www.elsevier.com/books/system-level-design-with-rosetta/alexander/978-1-55860-771-2#))</ref>

== References ==
((Reflist))

==External links==
* http://www.rosetta-lang.org

((IEEE standards))
[[Category:Formal specification languages]]
[[Category:IEEE standards]]

Pages transcluded onto the current version of this page (help):

Rosetta-lang (edit)
Template:Ambox (view source) (template editor protected)
Template:Cite book (view source) (protected)
Template:Cite news (view source) (protected)
Template:Cite web (view source) (protected)
Template:Find sources mainspace (view source) (template editor protected)
Template:Hlist/styles.css (view source) (protected)
Template:IEEE standards (edit)
Template:Main other (view source) (protected)
Template:More citations needed (view source) (template editor protected)
Template:Navbox (view source) (template editor protected)
Template:Pagetype (view source) (protected)
Template:Refimprove (view source) (template editor protected)
Template:Reflist (view source) (protected)
Template:Reflist/styles.css (view source) (protected)
Template:SDcat (view source) (protected)
Template:Short description (view source) (protected)
Template:Short description/lowercasecheck (view source) (protected)
Module:Arguments (view source) (protected)
Module:Category handler (view source) (protected)
Module:Category handler/blacklist (view source) (protected)
Module:Category handler/config (view source) (protected)
Module:Category handler/data (view source) (protected)
Module:Category handler/shared (view source) (protected)
Module:Check for unknown parameters (view source) (protected)
Module:Citation/CS1 (view source) (protected)
Module:Citation/CS1/COinS (view source) (protected)
Module:Citation/CS1/Configuration (view source) (protected)
Module:Citation/CS1/Date validation (view source) (protected)
Module:Citation/CS1/Identifiers (view source) (protected)
Module:Citation/CS1/Utilities (view source) (protected)
Module:Citation/CS1/Whitelist (view source) (protected)
Module:Citation/CS1/styles.css (view source) (protected)
Module:Disambiguation/templates (view source) (protected)
Module:Find sources (view source) (template editor protected)
Module:Find sources/config (view source) (template editor protected)
Module:Find sources/links (view source) (template editor protected)
Module:Find sources/templates/Find sources mainspace (view source) (template editor protected)
Module:Message box (view source) (protected)
Module:Message box/ambox.css (view source) (protected)
Module:Message box/configuration (view source) (protected)
Module:Namespace detect/config (view source) (protected)
Module:Namespace detect/data (view source) (protected)
Module:Navbar (view source) (protected)
Module:Navbar/configuration (view source) (protected)
Module:Navbar/styles.css (view source) (protected)
Module:Navbox (view source) (template editor protected)
Module:Navbox/configuration (view source) (template editor protected)
Module:Navbox/styles.css (view source) (template editor protected)
Module:Pagetype (view source) (protected)
Module:Pagetype/config (view source) (protected)
Module:Pagetype/disambiguation (view source) (protected)
Module:Pagetype/setindex (view source) (protected)
Module:Pagetype/softredirect (view source) (protected)
Module:SDcat (view source) (protected)
Module:String (view source) (protected)
Module:Unsubst (view source) (protected)
Module:Wikitext Parsing (view source) (protected)
Module:Yesno (view source) (protected)

Return to Rosetta-lang.

Retrieved from "https://en.wikipedia.org/wiki/Rosetta-lang"