Draft PAR Confirmation Number: 175809454.1464
Submittal Email: vberman@cadence.com  
Type of Project: Modification to a Previously Approved PAR P1685 on 11 Aug 2005
1.1 Project Number: P1685
1.2 Type of Document: Standard for
1.3 Life Cycle: Full
1.4 Is this project in ballot now? No
2.1 Title of Standard: Standard Structure for Packaging, Integrating and Re-using IP within Tool-flows, (SPIRIT). Old Title: Standard Structure for Packaging, Integrating and Re-using IP within Tool-flows, (SPIRIT).
3.1 Name of Working Group: SPIRIT Standardization Working Group
Contact information for Working Group Chair
Victor Berman
Email: vberman@cadence.com
Phone: 978-262-6560
Contact Information for Working Group Vice Chair

Email:
Phone:
3.2 Sponsoring Society and Committee:IEEE-SA Board of Governors/Corporate Advisory Group (BOG/CAG)
Contact information for Sponsor Chair:
Chuck Adams
Email: wcadams@us.ibm.com
Phone: 914-765-4382
Contact information for Standards Representative:

Email:
Phone:
3.3 Joint Sponsor:/ ()
Contact information for Sponsor Chair:

Email:
Phone:
Contact information for Standards Representative:

Email:
Phone:
4.1 Type of Ballot: Entity
4.2 Expected Date of Submission for Initial Sponsor Ballot: 2006-12
4.3 Projected Completion Date for Submittal to RevCom: 2007-03
5.1 Approximate number of entities expected to work on this project:
5.2 Scope of Proposed Standard: This standard describes an XML Schema for meta-data documenting Intellectual Property (IP) used in the development, implementation and verification of electronic systems and an Application Programming Interface (API) to provide tool access to the meta-data. This schema provides a standard method to document IP that is compatible with automated integration techniques. The API provides a standard method for linking tools into a System Development framework, enabling a more flexible, optimized development environment. Tools compliant with this standard will be able to interpret, configure, integrate and manipulate IP blocks that comply with the proposed IP meta-data description. The proposed project will create an IEEE standard based on version 1.4 of The SPIRIT Consortium schema and API. The standard will be independent of any specific design process. It does not cover the behavioral characteristics of the IP. Old Scope: This standard describes a meta-data schema for the description of Intellectual Property (IP) and an Application Programming Interface (API) to provide tool access to this schema. This schema provides a standard method to describe IP that is compatible with automated integration techniques. The API provides a standard method for linking tools into an IP framework, enabling a more flexible, optimized development environment. Tools compliant with this standard will be able to interpret, configure, integrate and manipulate IP blocks that comply with the proposed IP meta-data description. The proposed project will create an IEEE standard based on version 1.5 of the SPIRIT schema and API. The IEEE will refine the schema and API and clarify how they are used in the context of hardware design languages such as IEEE 1364 Verilog, IEEE 1666 SystemC, and IEEE 1076 VHDL.
5.3 Is the completion of this standard is dependent upon the completion of another standard: No
If yes, please explain:
5.4 Purpose of Proposed Standard: The purpose of this project is to provide a well-defined XML Schema for meta-data that documents the characteristics of Intellectual Property (IP) required for the automation of the configuration and integration of IP blocks; and to define an Application Programming Interface (API) to make this meta-data directly accessible to automation tools. Old Purpose: The purpose of this project is to provide a well-defined meta-data schema to define the characteristics of Intellectual Property (IP) required for the automation of the configuration and integration of IP blocks; and to define an Application Programming Interface (API) to make this meta-data directly accessible to automation tools.
5.5 Need for the Project: As designs get larger and more complex, the electronics industry is using increasing numbers of IP blocks in those designs. The lack of a standard description of those blocks makes their use difficult and error. This lack of a standard imposes a substantial financial burden on the electronics industry. This standard will help to solve this problem.
5.6 Stakeholders for the Standard: Stakeholders for this standard include EDA vendors, IP vendors, electronic systems builders and IC manufacturers.
Intellectual Property

6.1.a. Has the IEEE-SA policy on intellectual property been presented to those responsible for preparing/submitting this PAR prior to the PAR submittal to the IEEE-SA Standards Board? Yes
If yes, state date: 2005-06-03
If no, please explain:

6.1.b. Is the Sponsor aware of any copyright permissions needed for this project? Yes
If yes, please explain: The standard will be based on material owned by The SPIRIT Consortium. They have agreed to transfer the copyright of this material to the IEEE for use in this proposed standard.

6.1.c. Is the Sponsor aware of possible registration activity related to this project? No
If yes, please explain:

7.1 Are there other standards or projects with a similar scope? No
If yes, please explain:
and answer the following: Sponsor Organization:
Project/Standard Number:
Project/Standard Date: 0000-00-00
Project/Standard Title:

7.2 Future Adoptions
Is there potential for this standard (in part or in whole) to be adopted by another national, regional, or international organization? Yes

If Yes, the following questions must be answered:
Technical Committee Name and Number: IEC TC93 WG2
Other Organization Contact Information:
Contact person: Alex Zamfirescu
Contact Email address: alex.zamfirescu@gmail.com

7.3 Will this project result in any health, safety, security, or environmental guidance that affects or applies to human health or safety? No
If yes, please explain:
7.4 Additional Explanatory Notes: (Item Number and Explanation)
8.1 Sponsor Information:
Is the scope of this project within the approved scope/definition of the Sponsor's Charter?
If no, please explain:
Contact the NesCom Administrator