proposed updates for V1.0

regrant · regrant · commit 19dcc364372a · 2019-11-08T09:11:30.000-07:00
diff --git a/ChangeLog.tex b/ChangeLog.tex
@@ -1,4 +1,4 @@
-The following list contains changes to the community Power API specification version 0.9
+The following list contains changes to the community Power API specification version 1.0
 
 \begin{itemize}
   \item{First release of community Power API}
diff --git a/FutureVersion.tex b/FutureVersion.tex
@@ -5,7 +5,9 @@
 
 \begin{itemize}[noitemsep,nolistsep]
 
-\item{\textbf{Better Support for Frequency Scaling} - Frequency scaling features are not universal between hardware implementions. It is desirable to expose all of the possible behaviors of frequency scaling and we are working towards better descriptive solutions to represent these behaviors in the most accurate manner possible.}
+\item{\textbf{Support for Generic Notifications between Nodes} - Working on capability to send generic notifications between PowerAPI objects. This is expected to be useful for compatibility with other community projects and job management.}
+
+\item{\textbf{Better Support for Frequency Scaling} - Frequency scaling features are not universal between hardware implementations. It is desirable to expose all of the possible behaviors of frequency scaling and we are working towards better descriptive solutions to represent these behaviors in the most accurate manner possible.}
 
 \item{\textbf{Coexistence of Implementations} - One of the driving questions for this future work is - how does one implementation interface with another? It is possible, even likely that an implementor will focus on implementing a portion or portions of the specification. This begs the question of how does implementation A interact with implementation B? Further, what role does the specification play in driving this interaction? We intend to work closely with the community to sort out this issue and document the appropriate guidance in the next version of the specification.
 }
diff --git a/PowerAPI_Community.pdf b/PowerAPI_Community.pdf

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-The following list contains changes to the community Power API specification version 0.9`
	`1`	`+The following list contains changes to the community Power API specification version 1.0`
`2`	`2`
`3`	`3`	`\begin{itemize}`
`4`	`4`	`\item{First release of community Power API}`
Original file line number	Diff line number	Diff line change
`@@ -5,7 +5,9 @@`
`5`	`5`
`6`	`6`	`\begin{itemize}[noitemsep,nolistsep]`
`7`	`7`
`8`		`-\item{\textbf{Better Support for Frequency Scaling} - Frequency scaling features are not universal between hardware implementions. It is desirable to expose all of the possible behaviors of frequency scaling and we are working towards better descriptive solutions to represent these behaviors in the most accurate manner possible.}`
	`8`	`+\item{\textbf{Support for Generic Notifications between Nodes} - Working on capability to send generic notifications between PowerAPI objects. This is expected to be useful for compatibility with other community projects and job management.}`
	`9`	`+`
	`10`	`+\item{\textbf{Better Support for Frequency Scaling} - Frequency scaling features are not universal between hardware implementations. It is desirable to expose all of the possible behaviors of frequency scaling and we are working towards better descriptive solutions to represent these behaviors in the most accurate manner possible.}`
`9`	`11`
`10`	`12`	\item{\textbf{Coexistence of Implementations} - One of the driving questions for this future work is - how does one implementation interface with another? It is possible, even likely that an implementor will focus on implementing a portion or portions of the specification. This begs the question of how does implementation A interact with implementation B? Further, what role does the specification play in driving this interaction? We intend to work closely with the community to sort out this issue and document the appropriate guidance in the next version of the specification.
`11`	`13`	`}`