<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma",sans-serif;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#002060;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-AU" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US">Hi Mike,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US">> </span><span style="color:#1F497D">Per your request to point the working group page to
<a href="https://id.cto.telstra.com/public/openid-connect-account-porting-1_0.html">
https://id.cto.telstra.com/public/openid-connect-account-porting-1_0.html</a>, you may not be aware that the OpenID Foundation IPR procedures require that OpenID specifications be developed on foundation-controlled infrastructure. Therefore, I need to request
that the official copies of spec work currently happening on the Telstra host be moved to one of
<a href="https://bitbucket.org/openid/mobile">https://bitbucket.org/openid/mobile</a>,
<a href="https://github.com/openid">https://github.com/openid</a>, or <a href="http://svn.openid.net/">
http://svn.openid.net/</a>, so that future contributions happen on OpenID Foundation infrastructure. (It’s of course fine to have local private copies that you do editing in, but no public references should be made to those copies.)</span><span style="color:#1F497D;mso-fareast-language:EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I would much prefer an openid.net URL pointing to the latest Account Porting .html file in the Bitbucket repo.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">The spec work <i>is</i> done on foundation-controlled infrastructure — namely at
<a href="https://bitbucket.org/openid/mobile/">https://bitbucket.org/openid/mobile/</a>.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">The Telstra link is solely because bitbucket seems unable to server an .html as a web page to a browser.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Some other <a href="http://openid.net/wg/mobile/">
MODRNA WG</a> specs use xml2rfc.tools.ietf.org links (also not foundation-controlled infrastructure) to dynamically convert .xml from the repo to .html, eg
<a href="https://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi?Submit=Submit&format=ascii&mode=html&type=ascii&url=https://bitbucket.org/openid/mobile/raw/tip/draft-user-questioning-api.xml">
OpenID User Questioning API</a>. But that doesn’t work properly for the Account Porting spec as it includes a .png image.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">The <a href="http://openid.net/wg/heart/">
HEART WG</a> page uses links such as <a href="http://openid.bitbucket.org/HEART/openid-heart-oauth2.html">
http://openid.bitbucket.org/HEART/openid-heart-oauth2.html</a>, but they all seem to be broken.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">The <a href="http://openid.net/wg/fapi/">
FAPI WG</a> links to markdown (.md) version of the specs directly in the repo. This seems to work well as Bitbucket displays markdown properly.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Some WGs use openid.net/specs/ links. That looks perfect, but I assume this requires manual action (eg by the WG chair) to update every time a change is committed to the repo — an overhead & delay I really want
to avoid.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">If openid.net can server .html that is automatically pulled from the foundation-controlled repo whenever there is a commit (or, say, every 15 min as an approximation) then I’ll use that. Even better if it can
pull the repo and runs the repo’s build script to create the .html from the .xml and .uml.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I could try to switch from.xml to .md (markdown), which Bitbucket can display nicely. I’m not sure how easy or hard that is, nor whether Bitbucket will display a .png from the repo when showing a .md.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Until then I hope a Telstra link for the latest repo version (“editor’s copy”) isn’t perceived as subverting the IPR procedures.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">P.S. There are a lot of broken links to hg.openid.net and openid.bitbucket.org on the WG pages.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">--<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">James Manger<o:p></o:p></span></p>
</div>
</body>
</html>