Skip to content
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

Title-only items? #18

Closed
mattgallagher opened this issue May 18, 2017 · 1 comment
Closed

Title-only items? #18

mattgallagher opened this issue May 18, 2017 · 1 comment

Comments

@mattgallagher
Copy link

mattgallagher commented May 18, 2017

I really like the aims of this spec but I wanted to raise an issue/question about "title-only items"...

As I read it at the moment, the mandatory fields for an item are:

  • id
  • content_text OR content_html

Have you considered replacing that second requirement with:

  • content_text OR content_html OR title

The reason for this suggestion is that it would allow lists of links to fall within the spec, without mandating a dummy content_text="" field. Examples for this use-case include a minimalist feed for a link aggregation site like Hacker News or Reddit which is just "Link Text" (title) and "Link" (id).

Alternately...

If there is an expectation, in the absence of a title, that content_text may be contextually the "Link Text", perhaps this should be stated explicitly somewhere in the goals, examples or other discussion to reassure users like myself that it wouldn't be perverting the spec to use content_text in this way.

I personally would prefer not requiring a content tag since sometimes title is a more appropriate description of the semantic meaning than "content" (there are even cases where an item that is purely an id might be appropriate). I understand though if you'd rather downplay certain content structures.

@manton
Copy link
Owner

manton commented May 18, 2017

Thanks @mattgallagher! My take on this is that it's more appropriate for those items to just use content_text. If you think about link-blogging as just a variation of microblogging, it's more consistent to use content_text and content_html everywhere.

You're right that explicitly mentioning this in the spec is a good idea.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants