As someone who used to log lifting in plain text files (copied from a notebook) I think this is a really good idea.
To avoid all of the comments from people asking about GPS tracking, I think you should make it clear that it's primarily for strength training. The format is clearly oriented around that.
An addition that could make it more useful for recording cardio workouts like swimming/track/indoor cycling would be the concept of rest intervals. For example, it's common to prescribe a part of a swimming workout in a format like this:
4 x 100 at 1:20
Meaning you have 1:20 to complete each 100m rep, where any extra time is rest. You could also add extra fields for recording the actual time taken to complete rach rep. E.g:
Yeah, for sure the first use cases were strength oriented (I like heavy things).
I have a bit in the FAQ in the Guide that hand waves how you could model things like cardio. I personally model my intervals like an example from today
Squat:
# bands: 200lb
# box: 12 inches
# rest: 45 seconds
* wide and medium alternating
225 2r 10s
I love how you did your metadata in your example. I intend to leave the language VERY open ended and hope folks build tools for athletes that provide functionality that is spec compliant (thus portable!) but leverages nuances for the given sport. Thanks for taking a look!
To avoid all of the comments from people asking about GPS tracking, I think you should make it clear that it's primarily for strength training. The format is clearly oriented around that.
An addition that could make it more useful for recording cardio workouts like swimming/track/indoor cycling would be the concept of rest intervals. For example, it's common to prescribe a part of a swimming workout in a format like this:
Meaning you have 1:20 to complete each 100m rep, where any extra time is rest. You could also add extra fields for recording the actual time taken to complete rach rep. E.g: