Federal Register / Vol. 79, No. 73 / Wednesday, April 16, 2014 / Notices 21453 

records while ensuring compliance with 

potentially applicable statutory and 

regulatory requirements, such as the 

Family Educational Rights and Privacy 

Act (20 U.S.C. 1232g; 34 CFR Part 99) 

and the Privacy Act (5 U.S.C. 552a and 

34 CFR Part 5b)? 

2. How could APIs ensure that the 

appropriate individual has provided 

proper consent to permit the release of 

privacy-protected data to a third party? 

How can student data be properly 

safeguarded to prevent its release and 

use by third parties without the written 

consent often required? 

3. How might read-only or read-write 

APIs collect, document, and track 

individuals’ consent to have their 

information shared with specific third 

parties? 

4. How can personally identifiable 

information (PII) and other financial 

information (of students and parents) be 

safeguarded through the use of APIs? 

5. What specific terms of service 

should be enabled using API keys, 

which would limit use of APIs to 

approved users, to ensure that 

information is not transmitted to or 

accessed by unauthorized parties? 

6. What are the relative privacyrelated advantages and disadvantages of 

using read-only versus read-write APIs 

for student aid data? 

F. Compliance Issues 

1. What are the relative compliancerelated advantages and disadvantages of 

using read-only versus read-write APIs 

for student aid data? 

2. How can the Department prevent 

unauthorized use and the development 

of unauthorized products from 

occurring through the potential 

development of APIs? How might the 

Department enforce terms of service for 

API key holders, and prevent abuse and 

fraud by non-API key holders, if APIs 

were to be developed and made 

available? 

3. What kind of burden on the 

Department is associated with enforcing 

terms and conditions related to APIs? 

4. How can the Department best 

ensure that API key holders follow all 

statutory and regulatory provisions of 

accessing federal student aid funds and 

data through use of third-party 

products? 

5. How could prior consent from the 

student whom the data is about be 

provided for release of privacyprotected data to third party entities? 

6. How should a legal relationship 

between the Department and an API 

developer or any other interested party 

be structured? 

7. How would a legal relationship 

between the Department and an API 

developer or any other interested party 

affect the Department’s current 

agreements with third-party vendors 

that operate and maintain the 

Department’s existing systems? 

8. What disclosures should be made 

available to students about what 

services are freely available in 

government domains versus those that 

could be offered at a cost by a third 

party? 

9. If the Department were to use a 

third-party application to engage with 

the public on its behalf, how could the 

Department ensure that the Department 

follows the protocols of OMB 

Memorandum 10–23? 

G. Policy Issues 

1. What benefits to consumers or the 

Department would be realized by 

opening what is currently a free and 

single-point service (e.g., the FAFSA) to 

other entities, including those who may 

charge fees for freely-available services 

and processes? What are the potential 

unintended consequences? 

2. How could the Department ensure 

that access to title IV, HEA student aid 

programs truly remains free, even 

amidst the potential development of 

third-party apps that may charge a fee 

for assistance in participating in free 

government programs, products, and 

services with or without providing 

legitimate value-added services? 

3. What other policy concerns should 

the Department consider with regard to 

the potential development of APIs for 

higher education data and student aid 

processes at the Department? 

4. How would APIs best interact with 

other systems already in use in student 

aid processes (e.g., within States)? 

5. How would Department APIs 

benefit or burden institutions 

participating in title IV, HEA programs? 

6. While the Department continues to 

enhance and refine its own processes 

and products (e.g., through 

improvements to FAFSA or the IDR 

application process), how would thirdparty efforts using APIs complement or 

present challenges to these processes? 

Accessible Format: Individuals with 

disabilities can obtain this document in 

an accessible format (e.g., braille, large 

print, audiotape, or compact disc) on 

request to the program contact person 

listed under the FOR FURTHER

INFORMATION CONTACT section of this 

notice. 

Electronic Access to This Document: 

The official version of this document is 

the document published in the Federal 

Register. Free Internet access to the 

official edition of the Federal Register 

and the Code of Federal Regulations is 

available via the Federal Digital System 

at: www.gpo.gov/fdsys. At this site you 

can view this document, as well as all 

other documents of this Department 

published in the Federal Register, in 

text or Adobe Portable Document 

Format (PDF). To use PDF you must 

have Adobe Acrobat Reader, which is 

available free at the site. You may also 

access documents of the Department 

published in the Federal Register by 

using the article search feature at: 

www.federalregister.gov. Specifically, 

through the advanced search feature at 

this site, you can limit your search to 

documents published by the 

Department. 

Authority: 20 U.S.C. 3402(4). 

Dated: April 11, 2014. 

Jamienne S. Studley, 

Acting Under Secretary. 

[FR Doc. 2014–08649 Filed 4–15–14; 8:45 am] 

BILLING CODE 4000–01–P 

DEPARTMENT OF ENERGY 

President’s Council of Advisors on 

Science and Technology 

AGENCY: Department of Energy, Office of 

Science. 

ACTION: Notice of Open Teleconference. 

SUMMARY: This notice sets forth the 

schedule and summary agenda for a 

conference call of the President’s 

Council of Advisors on Science and 

Technology (PCAST), and describes the 

functions of the Council. Notice of this 

meeting is required under the Federal 

Advisory Committee Act (FACA), 5 

U.S.C., App. 2. The purpose of this 

conference call is to discuss PCAST’s 

big data and privacy report. 

DATES: The public conference call will 

be held on Wednesday, April 30, 2014, 

from 11:00 a.m. to 11:30 a.m., Eastern 

Time (ET). To receive the call-in 

information, attendees should register 

for the conference call on the PCAST 

Web site, http://www.whitehouse.gov/

ostp/pcast no later than 12:00 p.m. ET 

on Monday, April 28, 2014. 

FOR FURTHER INFORMATION CONTACT: 

Information regarding the call agenda, 

time, and how to register for the call is 

available on the PCAST Web site at: 

http://whitehouse.gov/ostp/pcast. 

Questions about the conference call 

should be directed to Dr. Ashley 

Predith, PCAST Assistant Executive 

Director, at apredith@ostp.eop.gov, 

(202) 456–4444. 

SUPPLEMENTARY INFORMATION: The 

President’s Council of Advisors on 

Science and Technology (PCAST) is an 

advisory group of the nation’s leading 

scientists and engineers, appointed by 


pmangrum on DSK3VPTVN1PROD with NOTICES
21454 Federal Register / Vol. 79, No. 73 / Wednesday, April 16, 2014 / Notices 

the President to augment the science 

and technology advice available to him 

from inside the White House and from 

cabinet departments and other Federal 

agencies. See the Executive Order at 

http://www.whitehouse.gov/ostp/pcast. 

PCAST is consulted about and provides 

analyses and recommendations 

concerning a wide range of issues where 

understandings from the domains of 

science, technology, and innovation 

may bear on the policy choices before 

the President. PCAST is co-chaired by 

Dr. John P. Holdren, Assistant to the 

President for Science and Technology, 

and Director, Office of Science and 

Technology Policy, Executive Office of 

the President, The White House; and Dr. 

Eric S. Lander, President, Broad 

Institute of the Massachusetts Institute 

of Technology and Harvard. 

Type of Meeting: Open. 

Proposed Schedule and Agenda: The 

President’s Council of Advisors on 

Science and Technology (PCAST) is 

scheduled to hold a conference call in 

open session on April 30, 2014 from 

11:00 a.m. to 11:30 a.m. 

During the conference call, PCAST 

will discuss its big data and privacy 

report. Additional information and the 

agenda, including any changes that 

arise, will be posted at the PCAST Web 

site at: http://whitehouse.gov/ostp/

pcast. 

Public Comments: It is the policy of 

the PCAST to accept written public 

comments of any length and to 

accommodate oral public comments 

whenever possible. The PCAST expects 

that public statements presented at its 

meetings will not be repetitive of 

previously submitted oral or written 

statements. 

The public comment period for this 

meeting will take place on April 30, 

2014 at a time specified in the meeting 

agenda posted on the PCAST Web site 

at http://whitehouse.gov/ostp/pcast. 

This public comment period is designed 

only for substantive commentary on 

PCAST’s work, not for business 

marketing purposes. 

Oral Comments: To be considered for 

the public speaker list at the meeting, 

interested parties should register to 

speak at http://www.whitehouse.gov/

ostp/pcast, no later than 12:00 p.m. ET 

on Wednesday, April 23, 2013. Phone or 

email reservations to be considered for 

the public speaker list will not be 

accepted. To accommodate as many 

speakers as possible, the time for public 

comments will be limited to two (2) 

minutes per person, with a total public 

comment period of 10 minutes. If more 

speakers register than there is space 

available on the agenda, PCAST will 

randomly select speakers from among 

those who applied. Those not selected 

to present oral comments may always 

file written comments with the 

committee as described below. 

Written Comments: Although written 

comments are accepted until the date of 

the meeting, written comments should 

be submitted to PCAST no later than 

12:00 p.m. ET on Monday, April 28, 

2014, so that the comments may be 

made available to the PCAST members 

prior to the meeting for their 

consideration. Information regarding 

how to submit comments and 

documents to PCAST is available at 

http://whitehouse.gov/ostp/pcast in the 

section entitled ‘‘Connect with PCAST.’’ 

Please note that because PCAST 

operates under the provisions of FACA, 

all public comments and/or 

presentations will be treated as public 

documents and will be made available 

for public inspection, including being 

posted on the PCAST Web site. 

Meeting Accommodations: 

Individuals requiring special 

accommodation to access this public 

meeting should contact Dr. Predith at 

least ten business days prior to the 

meeting so that appropriate 

arrangements can be made. 

Issued in Washington, DC on April 10, 

2014. 

LaTanya R. Butler, 

Deputy Committee Management Officer. 

[FR Doc. 2014–08632 Filed 4–15–14; 8:45 am] 

BILLING CODE 6450–01–P 

FEDERAL COMMUNICATIONS 

COMMISSION 

Information Collection Being 

Submitted for Review and Approval to 

the Office of Management and Budget 

(OMB) 

AGENCY: Federal Communications 

Commission (FCC). 

ACTION: Notice; request for comments. 

SUMMARY: As part of its continuing effort 

to reduce paperwork burden and as 

required by the Paperwork Reduction 

Act (PRA) of 1995 (44 U.S.C. 3502– 

3520), the FCC invites the general 

public and other Federal agencies to 

take this opportunity to comment on the 

following information collection. 

Comments are requested concerning: 

whether the proposed collection of 

information is necessary for the proper 

performance of the functions of the 

Commission, including whether the 

information shall have practical utility; 

the accuracy of the Commission’s 

burden estimates; ways to enhance the 

quality, utility, and clarity of the 

information collected; ways to minimize 

the burden of the collection of 

information on the respondents, 

including the use of automated 

collection techniques or other forms of 

information technology; and ways to 

further reduce the information 

collection burden on small business 

concerns with fewer than 25 employees. 

The FCC may not conduct or sponsor 

a collection of information unless it 

displays a currently valid OMB Control 

Number. No person shall be subject to 

any penalty for failing to comply with 

a collection of information subject to the 

PRA that does not display a valid OMB 

Control Number. 

DATES: Written PRA comments should 

be submitted on or before May 16, 2014. 

If you anticipate that you will be 

submitting PRA comments, but find it 

difficult to do so within the period of 

time allowed by this notice, you should 

advise the FCC contact listed below as 

soon as possible. 

ADDRESSES: Submit your PRA comments 

to Nicholas A. Fraser, Office of 

Management and Budget (OMB), via fax 

at 202–395–5167, or via the Internet at 

Nicholas_A._Fraser@omb.eop.gov and 

to Leslie Smith, Office of Managing 

Director (OMD), Federal 

Communications Commission (FCC), via 

the Internet at Leslie.Smith@fcc.gov. To 

submit your PRA comments by email, 

please send them to: PRA@fcc.gov. 

FOR FURTHER INFORMATION CONTACT: 

Leslie Smith, Office of Managing 

Director (OMD), Federal 

Communications Commission (FCC), at 

202–418–0217, or via the Internet at: 

Leslie.Smith@fcc.gov. 

SUPPLEMENTARY INFORMATION: 

OMB Control Number: 3060–0589. 

Title: FCC Remittance Advice Forms, 

FCC Form 159/159–C, 159–B, 159–E, 

and 159–W. 

Form Number(s): FCC Form 159 

Remittance Advice, 159–C Remittance 

Advice Continuation Sheet, 159–B 

Remittance Advice Bill for Collection, 

159–E Remittance Voucher, and 159–W 

Interstate Telephone Service Provider 

Worksheet. 

Type of Review: Revision of a 

currently approved collection. 

Respondents: Individuals or 

households; Business or other for-profit 

entities; Not-for-profit institutions; 

Federal government; and State, local, or 

tribal governments. 

Number of Respondents and 

Responses: 100,220 respondents; 

100,220 responses. 

Estimated Time per Response: 15 

minutes (0.25 hours). 

Frequency of Response: On occasion 

and annual reporting requirements; 

third party disclosure. 


pmangrum on DSK3VPTVN1PROD with NOTICES