-
Notifications
You must be signed in to change notification settings - Fork 6
Open
Description
One thing I just thought of while trying to describe the proposed
tag to the NeXML team: if you look at Mike’s translation of the original TSS spec (https://github.com/OpenTreeOfLife/phylostylotastic/blob/master/documentation/nexss%20specification.md), we had previously put a lot of styling specification on the tree selector as an abstract general selector.I think that in the original spec of TSS, since we were styling a phylogenetic tree specifically and not a NeXML/NexSON/Nexus document, we assumed that a stylesheet would only be styling one tree, hence we would have general canvas/tree/scale selectors.
However, over the course of the hackathon, it seems that NexSS is evolving more towards a slightly more general specification for styling files that contain trees in them, so therefore could specify more than one tree. Hence the idea of the
<figure> element: it would contain the references to the tree that is being styled, etc.A few questions that I thought of in regards to that:
- Does a
<figure>element contain<tree>elements or does it contain some sort of meta property that refers to a tree element? - Should the original
treeandscaleselectors in the TSS spec now be specified asfigure treeandfigure scalein the NexSS spec? (and is that the correct way to specify descent?) - I can't think of more questions right now; I got distracted in the middle of writing this and forgot if I was going somewhere. I am just going to post this issue now.
Metadata
Metadata
Assignees
Labels
No labels