-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft -01 #4
Conversation
- clarify decision to not add api actions from previous author meeting - split entity per suggestion #2 - add motivation notes for entity
# Conflicts: # draft-colwell-privacy-txt.md
@lvanderpeet I think the spec should define the encoding of a boolean attribute. Is it 0/1 or false/true? Alternatively, something to consider, I've been thinking it might be more human readable to work with nominal values instead of booleans. Consider the following two equivalent
I feel like the second one is much more readable. What do you think? Field#4: |
…aft-colwell-privacy-txt.md`
@grittygrease do you have more changes pending? I'm starting to work on fixing the build now. |
Regarding the URL section, should we just reference RFC3986? |
That seems fair. security.txt has some robust text here:
https://datatracker.ietf.org/doc/rfc9116/
A field MUST always consist of a name and a value (for example:
"Contact: ***@***.***"). A "security.txt" file can
have an unlimited number of fields. Each field MUST appear on its
own line. Unless otherwise specified by the field definition,
multiple values MUST NOT be chained together for a single field.
Unless otherwise indicated in a definition of a particular field, a
field MAY appear multiple times.
Implementors should be aware that some of the fields may contain URIs
using percent-encoding (as per Section 2.1 of [RFC3986]).
…On Wed, Jun 26, 2024 at 2:12 PM Brien Colwell ***@***.***> wrote:
Regarding the URL section, should we just reference RFC3986
<https://datatracker.ietf.org/doc/html/rfc3986>?
—
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABHDHZ32TZUNWFDXCFEGIN3ZJMABRAVCNFSM6AAAAABHIUFKKGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJSGM2TCOBRHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Merging the I also think a more concise format definition would be UTF-8 encoded (RFC3629) and use |
An example of merging
|
Use text from security.txt around fields and url parsing.
@lvanderpeet For this spec |
Addressing feedback from the first draft.