Skip to content

Determine preferred encoding format for document-level metadata #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
WaxCylinderRevival opened this issue Oct 7, 2016 · 2 comments

Comments

@WaxCylinderRevival
Copy link
Owner

WaxCylinderRevival commented Oct 7, 2016

For now, suggestions and issues refer to possible TEI construction

http://www.tei-c.org/release/doc/tei-p5-doc/en/html/index.html

@WaxCylinderRevival
Copy link
Owner Author

WaxCylinderRevival commented Oct 22, 2016

@joewiz pointed to <xenoData>, which may be used as a container for non-TEI formats in the <teiHeader>: http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-xenoData.html

Possible non-TEI encoding formats for FRUS document-level metadata include:

  • Dublin Core
  • MARCXML
  • EAD
  • MODS
  • RDF

@WaxCylinderRevival
Copy link
Owner Author

WaxCylinderRevival commented Oct 24, 2016

Per today's conversation with @joewiz, place item-level metadata (document, editorial note, attachment) in FRUS-namespace XML wrapper and use elements of different namespaces to capture the most robust metadata in the most appropriate metadata standard. For instance, we'd likely use <tei:date from="" to="" notBefore="" notAfter="" when=""> but perhaps add <ead:genreform> and <dc:isPartOf> elements.

I suggest <frus:itemMetadata> as wrapper element for flexibility and to avoid confusion with the FRUS-specific concept of a "document."

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

No branches or pull requests

1 participant