Child pages
  • Research and Scholarship Gap Analysis

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

This document attempts to identify the differences between the InCommon Research & Scholarship Category and the REFEDS Research & Scholarship Entity Category. The latter was formally adopted by the REFEDS community in February 2014. The REFEDS R&S specification was revised to V1.2 on November 28, 2014.

{:=} || ||InCommon
Wiki Markup
Advanced Tables - Table Plus
columnAttributes
style="vertical-align:middle;",style="width:60%;vertical-align:middle;",style="width:40%;vertical-align:middle;"

 

InCommon R&S

Requirement

||

REFEDs

R&S

Requirement

|| | 1 | \[[Participation Agreement|http://www.incommon.org/docs/policies/participationagreement.pdf], section 9\] Participant agrees to respect the privacy of and any other constraints placed on identity information that it might receive from other InCommon Participants as agreed upon between Participant and the InCommon

1

[Participation Agreement, section 9] Participant agrees to respect the privacy of and any other constraints placed on identity information that it might receive from other InCommon Participants as agreed upon between Participant and the InCommon Participant(s).

In

particular,

Participant

understands

that

it

may

not

permanently

store

nor

share

or

disclose

or

use

for

any

purpose

other

than

its

intended

purpose

any

identity

information

that

it

receives

from

another

InCommon

Participant

without

express

written

permission

of

the

other

InCommon

Participant.

Participant

understands

that

the

storing

and

sharing

of

resources

is

between

the

Participant

and

the

InCommon

Participant(s)

and

is

not

the

responsibility

of

InCommon.

|

A

"Service

Provider

claims

that

it

will

not

use

attributes

for

purposes

that

fall

outside

of

the

service

definition."

| | 2 |

2

"Whether

an

SP

operator

is

commercial

or

non-commercial

is

not

relevant

to

eligibility

for

the

R&S

Category,

nor

are

any

other

aspects

of

how

the

service

is

implemented

or

operated,

beyond

the

specific

requirements

noted

below.

It's

all

about

purpose."

|

"This

Entity

Category

should

not

be

used

for

access

to

licensed

content

such

as

e-journals."

| | 3 |

3

"...because

of

the

risk

involved,

a

Service

Provider

that

engages

subjects

in

experiments

that

require

specific

oversight

is

not

eligible

for

the

R&S

Category."

| NA | | 4 |

NA

4

"The

SP

provides

an

mdui:DisplayName

in

metadata..."

|

"The

Service

Provider

provides

an

mdui:DisplayName

and

mdui:InformationURL

in

metadata."

| | 5 |

5

"The

SP

provides

Technical

and

Administrative

contacts

in

metadata."

|

"The

Service

Provider

provides

one

or

more

technical

contacts

in

metadata."

| | 6 |

6

"R&S

category

SPs

may

request

other

attributes,

but

IdP

operators

will

likely

require

a

prior

agreement

before

releasing

additional

attributes."

{

HTML

}<hr>{html}

<hr>
"It

is

therefore

highly

recommended

that

SPs

use

a

minimalist

approach

to

attributes,

only

requesting

those

attributes

that

they

absolutely

need."

|

"Service

Providers

SHOULD

request

a

subset

of

R&S

Category

Attributes

that

represent

only

those

attributes

that

the

Service

Provider

requires

to

operate

its

service."

| | 7 | {{{nl:

7

http://id.incommon.org/category/research-and-scholarship

}}} | {{{nl:

http://refeds.org/category/research-and-scholarship

}}} | {table-plus}

Privacy

[Item 1] Here is the relevant phrase from the Participation Agreement:

...

The primary distinction is that the former is included in a signed legal agreement while the latter is self-asserted by the service owner. See, for example, the R&S application form used by InCommon.

Commercial Services

...

For clarity, these two requirements are broken into three parts on the R&S application form:

  1. [True/False] My service provides requested attributes in metadata.
  2. [Yes/No] Are the requested attributes in metadata a subset of the R&S attribute bundle? (Note: This is highly RECOMMENDED otherwise a bilateral agreement with each IdP may be required.)
  3. [True/False] My service requests only those attributes required to operate the service.

...