Re: [xri] host-meta comments

--===============0931437718==
Content-Type: multipart/alternative; boundary=0015174c1146c854900463508b75

--0015174c1146c854900463508b75
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Good point. Sounds good to me.

On Thu, Feb 19, 2009 at 4:00 PM, Mark Nottingham <[email protected]> wrote:

>
> The problem is that this will make it impossible to use an existing HTTP
> header parser (e.g., in Python, Perl, Ruby, whatever's standard library), a
> goal that's guided a lot of the design.
>
> Why not just use
>
> Link: </foo>; rel="something"
> Comment: This one is for you, Joe!
> Link </bar>; rel="joes-link"
>
> ?
>
>
>
> On 19/02/2009, at 3:54 AM, Dirk Balfanz wrote:
>
>
>>
>> On Wed, Feb 18, 2009 at 8:23 AM, Breno de Medeiros <[email protected]>
>> wrote:
>> While /host-meta is intended to be parsed by machines and not
>> human-readable content, it is often the case that users eyeball such content
>> for clues. For instance:
>>
>> 1. Developer is writing and debugging a library to parse host-meta files.
>> 2. Developer is looking at /host-meta examples to get clues on how to
>> write one for his site.
>>
>> Being able to add human-readable comments on site-meta can be useful for
>> such tasks. It also helps to preserve 'institutional memory' by
>> documentation in place, which is often the only one that developers can
>> locate.
>>
>> Should there be a simple mechanism for line comments in site-meta?
>>
>> +1 for comments.
>>
>> I propose that any line that starts with # (possibly preceded by
>> whitespace) is a comment.
>>
>> Dirk.
>>
>
>
> --
> Mark Nottingham       [email protected]
>
>
>


-- 
--Breno

+1 (650) 214-1007 desk
+1 (408) 212-0135 (Grand Central)
MTV-41-3 : 383-A
PST (GMT-8) / PDT(GMT-7)

--0015174c1146c854900463508b75
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Good point. Sounds good to me.<br><br><div class=3D"gmail_quote">On Thu, Fe=
b 19, 2009 at 4:00 PM, Mark Nottingham <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:[email protected]">[email protected]</a>&gt;</span> wrote:<br><blockq=
uote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 204, 20=
4); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
The problem is that this will make it impossible to use an existing HTTP he=
ader parser (e.g., in Python, Perl, Ruby, whatever&#39;s standard library),=
 a goal that&#39;s guided a lot of the design.<br>
<br>
Why not just use<br>
<br>
Link: &lt;/foo&gt;; rel=3D&quot;something&quot;<br>
Comment: This one is for you, Joe!<br>
Link &lt;/bar&gt;; rel=3D&quot;joes-link&quot;<br>
<br>
?<div><div></div><div class=3D"Wj3C7c"><br>
<br>
<br>
On 19/02/2009, at 3:54 AM, Dirk Balfanz wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
On Wed, Feb 18, 2009 at 8:23 AM, Breno de Medeiros &lt;<a href=3D"mailto:br=
[email protected]" target=3D"_blank">[email protected]</a>&gt; wrote:<br>
While /host-meta is intended to be parsed by machines and not human-readabl=
e content, it is often the case that users eyeball such content for clues. =
For instance:<br>
<br>
1. Developer is writing and debugging a library to parse host-meta files.<b=
r>
2. Developer is looking at /host-meta examples to get clues on how to write=
 one for his site.<br>
<br>
Being able to add human-readable comments on site-meta can be useful for su=
ch tasks. It also helps to preserve &#39;institutional memory&#39; by docum=
entation in place, which is often the only one that developers can locate.<=
br>

<br>
Should there be a simple mechanism for line comments in site-meta?<br>
<br>
+1 for comments.<br>
<br>
I propose that any line that starts with # (possibly preceded by whitespace=
) is a comment.<br>
<br>
Dirk.<br>
</blockquote>
<br>
<br>
--<br></div></div><font color=3D"#888888">
Mark Nottingham &nbsp; &nbsp; &nbsp; <a href=3D"mailto:[email protected]" =
target=3D"_blank">[email protected]</a><br>
<br>
<br>
</font></blockquote></div><br><br clear=3D"all"><br>-- <br>--Breno<br><br>+=
1 (650) 214-1007 desk<br>+1 (408) 212-0135 (Grand Central)<br>MTV-41-3 : 38=
3-A <br>PST (GMT-8) / PDT(GMT-7)<br>

--0015174c1146c854900463508b75--

--===============0931437718==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Apps-Discuss mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/apps-discuss

--===============0931437718==--