-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Xbrl context #1
Xbrl context #1
Conversation
* Change focus to regular XBRL * add review gh action workflow * add important steps to workflow * dont use golang docker image
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.
Would there be any value in having a (* Context) Validate()
that checked higher level semantics?
|
||
// Identifier specifies a scheme for identifying business entities and an identifier that follows the scheme. | ||
// https://www.xbrl.org/Specification/XBRL-2.1/REC-2003-12-31/XBRL-2.1-REC-2003-12-31+corrected-errata-2013-02-20.html#_4.7.3.1 | ||
// For Example: |
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.
<3 including examples of the data that might be parsed
Instant *string `xml:"instant"` | ||
|
||
// Forever is non-nil if Period.Type() returns Forever. | ||
// Note ideally this would be a bool, but the XML Unmarshaller doesn't support |
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.
Should we make a custom unmarshal for it?
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 don't think it's really necessary. Type()
returning Forever
is already a clean way to determine if the period represents 'forever', so you wouldn't really have to interact with this property directly as a user.
I might come back to this later once I'm more experienced with custom unmarshallers though
This might be valuable if/when we come back and add support for Context |
For our purposes, XBRL consists of contexts, facts, and units. This is part one: the contexts