Roderic Page

@deepreef From the perspective of the LSID archive ideally XML like the example I showed above https://github.com/tdwg/tnc/issues/117#issuecomment-795527382 (which was actually retrieved from ZooBank when its LSID service was live). The...

@deepreef From my perspective I'd just like the ZooBank LSIDs (I think of my services as a "wayback machine" for LSIDs). So my preference is not to include additional links...

@cboelling This was 2005-2006 as I recall, and whatever I said then is probably stuck somewhere on a ZIP file or a DVD! My recollection at the time was that...

@deepreef Cool, I will take a look. From my perspective, in a ZooBank LSID it's not the LSID prefix that is cumbersome... it's the UUID. I think if you (a)...

OK @deepreef I hoping that you're getting some sleep now ;) Here is my version of what ZooBank XML should look like, with comments to explain why I've made the...

@deepreef Oops, forgot your other questions. If there's no info then I would simply not include the corresponding tag, so no volume, no tag. Other identifiers, yes please, especially DOIs...

@cboelling Yes, governance matters, but I would argue providing value to users should be the primary driver. If something isn't useful and doesn't help people do what they want to...

@deepreef Regarding the namespaces in the rdf:RDF tag, they can end in either a forward slash / or a hash #, depending on the choice made by whoever created that...

@deepreef Regarding identifiers there are a bunch of ways to include and represent DOIs (that there are so many ways to do things is yet another reason RDF is hard...

I note that records where the web page displays the article as having a _Part of_ relationship with on for more ISSNs don't display ISSNs in the JSON-LD, e.g. the...