boyska/radiomanifest-spec
1
0
Fork 0
Code Issues 2 Pull requests Releases Wiki Activity

minor language fixes

Browse source
This commit is contained in:
boyska 2022-02-13 20:54:03 +01:00
parent 54a7bf9d80
commit 81584fc970
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
spec.asciidoc
View file

@ -233,10 +233,10 @@ format to be easy to extend in the future.
=== Why not add some more field here and there? === Why not add some more field here and there?
Good point. It's pretty hard to define a threshold: should we add a ``slogan`` for a radio? Image? Logo? Good point. It's pretty hard to define a threshold: should we add a ``slogan`` for a radio? Image? Logo?
Gallery? Frequency of broadcasting? We applied the principle of sticking to (what we felt was) the bare Gallery? Frequency of broadcasting? We applied the principle of _Fewer format features are better_, knowing
minimum, knowing that the standard is easily extendable, so future needs can be accomodated. that the standard is easily extendable, so future needs can be accomodated.
=== Why not extend RSS itself? We could add more info to the ``<channel>>`` tag === Why not extend RSS itself? We could add more info to the ``<channel>`` tag
That's a nice idea. However, we think this would make the adoption harder. That's a nice idea. However, we think this would make the adoption harder.