Hi Felipe,
So you want to define the LOM application profile for Moodle courses (MoodleCore).
Im interested with your work. We will be able to search courses by metadata. Maybe we will export courses with metadata, so we will reuse the courses between moodle platforms.
And why not dreaming: the birth of a Learning Object Repository (LOR) such as MERLOT with Moodle courses exported.
But I wonder for the interoperability with other platforms. In this case, a Learning Object reFeratory (LOF) is more interesting than a LOR.
Lets come back to your work.
Some data elements can be extracted from the moodle database. Other elements are implicit.
Here are some comments for each data element of the LOM.
1.1.1 General.Idetifier.Catalog
1.1.2 General.Identifier.Entry
These data elements are implicit if you use an URI
1.2 General.Title
The value of this data element can be found in the moodle database.
1.3 General.Language
This data element is necessary but Im afraid you have to ask the author for it.
1.4 General.Description
The value of this data element can be found in the moodle database. But be careful the value in the database can be HTML-coded
1.5 General.Keyword
This element is important. Why do you ignore it?
1.6 General.Coverage
I think you can ignore it.
1.7 General.Structure
This element is implicit. I think that networked best suits a moodle course.
1.8 General.AggregationLevel
This element is implicit. We can use the value 3.
2.1 LifeCycle.Version
This data element is necessary but Im afraid you have to ask the author for it.
2.2 LifeCycle.Status
Why do you ignore this element?
I think it would be useful for a student searching for a course to know if the status of this course is draft, final, revised or unavailable.
2.3 LifeCycle.Contribute
at least one author -> Yes youre right!
In this case, 2.3.1 LifeCycle.Contribute.Role is implicit = author.
But you have to ask for 2.3.2 LifeCycle.Contribute.Entity element because the author can be different from the teacher stored in the moodle database.
Do you plan to use 2.3.3 LifeCycle.Date?
3.1 Meta-metadata.Identifier is implicit if you use an URI.
3.2 Meta-metadata.Contribute.
Most of application profiles use this element. You can easily know the user filling in the metadata.
3.3 Meta-metadata.MetadataSchema
Its implicit -> MoodleCore v1.0
3.4 Meta-metadata.Language
Same as 1.3
4.1 Technical.Format
What MIME type do you expect for a moodle course? 
4.2 Technical.Size
Maybe this element can be calculated.
4.3 Technical.Location
Ok for the URL
4.4 Technical.Requirement
4.5 Technical.InstallationRemarks
4.6 Technical.OtherPlatformRequirements
As Moodle can be used with most of Internet browsers, you can ignore these elements.
4.7 Technical.Duration
A moodle course is not a sound or a movie. You can ignore this element.
5.1 Educational.InteractivityType
A moodle course has a mixed interactivity type.
5.2 Educational.LearningResourceType
This element can be ignored. It doesnt fit with a moodle course.
5.3 Educational.Interactivity Level
With the social constructionist epistemology of teaching and learning, Im afraid we must use very high
5.4 Educational.SemanticDensity
Ok to ignore it.
5.5 Educational.IntendedEndUserRole
learner of course!
5.6 Educational.Context
The LOM value space is really poor for this element. We will have to define other vocabulary elements.
5.7 Educational.TypicalAgeRange
Ask the author
5.8 Educational.Difficulty
Is it useful in a social constructionist context?
5.9 Educational.TypicalLearningTime
5.10 Educational.Description
5.11 Educational.Language
Ok to ignore these elements.
6 Rigths category
Ok to ask the user to fill in these elements.
Why do you ignore the category 7. Relation?
It can be useful to tell the student that another course is required by the course he wants to study.
Ok to ignore the 8 Annotation category.
How will you use the 9 Classification category?
Best regards.