-
Notifications
You must be signed in to change notification settings - Fork 26
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
removed duplicate tags that were being printed with some refaddresses…
…; continue to clear log
- Loading branch information
Showing
8 changed files
with
29 additions
and
19 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
a573061
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just wanted to confirm, the equations for DataDefs, GenDefs, IMs, and TMs, should have the
"Eqn:"
text appended before the reference address, correct?@szymczdm @JacquesCarette
Currently, the equations in the models and definitions directly take the labels of their respective model/definition:
Drasil/code/drasil-docLang/Drasil/DocumentLanguage/Definitions.hs
Line 120 in 23680c4
For now, should a hack be made to take in a label and tweak the refaddress with a new
RefType
passed in??
a573061
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, good question. Now that you have asked it, I think that
Eqn:
is something I do in my latex when I have some raw equation for which I have not really thought enough about "where does it belong". But in Drasil, that is never the case: we always know where an equation belongs. It arises in a context. And so if that context is used to 'mark' each equation, giving some provenance information [not quite traceability], that's good.In other words, I think that the change described above is good. In general, I think the label really ought to be
so as to record real traceability information.
a573061
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the idea of capturing provenance information (although the labels can get a little long). However, if the label starts with
DD
doesn't that imply it is a data definition? I might likeEqn:
better than that. It is actually a bit hard to tell without seeing a document completed the way @JacquesCarette proposes. Ideally, it would be nice if this is something that we could change easily. We could then experiment to see what approach we prefer.In the interest of making progress, I'm fine with trying the
DD:<label-of-DD>:<label-of-equation>
approach, if that is the easiest thing to implement at this point.a573061
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One clarification: I only meant this for this "reference address" (i.e. internal label, that would be used in the .tex and .html files), not for the short name that would show up in the rendered document.
Eventually, we'll also likely do something similar (and probably even longer) to the UIDs.
That's the benefit of have layers of names for the same thing: we can have rich provenance information being tracked, without forcing users to see this by default.
a573061
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense. Thanks for the clarification @JacquesCarette.