yaml / www.yaml.org Goto Github PK

See subject. This is how it looks like to me.

The link is shown on yaml.org.

YAML has become widely used as a more human-friendly alternative to JSON. Given its widespread use, I was surprised to find no media type registration at IANA. There is also a need for a structured data suffix, +yaml, to formally legitimize media types that are syntactically valid YAML, but also provide semantics.

For IANA registration, someone close enough to the YAML format authoring should submit some paperwork to the IETF (or possibly directly to IANA). I would be happy to provide the bulk of the content for the registration of the media type and the +yaml structured data suffix if someone here would be willing to represent the "owners" of the YAML format.

Happy to provide more info, use cases, etc, if needed.

YAML has lost its way on human readability. When a single space or leading 0 on a number can fundamentally change the outcome you are essentially asking that humans read with the precision of a parser. That is the antithesis of what being human is. As a data serialisation format YAML has it's place but when touting human readability as an organising principal and so heavily comparing it to JSON calling it the "human readable format" is getting increasingly difficult to defend.

So far we only have the index.html top level page, and the /spec/ subdir. We need all the other assets moved in.

https://yaml.org/faq.html says:

Indeed Guido van Rossum of Python has acknowledged that allowing TABs in Python source is a headache for many people and that were he to design Python again, he would forbid them.

I would be interested in knowing the source of that reference, as often tabs are suggested as useful for those who are visually impaired (src, src), and I can find no reference in Googling that Guido has indicated Python ideally should not support tabs.

In fact this link from the Python mailing list indicates that Guido generally supports them (or at least did in the early days -- that's quite old).

Dear Staff,

I'm requesting to add fusionyaml (a java project) to the list of libraries.

Info:

Implemented YAML version(s): 1.0, 1.1
How completely implemented is it: almost completely implemented, with the exception of anchors. Writing comments aren't supported but reading comments are
Project Website: https://www.fusionyaml.org/
Programming Language: Java
Small Note: Depends on SnakeYAML to deliver the best features

Thanks in advance

The website still lists yaml-cpp as a 1.1 yaml library, it should be 1.2

Projects > C/C++ Libraries > Syck:

link goes to unrelated _why impersonator

Like reported in yaml/yaml-spec#172:
Links like https://yaml.org/spec/1.2/#ns-tag-char will be redirected and lose the url fragment.
I think the old page has to be reinstated.
There could be a link on top pointing to the new format and a watermark. Maybe even Javascript that does lead to the correct page including the fragment. Which should be 1.2.1 and not 1.2.2 btw

With all due respect, I understand that the title might be kind of controversial to those of you in the community who do not understand all of the issues at play, and so with the most respect possible, I'm going to try to be professional here now that I have your attention.

Out of respect, I will make my case bluntly:

1. Yaml requires whitespace that actively discriminates against the disabled or older engineers who may have decreased sight.

2. This requirement for non-terminal whitespace To have configuration and execution context is an active issue in the communities that use it that causes problems and errors, often creating issues because even the most fully sighted and careful people will still make mistakes, because the format is so restrictive when it comes to whitespace. Due to this bad design, it's very error prone.

3. The jokes and comments about the YAML format being "made for humans" may not be meant to be discriminatory, but they absolutely are, Because what you're really saying is that humans should be allowed to use it, and if you're not able to because of disabilities such as vision issues, then you're not really human. This is explicit discrimination on its own.

4. This website perpetuates the yaml format, and by doing so, it also perpetuates the inevitable discrimination that happens when somebody wants to join a project that forced the use of yaml (k8s, others) but they are also limited by a disability such as vision loss.

It took me losing my eye as punishment for defending somebody a bully was picking on to give me a different perspective, so I understand that if you are reading this and have 2 working uninjured eyes, this may not seem like a big deal to you.

But if you're trapped in your head because the hollow grey of blindness is all you can see, and you're isolated because of the pandemic and nobody's around to help you, then how are you supposed to join a community, build relationships, or do anything in these communities that require this if the technology itself actively creates a barrier for your contribution or use?

So with all due respect this file format is actively harmful and holds back the progress of humanity, it should be discarded, and I would like you to simply delete it and abandon it, to help humanity progress to using file formats that are not abilest, please.

I tried searching up the project, and every site I found just pointed to this link. A quick ctrl-f on the relocated projects Oracle page tells you that it's not anywhere in there, either.

The comment on the js-yaml implementation has a broken link at the end of the line. Demo
should link to http://nodeca.github.io/js-yaml/ , which seems to work.

I'll look into generating a PR.

http://yaml.org is currently hosted on a cloud vm. It used to be needed because there were cgi programs like ypaste, but ypaste is now hosted elsewhere.

yaml.org is all static so we can host on GitHub.

The following steps should happen:

1. Set up a Makefile rule to build the content into gh-pages
2. Get the yaml/yaml-spec to also build in gh-pages
3. Test the gh-pages site using some other domain
4. Write a Contributing file explaining how new content should be added
5. Set CNAME to yaml.org
6. Work with Clark to update the yaml.org DNS

After this, it will be much easier to maintain yaml.org and have changes get published.

The link to yaml4r leads to a 404 page by sourceforge. Maybe remove that entry from the list.

AFAIK, this is the official logo for YAML, so I did an SVG version of the PNG, and set it to the public domain. There are gazillions of 'YAML logos' out there, but the only one I found directly on a YAML official page was this one, so I'm assuming it's the right one to use...

Zipped because, well, GitHub dislikes SVG.
YAML-logo.svg.zip

(Edit: after validating this SVG, I got an error on the W3C validator, so I uploaded a new version)

Contributing with html code is very error prone. I would suggest to generate html with Jekyll which works great with Github Pages.

Jekyll makes extensive use of YAML with its configuration file and its collections.

I'm quite experienced with it so I'll be happy to help!

Once the site is staged and ready, @cce needs to review it and then make the DNS changes to yaml.org and it will be live.

We already have a www.yaml.com and soon a www.yaml.io.

I'll have to make sure the server that serves yaml.org gets updated. Doubt this would break anything else. GitHub should handle redirects anyway.

I was trying to create a link for subsection Canonical Form of section 10.2.1.4. For that, I inspected the HTML and copied the value of the nearest id attribute, which is canonical-form. Doing so would normally allow one to create the link https://yaml.org/spec/1.2.2/#canonical-form. Clicking on that link, however, sends you to section 3.2.1.3.

According to the HTML specification, section 3.2.3.1, the value of this attribute should be unique.

Yaml is not human friendly. Change the site description to "yet another markup format"

http://yaml.org/spec/current.html :

YAML Ain't Markup Language (YAML™) Version 1.1

I can't see the source for this, so it may be an old file that needs deleting off the server, or an old configuration/deployment path/alias which needs updating.

Noticed this when a forum linked to current.html and noticed this was old.

$ curl -IL https://www.yaml.org 
curl: (6) Could not resolve host: www.yaml.org
$ curl -IL http://www.yaml.org 
curl: (6) Could not resolve host: www.yaml.org
$ curl -IL https://yaml.org 
HTTP/2 200 
server: GitHub.com
content-type: text/html; charset=utf-8
last-modified: Sat, 18 Aug 2018 13:15:52 GMT
etag: "5b781c08-3a8b"
access-control-allow-origin: *
expires: Thu, 06 Dec 2018 23:46:26 GMT
cache-control: max-age=600
x-github-request-id: 1510:03AA:19F8593:2228080:5C09B27A
accept-ranges: bytes
date: Fri, 07 Dec 2018 09:51:00 GMT
via: 1.1 varnish
age: 217
x-served-by: cache-hhn1529-HHN
x-cache: HIT
x-cache-hits: 1
x-timer: S1544176260.249232,VS0,VE1
vary: Accept-Encoding
x-fastly-request-id: 6a67c1fd65937aa94c6dbe354add42932893ae98
content-length: 14987
$

Maybe switching the GitHub Pages website to https broke it?

Historically it seems the main source of information for the yaml / yml debate was the FAQ page, for example on the Wikipedia page for YAML:

https://en.wikipedia.org/wiki/YAML#cite_note-11

It seems with the Github Pages version of the website, this page has been removed, and I can't find documentation on the preferred filename extension for YAML either on the yaml.org website or in the RFCs. Perhaps the faq.html page could be restored?

The yamlvim website is https://www.vim.org/scripts/script.php?script_id=3190.

I'm not sure if it's a typo or the link has been changed, but it was the wrong link, anyway. (3191 not 3190)

Thanks.

For starters there are bad links on the site. I've wanted to help fix those for a long time, but I have never been a able to figure out the files for this site. It would appear that there are .txt files that act as portions of the site that are put together to make the html files via the Makefile. But then there seem to be missing parts --no .txt files seem to correspond to .html sections.

strictyaml is a Python-based YAML parser based on ruamel.yaml. It provides Python-based schema validation and parses a restricted subset of YAML (design rationale given here https://github.com/crdoconnor/strictyaml/blob/master/FAQ.rst).

The link to the 1.0 spec in http://yaml.org/spec/ is wrong:
Current html

Hi! I work as a web developer/designer and would like to contribute in any way I can. Here is a start of a design proposal for the website. Please give feedback and let me know if this is interesting.

https://snakeyaml.org/ seems to be a football page, I presume it used to be the website for the snakeyaml project?

I searched for the official page for snakeyaml but was not able to find it, old page on bitbucket is inaccessible and something called snakeyaml-engine is in the top results, but its version two instead of 1 that is found on maven.

Really confused overall.

Apparently the website maintenance reached a status which counts as unmaintained as the list of trivial open PRs not merged is a proof of that.

I would like to address this issue and assure that yaml.org does not look like a relic.

@ingydotnet @clarkevans @orenbenkiki Can you help me fix that?