Skip to content

Draft note about metadata in FILEs - #780

Open
tychonievich wants to merge 3 commits into
mainfrom
note-metadata
Open

Draft note about metadata in FILEs#780
tychonievich wants to merge 3 commits into
mainfrom
note-metadata

Conversation

@tychonievich

Copy link
Copy Markdown
Collaborator

Resolve #779

I'm not sure that this is the right text; edits welcome.

I chose to make most of this addition normative because I think we want to make recommendations, not just alert readers to a topic of possible interest.

Resolve #779

I'm not sure that this is the right text; edits welcome.

I chose to make most of this addition normative because I think we want to make recommendations, not just alert readers to a topic of possible interest.
Comment thread specification/gedcom-3-structures-3-meaning.md Outdated
which may be of value to family history work.
Applications should not to remove or edit metadata except as requested by the user.
Applications are encouraged to show the metadata in referenced external files to the user
and provide ways of integrating that metadata into appropriate structures with user guidance.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we say anything more about what is "appropriate"? E.g., could we have a table of metadata item <-> appropriate GEDCOM structure?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we realistically can. There are hundreds of metadata tags defined in multiple standards and some evidence that common applications have their own de facto standard way of using tags that differs from those standards.

Even were that not the case, it's still not clear where data goes. Consider the dc:title metadata field of some_image.jpg used in the following way:

0 @I1@ INDI
1 SOUR @S1@
0 @S1@ SOUR
1 OBJE @O1@
0 @O1@ OBJE
1 FILE some_image.jpg

That dc:title might belong in any of the following places:

0 @I1@ INDI
1 SOUR @S1@
1 NAME maybe goes here (1)
1 NOTE maybe goes here (2)
0 @S1@ SOUR
1 OBJE @O1@
2 TITL maybe goes here (3)
1 TITL maybe goes here (4)
1 NOTE maybe goes here (5)
0 @O1@ OBJE
1 FILE some_image.jpg
2 TITL maybe goes here (6)
1 NOTE maybe goes here (7)

I don't think an application can pick a correct location without human help, hence the "with user guidance" part of the proposed text.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. I think explaining that in a note (maybe using a subset of the example that shows 2 or 3 places something could go) would help the reader understand what "with user guidance" means.

Co-authored-by: Dave Thaler <dthaler1968@gmail.com>
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

Successfully merging this pull request may close these issues.

Add note about Metadata in Media Files

2 participants