Skip to content
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

SIARD validation too strict on LOB file/folder names. (P_4.2-3) #599

Open
stighemmer opened this issue Mar 12, 2024 · 0 comments
Open

SIARD validation too strict on LOB file/folder names. (P_4.2-3) #599

stighemmer opened this issue Mar 12, 2024 · 0 comments
Assignees

Comments

@stighemmer
Copy link

I would like to debate the strictness which dbptk enforces LOB file and folder names.

(quoting from version 2.1.1 of the standard)
Section P_4.2-3 states:

The individual table folders contain an XML file and an XSD file, the names of which (folder designation and both file
names) must be identical. With the exception of BLOB and CLOB folders together with their content (BIN, TXT, or XML
files, or a file extension associated with the MIME type of the lob files in case this is known, e.g. JPG), no other folders or
files are permitted.

Example
...Deleted...

Recommendation
It is advisable to normalise the lob folders and lob files and to use, for example, lob1/ and record0.bin, record0.txt, or
record0.xml instead of the actual name, or a file extension associated with the MIME type of the lob files in case this is
known (see restrictions under P_4.2-6).

This section is marked M for Mandatory.

I would like argue that the "Recommendation" part of this section is NOT mandatory. The presence of the phrases "Recommendation", "advisable" and "for example" should indicate that implementers are free to choose other folder
and file names. dbptk should not give ERROR messages for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants