Heather Flanagan

Vashon, Washington, United States Contact Info
3K followers 500+ connections

Join to view profile

About

The Internet is powered by words as much as it is by technology.

I would never…

Articles by Heather

See all articles

Contributions

Activity

Join now to see all activity

Experience & Education

  • Spherical Cow Consulting, LLC

View Heather’s full experience

See their title, tenure and more.

or

By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.

Licenses & Certifications

Publications

  • Government-Issued Digital Credentials and the Privacy Landscape

    OpenID Foundation

    This paper is an especially timely as governments around the world seek to scale their existing digital identity credential implementations, or chart a path to deliver new digital identity credential programs. It seeks to offer a balanced, global view of privacy concerns by exploring laws, implementations, gaps, and tradeoffs facing the people developing these new ecosystems. It builds on the thoughtful work of other studies and concludes with tangible recommendations in three areas:

    This paper is an especially timely as governments around the world seek to scale their existing digital identity credential implementations, or chart a path to deliver new digital identity credential programs. It seeks to offer a balanced, global view of privacy concerns by exploring laws, implementations, gaps, and tradeoffs facing the people developing these new ecosystems. It builds on the thoughtful work of other studies and concludes with tangible recommendations in three areas:

    The Basics of Security and Privacy
    Addressing Ongoing Concerns
    Getting Ahead of Emerging Concerns

    Beyond identifying issues, the contributors to this paper seek to point our concrete areas that will inform how to build more privacy-preserving ecosystems, and what issues the community needs to continue working on together.

    See publication
  • Approaching Trust: Case Studies for Developing Global Research Infrastructures

    Frontiers in Research Metrics and Analytics

    Trust is a core component of collaboration. Trust is a local phenomenon, and scientific research is a global collaborative, its impact multiplied through open exchange, communication and mobility of people and information. Given the diversity of participants, local policies and cultures, how can trust be established in and between research communities? You need transparent governance processes, thoughtful engagement of stakeholder groups, and open and durable information sharing to build the…

    Trust is a core component of collaboration. Trust is a local phenomenon, and scientific research is a global collaborative, its impact multiplied through open exchange, communication and mobility of people and information. Given the diversity of participants, local policies and cultures, how can trust be established in and between research communities? You need transparent governance processes, thoughtful engagement of stakeholder groups, and open and durable information sharing to build the “stickiness” needed. In this paper we illustrate these concepts through three trust building use cases: ORCID, Global Alliance for Genomics and Health, and SeamlessAccess, platforms sharing an identity and access technical service core, painstaking community building, and transparent governance frameworks.

    Other authors
    See publication
  • RFC 8153: Digital Preservation Considerations for the RFC Series

    RFC Editor

    The RFC Editor is both the publisher and the archivist for the RFC Series. This document applies specifically to the archivist role of the RFC Editor. It provides guidance on when and how to preserve RFCs and describes the tools required to view or re-create RFCs as necessary. This document also highlights gaps in the current process and suggests compromises to balance cost with best practice.

    See publication
  • RFC 7990: RFC Format Framework

    RFC Editor

    In order to improve the readability of RFCs while supporting their archivability, the canonical format of the RFC Series will be transitioning from plain-text ASCII to XML using the xml2rfc version 3 vocabulary; different publication formats will be rendered from that base document. With these changes comes an increase in complexity for authors, consumers, and the publisher of RFCs. This document serves as the framework that provides the problem statement, lays out a road map of the documents…

    In order to improve the readability of RFCs while supporting their archivability, the canonical format of the RFC Series will be transitioning from plain-text ASCII to XML using the xml2rfc version 3 vocabulary; different publication formats will be rendered from that base document. With these changes comes an increase in complexity for authors, consumers, and the publisher of RFCs. This document serves as the framework that provides the problem statement, lays out a road map of the documents that capture the specific requirements, and describes the transition plan.

    See publication
  • RFC 7993: Cascading Style Sheets (CSS) Requirements for RFCs

    RFC Editor

    The HTML format for RFCs assigns style guidance to a Cascading Style Sheet (CSS) specifically defined for the RFC Series. The embedded, default CSS as included by the RFC Editor is expected to take into account accessibility needs and to be built along a responsive design model. This document describes the requirements for the default CSS used by the RFC Editor. The class names are based on the classes defined in "HTML for RFCs" (RFC 7992).

    See publication
  • RFC 7994: Requirements for Plain-Text RFCs

    RFC Editor

    In 2013, after a great deal of community discussion, the decision was made to shift from the plain-text, ASCII-only canonical format for RFCs to XML as the canonical format with more human-readable formats rendered from that XML. The high-level requirements that informed this change were defined in RFC 6949, "RFC Series Format Requirements and Future Development". Plain text remains an important format for many in the IETF community, and it will be one of the publication formats rendered from…

    In 2013, after a great deal of community discussion, the decision was made to shift from the plain-text, ASCII-only canonical format for RFCs to XML as the canonical format with more human-readable formats rendered from that XML. The high-level requirements that informed this change were defined in RFC 6949, "RFC Series Format Requirements and Future Development". Plain text remains an important format for many in the IETF community, and it will be one of the publication formats rendered from the XML. This document outlines the rendering requirements for the plain-text RFC publication format. These requirements do not apply to plain-text RFCs published before the format transition.

    See publication
  • RFC 7997: The Use of Non-ASCII Characters in RFCs

    RFC Editor

    In order to support the internationalization of protocols and a more diverse Internet community, the RFC Series must evolve to allow for the use of non-ASCII characters in RFCs. While English remains the required language of the Series, the encoding of future RFCs will be in UTF-8, allowing for a broader range of characters than typically used in the English language. This document describes the RFC Editor requirements and gives guidance regarding the use of non-ASCII characters in RFCs. This…

    In order to support the internationalization of protocols and a more diverse Internet community, the RFC Series must evolve to allow for the use of non-ASCII characters in RFCs. While English remains the required language of the Series, the encoding of future RFCs will be in UTF-8, allowing for a broader range of characters than typically used in the English language. This document describes the RFC Editor requirements and gives guidance regarding the use of non-ASCII characters in RFCs. This document updates RFC 7322. Please view this document in PDF form to see the full text.

    See publication
  • Bringing IAM & SSO to the Campus

    TF-Identity and Access Management, APAN 42

    Materials from a workshop on Identity & Access Management held at APAN 42.

    Day One focused on the perspective of the campus, and what campuses and their partners need to consider as they try to understand and prioritize resources around identity management.

    Other authors
    See publication
  • The Value Proposition for Identity Federations

    REFEDS

    From the paper:

    "This paper attempts to bring clarity to the questions that surround the heart of the value proposition for identity federation. Why should identity management and federation be prioritized? What arguments can campus CIOs use to sway the local and regional funding agencies that already have so many demands? What needs to be done to establish an identity federation, and have it interoperate with other identity federations around the world?"

    Other authors
    See publication
  • RFC 7322: RFC Style Guide

    RFC Editor

    Summary:

    This document describes the fundamental and unique style conventions and editorial policies currently in use for the RFC Series. It captures the RFC Editor's basic requirements and offers guidance regarding the style and structure of an RFC.

    Additional guidance is captured on a website that reflects the experimental nature of that guidance and prepares it for future inclusion in the RFC Style Guide.

    This document obsoletes RFC 2223, "Instructions to RFC Authors".

    Other authors
    • Sandy Ginoza
    See publication
  • The RFC Series & the Twenty-First Century

    The IETF Journal

    A short background on upcoming changes to the format for RFCs.

    See publication
  • RFC 6949: RFC Series Format Requirements & Future Development

    RFC Editor

    Summary:

    This document describes the current requirements and requests for enhancements to the format of the canonical version of the RFC Series. Terms are defined to help clarify exactly which stages of document production are under discussion for format changes. The requirements described in this document will determine what changes will be made to the RFC Series format.

    This document updates RFC 2223.

    Other authors
    See publication

Organizations

  • IDPro

    -

    - Present

    From https://idpro.org: IDPro is the organization that: * Helps define, support, and improve the digital identity profession globally * Facilitates identity practitioners interacting with, learning from, and giving back to their professional community * Enables identity technology and service providers to interact with identity professionals in thoughtful, respectful, and valuable ways * Provides a collective voice for the digital identity and access management industry to policy makers

  • Editorial Freelancers Association

    Member

    - Present
  • Northwest Independent Editors Guild

    Member

    - Present
  • American Copy Editors Association

    Member

    - Present
  • International Association of Scientific, Technical & Medical Publishers

    Member

    - Present
  • World Wide Web Consortium (W3C)

    Invited Expert, Publishing Working Group

    - Present
  • Society for Scholarly Publishing

    Member, Communications Committee

    -
  • Special Library Association

    Member

    -
  • SANS GSEC

    Member, Advisory Board

    -

Recommendations received

12 people have recommended Heather

Join now to view

More activity by Heather

View Heather’s full profile

  • See who you know in common
  • Get introduced
  • Contact Heather directly
Join to view full profile

Other similar profiles

Explore collaborative articles

We’re unlocking community knowledge in a new way. Experts add insights directly into each article, started with the help of AI.

Explore More

Others named Heather Flanagan in United States

Add new skills with these courses