From a54835d5987b5f9bde79b6f08408eccf16da441e Mon Sep 17 00:00:00 2001
From: hategan <mhategan@gmail.com>
Date: Tue, 19 Mar 2024 15:06:09 -0700
Subject: [PATCH] Renamed the `projectName` attribute to `account` and
 clarified that it is to be mapped to whatever the scheduler uses for
 accounting.

---
 specification.md | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/specification.md b/specification.md
index d2112e5..654c129 100644
--- a/specification.md
+++ b/specification.md
@@ -1560,18 +1560,20 @@ If no queue is specified, the implementation or LRM may either choose a default
 queue or throw an [`InvalidJobException`](#invalidjobexception).
 
 
-<a name="jobattributes-setprojectname"></a>
+<a name="jobattributes-setaccount"></a>
 ```java
-void setProjectName(String projectName)
-String? getProjectName()
+void setAccount(String account)
+String? getAccount()
 ```
 
-Sets/gets a project name. 
+Sets/gets an account for accounting/billing purposes.
 
-It is common for local LRM policies to use projects to allow structured billing 
+It is common for local LRM policies to use accounts to allow structured billing
 of CPU-hours. If no project is specified, the implementation or LRM may either 
 choose a default project or throw an 
-[`InvalidJobException`](#invalidjobexception).
+[`InvalidJobException`](#invalidjobexception). Certain schedulers may have the notion of a
+`project` or both an `account` and `project`. This attribute must be mapped to
+the scheduler option that is intended for billing/accounting.
 
 
 <a name="jobattributes-setreservationid"></a>