|
Key-Value pairs?
Dictionary?
Hashtable?
Associative array?
Or am I missing something?
|
|
|
|
|
I'm looking for a (possibly not existing) term for the file format, like CSV also refers to the file format (or layout if you will) although in-memory it would be a DataTable or whatever.
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
key-value pair data file
«In art as in science there is no delight without the detail ... Let me repeat that unless these are thoroughly understood and remembered, all “general ideas” (so easily acquired, so profitably resold) must necessarily remain but worn passports allowing their bearers short cuts from one area of ignorance to another.» Vladimir Nabokov, commentary on translation of “Eugene Onegin.”
|
|
|
|
|
Headache
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
You have no idea! The general file format is the smallest of headaches - when you see the field descriptions the real headache starts: "215 : Indicates if the title is contained in field 300 or 315" might give you a small idea of it... 
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
modified 28-Feb-16 6:02am.
|
|
|
|
|
In that case Sascha's Delirium Tremens (SDT) may fit better... 
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Right!  
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
I believe the main term used when dealing with splitting content is "delimited". So, line-delimited values, or something?
|
|
|
|
|
Indexed-data file with line-separated values.
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
Looking at the title, I thought that you were looking for a ...
Term as a Faculty member in a University.
|
|
|
|
|
Are you sure that's not an INI file? 
|
|
|
|
|
Well.. they initialize the madness that will befall you when actually dealing with their semantic content.. 
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
This is the closest that comes to my mind. INI format is exactly what you've got there, except yours is missing the = sign between the key and value. You have section headers followed by a bunch of key value pairs that only apply to that section.
Now you may not be using for configuration data, which is what INI format files are typically used for, but I don't think that's a requirement of the format per se.
|
|
|
|
|
Unless I{m missing something, it looks like columnar data to me.
CQ de W5ALT
Walt Fair, Jr., P. E.
Comport Computing
Specializing in Technical Engineering Software
|
|
|
|
|
Please take a look - can you confirm the term "columnar" for this kind of file/record layout?:
### 00043nM2.01000024 h
001 0000000913
003 20150612
004 20100526
030 a|1ibr|a|||17
076eTourismus
100 Finger-Benoit, Claus
104aGayler, Brigitte
331aAnimation im Urlaub
335aHandbuch fr Planer und Praktiker
359 Claus Finger ; Brigitte Gayler
403 3., vollst. berarb. u. aktualis. Aufl.
410 Mnchen [u. a.]
412 Oldenbourg
425a2003
433 IX, 340 S.
434 Ill.
451bLehr- und Handbcher zu Tourismus, Verkehr und Freizeit
527z636517721 Digitalisierte Ausg. --->Animation im Urlaub
540aISBN 978-3-486-27363-2 Pb.
568 03N052763
655ehttp://www.gbv.de/dms/hbz/toc/ht013645014.pdf
655ehttp://d-nb.info/965931528/04
700 T::FIN
750cDas Standardwerk zur Urlaubs-Animation in dritter Auflage! Es ist ebenso ein Zeitdokument des modernen Tourismus, wie eine Handlungsanweisung zum animativen Urlaub fr Tourismusunternehmen, Studierende der Touristikstudieng„nge, G„stebetreuer und Urlauber. Aus dem Inhalt: Einleitung. Grundlagen der Animation. Urlaubserwartungen und Urlaubsaktivit„ten. Inhaltliche Bereiche der Animation im Urlaub. Die Person - der Animateur, die Animateurin. Grundlagen und Prinzipien der Animation. Systembeschreibungen - Beispiele realisierter Animation.
902 Animation
902 Urlaub
902 Handbuch
### 00044nM2.01000024 l
001 0000000913
003 20150612
004 20100526
012 0000000913
100 T 76
105 Bibliothek
120 00001465
### 00045nM2.01000024 h
001 0000000915
003 20150612
004 20100526
030 a|1ibr|a|||17
076eTourismus
100 Schulz, Axel
331aVerkehrstr„ger im Tourismus
335aLuftverkehr, Bahnverkehr, Straenverkehr, Schiffsverkehr
359 von Axel Schulz
403 1. Auflage
410 Mnchen
412 Oldenbourg
425a2009
433 X, 342 S.
434 Ill., graph. Darst.
451bLehr- und Handbcher zu Tourismus, Verkehr und Freizeit
501 Literaturverz. S. [321] - 334
540aISBN 978-3-486-58876-7 Gb. : 34,80 EUR
568 08N290333
655ehttp://deposit.d-nb.de/cgi-bin/dokserv?id=3131366&prov=M&dok_var=1&dok_ext=htm
655ehttp://www.gbv.de/dms/zbw/571624782.pdf
655ehttp://d-nb.info/989417263/04
700 T::SCHUL
750cZiel des Lehrbuches ist es, einen umfassenden šberblick aller Arten von Verkehrstr„ger (Flug-, Bahn-, Straáen- und Schiffsverkehr) und deren Bedeutung im Tourismus zu geben. Hierzu wurde ein Referenzmodell fr alle Verkehrstr„ger entwickelt, welches aus den Grundelementen Markt & Strategie, Produktionsfaktoren, Marketing & Vertrieb, Dienstleistung Reise sowie Unternehmenssteuerung besteht. Dieses theoretische Modell wurde auf die spezifischen Eigenheiten der einzelnen Verkehrstr„ger angepasst, jedoch weitestgehend vergleichbar strukturiert. Den Abschluss jedes Kapitels bilden m"gliche Prfungsfragen, Internetquellen sowie Literaturhinweise. Das Lehrbuch wendet sich an Studenten des Grund- und Hauptstudiums der Studienrichtung Tourismus. "Der Aufbau des Buchs entspricht absolut den Bedrfnissen, welche ich an ein Lehrmittel auf Stufe Bachelor stelle. Die vielen Praxisbeispiele machenes fr Studierende von Fachhochschulen zu einem geeigneten und bersichtlich gestalteten Werk." (AndySchocher, Dozent fr Transportsysteme, Hochschule fr Technik und Wirtschaft HTW Chur, Schweiz)
902 Tourismus
902 Verkehrsmittel
902 Verkehrstr„ger
902 Bahnverkehr
902 Schiffsverkehr
902 Strassenverkehr
902 Luftverkehr
### 00046nM2.01000024 l
001 0000000915
003 20150612
004 20100526
012 0000000915
100 T 78
105 Bibliothek
120 00001426
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
I'd say yes, column delimited. You have three columns. Number, space or lower case letter, then the data. I'm assuming you have text wrap on in the case of line 750. Just odd that they didn't delimit it better.
|
|
|
|
|
milo-xml wrote: Just odd that they didn't delimit it better.
The format originates from the seventies...
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
750 is being wrapped by the browser, there is only one line break.
|
|
|
|
|
Be sure to implement some robust error handling. 
Remember: sh*t happens 
Press F1 for help or google it.
Greetings from Germany
|
|
|
|
|
Yeah.. though I wish that'd be the major challenge here
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
It comes close to an ini file, but I'd go with Walt's columnar data term.
|
|
|
|
|
Distributed recordset ?
My English is permanently under construction. Be patient !!
|
|
|
|
|
This reminds me of an EDI file.
I assume it cannot handle a MULTI-LINE value.
I assume only ONE value per line
Since it has multiple record types inside one file,
I agree that it looks like an INI file without equal signs, or [] sections.
I would start by calling a single file with ONE set of values:
A Space Delimited KEY VALUE file. But you could simplify it by calling it a Key Value file.
The fact that multiple headers can exist, implies some level or hierarchy.
So, I get to:
Hierarchical Key Value File (Sounds nice and formal)
or a
Multi-Section Key Value File
Organized Key Value File
Multi Key Value File
EDIType Key Value File
Hopefully that gets you started
Now are you going to design an event driven parser. Where each time it finds a header, it calls an event to get it parsed until the next hearder?
|
|
|
|
|
Yeah, I think I'll go with Key-Value file 
Kirk 10389821 wrote: Now are you going to design an event driven parser. Where each time it finds a header, it calls an event to get it parsed until the next hearder?
I'll split it into Key-Value pairs first without caring for the values and then pass the list of Key-Value pairs to the next processing stage. I don't need events there but if someone who wants to use my reader-code from the Tip/Trick I'm going to write needs events he'll still be able to implement them on the list of Key-Value pairs 
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
