Technically union is more apt here, because the object will have an
associated schema, it's just unclear what the type for that schema
should be. For instance, does tvdb own the schema under their own
domain? or is it more apt for my.spoor to control it? Going forward I
will use an appropriate tld from the owner of the schema. This should
allow adoption from external providers later if lexicon does take off.
Removed the source field, and made queryable be a union where the type
will reveal how to query, and the data to query will be contained
within. (This is much smarter)...
Changed overrides to be a simple empty object (which should be fine in
the spec). This reflects what it should actually be.
Finally explicitly added the tvdb api v4 option.
I really like this change. I think it'll make records way easier to
understand in the repo, and more useful if the external site goes down.
Also allows shortcut querying if you don't need more data than the title
So I sort of used "object" instead of "record" because I thought key was
an option type ^_^
So I had to fix that.
Also moves title to defs because it is not supposed to be a record
THESE LEXICONS ARE NOT FINAL, she screamed into the wind.
converts all references to woach.me to spoor.my to reflect the official
domain name.
Rename "feed" 3ld to "log" since the content here is separate from what
an activity feed would look like. Log has more in common with records.
I maintained the name activity over "spoor" here, because I want the
items to be easily digested by other services. I think "spoor" is
actually a more apt term than "activity" since "activity" is more
generic, than the specific mediaspoor it is, but it will do.
Changes the "anilist" entry to a more generic "external" entry, which
will be able to handle tvdb, or similar.
I have a local stash with an alternative media method, but for the MVP
we'll just implement anilist. In order to use anilist we need to contact
them to make sure we don't break rule 5 of their Terms of Service.
