Difference between revisions of "FILLOC"
Line 26: | Line 26: | ||
Justification:<br> | Justification:<br> | ||
− | + | This attribute simplifies the management of supporting files. It allows encoders to include in a dataset a pointer to a specific section, paragraph, segment, or other location in a supporting file. This makes it possible to have (for example) all the shipping regulations of a country in one file (or a few files) and have different Regulations objects point to different clauses in the file. The pointer may be an XML ID, HTML ID, line number, bookmark in a PDF file, a “key” in a resources file, etc. Product specifications are expected to describe the meaning of the pointer for a data product and state how the supporting files must be structured (bookmarked, tagged, etc.). | |
Comment: | Comment: |
Revision as of 09:12, 4 August 2011
FEATURE OBJECT ATTRIBUTES
Attribute: File locator
Acronym: FILLOC Code: ?
Camel case: fileLocator
Attribute type: S
Definitions:
The string encodes the location of a fragment of text or other information in a support file.
Remarks:
Product specifications must state how the association between a FILLOC and a support file is made. For example, the associated support file may be identified as the file named by a TXTDSC attribute bound to the same TXTCON attribute. Product specifications must also define the meaning of the value of this attribute. For example, the value may be defined as a fragment identifier for a HTML file, or a character count for a plain text file, etc.
Distinction:
Justification:
This attribute simplifies the management of supporting files. It allows encoders to include in a dataset a pointer to a specific section, paragraph, segment, or other location in a supporting file. This makes it possible to have (for example) all the shipping regulations of a country in one file (or a few files) and have different Regulations objects point to different clauses in the file. The pointer may be an XML ID, HTML ID, line number, bookmark in a PDF file, a “key” in a resources file, etc. Product specifications are expected to describe the meaning of the pointer for a data product and state how the supporting files must be structured (bookmarked, tagged, etc.).
Comment:
No comments.
David | others | Raphael | Jens |
---|---|---|---|
Y/N | others Y/N | RMM Y/N | Y/N |