[dmitshur], strugee, [tantek], gRegorLove, plenglin and [chrisaldrich] joined the channel
#plenglinI'm trying to figure out a better microformat for my tagging system. Right now, a tag like `cpp` refers to a regular tag. A tag starting with a /, like `/project/astrid-tech/` or `/blog/2020-11-14-kombucha/`, refers to a specific object that is described by a page with that slug.
[dmitshur] joined the channel
#plenglinI've been looking at machine tags (object:project=astrid-tech, compsci:language=cpp), or URN's (urn:astrid-tech:project:astrid-tech), or possibly just referring to objects with their fully qualified URI (i.e. https://astrid.tech/projects/astrid-tech/ or maybe use a custom scheme)
#plenglinHmm, maybe I'm just completely misinterpreting how triple tags are meant to work
[KevinMarks] joined the channel
#[KevinMarks]That's a bit like the rel-tag ragspacw idea
#plenglinI do have tag pages located at slugs like `/tags/cpp/`
#plenglinOh wait, are machine tags are meant to be more like like `mentions:project=astrid-tech` or `part-of:project=astrid.tech` or `uses:cslang=cpp`?
#plenglinSome of these places I'm looking at say machine tags don't require values
#gRegorLoveI think most consumers expect the tag value to be plaintext so aren't doing much special with them beyond that. You could use class="u-category" on the link and the parser would parse the URL instead of the tag name, but consumers don't know to do anything special with that resulting URL