The Incommon Federation wiki has moved.

Please visit the new InCommon Federation Library wiki for updated content. Remember to update your bookmarks.

Click in the link above if you are not automatically redirected in 15 seconds.



You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 21 Next »

Research and Scholarship (R&S) Category Application Form

To have your service considered for the Research and Scholarship (R&S) Category, a PI, site administrator, technical contact, or some other responsible individual should complete and submit this web form. All fields are required.

Questions? Please send email to admin@incommon.org with "R&S Application" in the subject line.

Unknown macro: {mail-form}
Unknown macro: {mail-input}
Unknown macro: {mail-input}

Service Information

Name of my service:

Unknown macro: {mail-input}

Name of the organization that owns/runs my service:

Unknown macro: {mail-input}

The entityID of my service (to determine your entityID, browse for your entity info page):

Unknown macro: {mail-input}

Information URL of my service (for end users):

Unknown macro: {mail-input}

How my service supports research and scholarship (2–3 sentences):

Unknown macro: {mail-textarea}

Requirements

My service meets the following basic requirements:

Unknown macro: {mail-input}

My service supports research and scholarship as an essential component.

Unknown macro: {mail-input}

My service does not engage subjects in experiments that require specific oversight.

My service meets the following technical requirements:

Unknown macro: {mail-input}

My service metadata has been submitted to InCommon and published in a human-readable format on the InCommon public web site.

Unknown macro: {mail-input}

My service is a production service that supports SAML V2.0 Web Browser SSO.

Unknown macro: {mail-input}

My service refreshes and verifies metadata at least daily.

Unknown macro: {mail-input}

My service provides an MDUI DisplayName in metadata (one of numerous User Interface Elements in metadata).

Unknown macro: {mail-input}

My service has an endpoint in metadata that supports the SAML V2.0 HTTP-POST binding.

Unknown macro: {mail-input}

My service provides both technical and administrative contacts in metadata.

Unknown macro: {mail-input}

My service provides requested attributes in metadata.

Personal Information

Unknown macro: {mail-input}
Unknown macro: {mail-input}

My name:

Unknown macro: {mail-input}

My email address:

Unknown macro: {mail-input}

My affiliation with this service (PI, site administrator, technical contact, service operator, etc.):

Unknown macro: {mail-input}

The following is a true statement:

Unknown macro: {mail-input}

I have read the InCommon Participation Agreement and understand that my service is bound by this Agreement (which was signed by my organization) and therefore my service is subject to the Privacy constraints outlined in section 9 of that document.


Unknown macro: {mail-input}

By pressing the "Submit Application" button, I certify that my service meets all requirements described in the Research and Scholarship Category document.

Unknown macro: {mail-submit}
Unknown macro: {mail-success}

Application Accepted!

Thank you for applying for R&S. Someone will contact you asap.

#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
  • No labels