Skip to content

Draft and publish LinkedIn post introducing LMD #8

Description

@EthanThatOneKid

Goal

Draft and publish a LinkedIn post introducing Linked Markdown (LMD), with a light-touch closing ask for help navigating the first-time arXiv submission / endorsement process.

Primary draft

I’m drafting a paper and specification for Linked Markdown (LMD): Markdown as semantic infrastructure.

The idea is simple: a Markdown file should stay a Markdown file, but it should also be able to participate in a semantic graph.

With LMD, a document is:

- valid CommonMark, so GitHub, Obsidian, VS Code, Pandoc, and normal Markdown renderers still work
- valid JSON-LD, so frontmatter can give the document a stable `@id`, `@type`, and RDF-compatible properties
- validatable with SHACL
- queryable with SPARQL
- publishable as static HTML, JSON-LD, or raw Markdown

The smallest useful LMD document is just a normal `.md` file with JSON-LD frontmatter:

```yaml
---
id: https://example.org/docs/my-item
@type: schema:Article
@context:
  schema: https://schema.org/
---

# My Item
Content here.

No custom Markdown syntax. No new file extension. No special renderer.

The goal is to make existing Markdown corpora, docs sites, Obsidian vaults, GitHub wikis, and agent-readable knowledge bases more structured without breaking the human-readable workflows that made Markdown successful in the first place.

The draft spec is here: https://github.com/wazootech/linked-markdown

I’m also preparing the paper for arXiv. If you have experience publishing in cs.SE, cs.DL, or cs.IR and can help a first-time arXiv submitter understand the endorsement process, I’d appreciate a pointer.


## Alternate arXiv CTA options

```md
If you’ve gone through arXiv’s first-time author endorsement process, especially in `cs.SE`, `cs.DL`, or `cs.IR`, I’d appreciate advice.
I may need an arXiv endorsement for the first submission, so if you’re familiar with that process, I’d be grateful for guidance.
If you’re an arXiv author in a related CS category and are open to advising on the first-time submission process, please reach out.

Suggested edits before posting

  • Pick one arXiv CTA; the first alternate is probably the least transactional.
  • Add the public spec URL if preferred over the GitHub repo URL: https://wazootech.github.io/linked-markdown/spec/
  • Consider attaching a screenshot of the minimal LMD document or the spec homepage.

Acceptance criteria

  • Final LinkedIn post is reviewed for tone and technical accuracy.
  • Post includes one clear link to the spec or repo.
  • Post includes a non-transactional arXiv guidance ask.
  • Post is published by Ethan.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions