Syntax Rules

From XBRLWiki

• Public elements MUST have two custom attributes: @model:creationDate and @model:modificationDate.

Comment-01

• Public elements MAY have two custom attributes: @model:fromDate and @model:toDate.

These attributes establish its currency period (note that the validity of the concept MAY differentiate from its currentness due to reports from long ago). Omission of these attributes results to 'Forever' behaviour. Comment-06

• Language specific information MUST be expressed through label relationships.
• Concepts MUST use 2.1 labels.
• Concepts represented by xlink resources MUST use generic labels.

Comment-02

• Label relationships MUST be placed in an ELR using the default role http://www.xbrl.org/2003/role/link

Comment-03

• 2.1 labels MUST use http://www.xbrl.org/2003/role/label as their role for their standard label.
• Generic labels MUST use http://www.xbrl.org/2008/role/label as their role for their standard label.
• 2.1 labels MUST use http://www.xbrl.org/2003/role/verboseLabel as their role for their definition.

Comment-04

• Generic labels MUST use http://www.xbrl.org/2008/role/verboseLabel as their role for their definition.
• 2.1 labels MUST use http://www.xbrl.org/2003/role/documentation as their role for legal references.

Comment-05

• Generic labels MUST use http://www.xbrl.org/2008/role/documentation as their role for legal references.
• Labels MUST be separated in linkbases according to their language used.
• Extensions MAY be using the special table-row-column-code linkbase for application specific codifications.
• The table-row-column-code resources MUST use http://www.eurofiling.info/xbrl/role/rc-code as their role.

Note:

Current references are described in plain English; as a consequence, labels are a better solution than reference linkbases. In the future, a structured approach for legal references could be undertaken.