Similar.

In perl "use Foo::Bar" means to load the file Foo/Bar.pm found in @INC (embedded in PERL at compile time)... or...

$PERL5LIB which can be set in shell startup files for users.

Also, Bar.pm requires a specific format, which depends on what you're attempting to accomplish be ingesting this file.

David Favor:
If you look at some of my last questions, you'll see that I rewrote all of my local cemetery's "internment books".  These are books that list things like: when/why people died. where they are buried, etc.  My sister got the job of bookkeeper for the cemetery.  I have free time and they don't know squat about making the information digital.  I spent about 15 months rewriting their books.  She also has maps of the cemetery which is broken into 5 divisions called sections.  Each section is divided into "lots".  Each lot is a set of 12 graves.  The internment books give the name of each person buried in the graves.  I have the digital information as an openoffice calc spreadsheet.  Since I am trying to learn perl, and I don't want to make the maps by hand, I want to get perl to do the work and somehow make the maps.  I used inkscape to draw some of the cemetery but I couldn't figure out how to get the information from the spreadsheet into inkscape.  This made me think that inkscape might be a mistake.  A previous expert mentioned learning javascript.  This is an option but I was seeing if perl can draw before moving to js.  I also looked at putting the sheet into mysql.  What I know is the digital form of the internment books is a useful form and I'm trying into     take advantage of it.  I really have no involvement but I thnk my sister is really overlooking a useful tool.

Start with how you'd like to present the data to users, including how they will query data.

I'd likely present this data as a normal HTML 4x3 or 3x4 table as what a user will see.

In your database, you'll have one table where each row contains section + lot + grave, so section=3 + lot=9 + grave=5 represents each cell in your matrix.

Then either store the actual grave information in another table or maybe just store this data as a custom HTML file, as each grave representation might be very different + representing ad-hoc in a database table can be tricky.

And yes, steer clear of Inkspace, use HTML tables to represent your data + you're coding will be much easier.

Tip #1: Since you're just starting your coding adventure, be sure you generate valid HTML. If you miss this step + generate broken HTML syntax, then you're debugging will be difficult, especially when someone contacts you + says the page their viewing is blank white or the layout is scrambled.

Use https://validator.w3.org/nu/ to incrementally validate your code.

Each time you make a code change, validate your HTML. Your target is 0 HTML errors.

Tip #2: Use WordPress. Once you start working with all this data, there will come a day when you'd like to do something like let people login + add information to their relatives gravesite. If you start with WordPress, you're life will likely be easier in the long run.