Looking for a term
-
In the domain of my current project I'm dealing with exchange formats where records are saved with key-value pairs each in a separate line:
### header
001 value1
002 value2
010 value3
300 value4header of next record
(etc)
As I'm planning on writing a Tip/Trick on a general purpose reader for that kind of format I'm wondering if there is an existing term for this - something like "line separated values"? thanks, Sascha
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
Distributed recordset ?
My English is permanently under construction. Be patient !!
-
Sounds good, though I'm a bit worried people might think it has anything to do with columnar databases... 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 Handbuch00044nM2.01000024 l
001 0000000913
003 20150612
004 20100526
012 0000000913
100 T 76
105 Bibliothek
120 0000146500045nM2.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 Mar -
Are you sure that's not an INI file? :suss:
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.
-
In the domain of my current project I'm dealing with exchange formats where records are saved with key-value pairs each in a separate line:
### header
001 value1
002 value2
010 value3
300 value4header of next record
(etc)
As I'm planning on writing a Tip/Trick on a general purpose reader for that kind of format I'm wondering if there is an existing term for this - something like "line separated values"? thanks, Sascha
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
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?
-
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... X|
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
-
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
-
In the domain of my current project I'm dealing with exchange formats where records are saved with key-value pairs each in a separate line:
### header
001 value1
002 value2
010 value3
300 value4header of next record
(etc)
As I'm planning on writing a Tip/Trick on a general purpose reader for that kind of format I'm wondering if there is an existing term for this - something like "line separated values"? thanks, Sascha
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
-
Records in a "Fielded" text file: Fielded text - Wikipedia, the free encyclopedia[^] (Your "key-value" pairs could easily evolve into something more comprehensive; then you're stuck with a misleading name).
I appreciate your intent, Gerry, but I'm certain that it won't evolve: It's not my own creation, it's a standard originating from the seventies and the basic structure hasn't changed since ;)
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
-
In the domain of my current project I'm dealing with exchange formats where records are saved with key-value pairs each in a separate line:
### header
001 value1
002 value2
010 value3
300 value4header of next record
(etc)
As I'm planning on writing a Tip/Trick on a general purpose reader for that kind of format I'm wondering if there is an existing term for this - something like "line separated values"? thanks, Sascha
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
-
what do mean by exchange formats? fixed format, as in cobol comes to mind, or space delimited, or series data?
It's newline-delimited. I'm just wondering if there's a term for it, like CSV for comma-separated. What is your notion of series data?
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
-
It's newline-delimited. I'm just wondering if there's a term for it, like CSV for comma-separated. What is your notion of series data?
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
-
Isn't CSV technically newline-delimited as well as comma separated? I guess series data, I was thinking if it's ordered like time series, but none of the values are datetime. Not sure if that makes sense. Order Number Value 10 11.2 11 16.5 12 18.5
wizardzz wrote:
Isn't CSV technically newline-delimited as well as comma separated?
Sure. Then "my" format would be "empty-line-delimited and newline-separated" :)
wizardzz wrote:
I was thinking if it's ordered like time series, but none of the values are datetime.
No, that's not the right term for it then. I think I'll go with "something key-value something" ;)
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
-
I appreciate your intent, Gerry, but I'm certain that it won't evolve: It's not my own creation, it's a standard originating from the seventies and the basic structure hasn't changed since ;)
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
-
I threw "evolution" in as an "extra"; I guess I failed to make my point. "Key Value Pair" sounds like IT-speak or something from a grocery flyer.
IT-speak is alright because the only reason I'm looking for a term for it is my intention to write an Article/Tip/Trick for it :)
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.
-
In the domain of my current project I'm dealing with exchange formats where records are saved with key-value pairs each in a separate line:
### header
001 value1
002 value2
010 value3
300 value4header of next record
(etc)
As I'm planning on writing a Tip/Trick on a general purpose reader for that kind of format I'm wondering if there is an existing term for this - something like "line separated values"? thanks, Sascha
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
I would call it "sectioned data" where each record is a "section" of the file starting with a header and having its values in the remainder of the section. I've had to parse data like this a few times before, some not nearly as straightforward as yours though.