The following is the public test suite for the Edgar Filing Guide...
http://sec.gov/spotlight/xbrl/interactive_data_test_suite.shtml
Thursday, September 17, 2009
How to add human readable names to XBRL Extended Links
Extended Links have a title attribute, by adding a human readable name to this attribute most applicatinos can display this attribute.
Why do this, the Extended Link URIs are not useful in User Interfaces, therefore having a human readable name is useful, hence using titles.
One draw back is that you can only have one label, and cannot have a language attribute.
An alternative way to do this is to add an ID on an extended link and have resources that refer to that id. This is not an XBRL standard, but is feasible. Not that any XBRL application support this.
Why do this, the Extended Link URIs are not useful in User Interfaces, therefore having a human readable name is useful, hence using titles.
One draw back is that you can only have one label, and cannot have a language attribute.
An alternative way to do this is to add an ID on an extended link and have resources that refer to that id. This is not an XBRL standard, but is feasible. Not that any XBRL application support this.
Friday, September 11, 2009
XBRL Filings
XBRL is flexable enough to allow users to report data, verify its consistency. The extensibility however is a challenge to support when creating a storage solution.
Finding a balance between infinite flexability and creating storage in a RDMS is a challenge.
How do you deal with facts reported more than once?
How do you deal with facts reported but in different documents?
Do different filers have the same presentation?
Thoughts?
Finding a balance between infinite flexability and creating storage in a RDMS is a challenge.
How do you deal with facts reported more than once?
How do you deal with facts reported but in different documents?
Do different filers have the same presentation?
Thoughts?
Subscribe to:
Posts (Atom)