Coder Social home page Coder Social logo

gedcomx-citation's People

Contributors

stoicflame avatar

Stargazers

 avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

gedcomx-citation's Issues

Citation templates are none of GedcomX's business.

Citation templates are about displaying citation information in reference notes and bibliographies: They're the province of applications. GedcomX's mission is about passing information, including citation information, between applications, so our concern should be with the citationFields and we should leave citation templates to projects like Citation Style Language.

Bibliographic Metadata vs. Citation: What is the goal?

Consider the following:

  1. A citation is a representation of bibliographic metadata.
  2. The same bibliographic metadata represented as a list fields is NOT a citation.

If both of these statements are true, I have (at least) the following question:

What is it that GEDCOM X hopes to be able to exchange: bibliographic metadata or citations?

Asked another way, what if the model only supported the exchange of bibliographic metadata and not citations? Would that be sufficient? A model with a bibliographic metadata mechanism and no citation mechanism? It seems that, for some, this is all that is required.

Or what about a hybrid scenario? GEDCOM X already specifies a citation exchange mechanism. If we added a mechanism for representing bibliographic metadata in a fielded, semantic way and left the current citation mechanism in place, but assumed that the bibliographic metadata may only be partial and (in isolation) insufficient to represent a citation, would we have sufficient functionality?

Or is GEDCOM X required to exchange bibliographic metadata AND all the semantical information required to be able to form citations via automation? No. I am not suggesting the transmission of styling or formatting. I am talking about sending enough semantical information that the relationships among the various bibliographic metadata items are well understood (e.g., any hierarchies are apparent, etc.) and automation becomes possible.

Doesn't MARC do what we need?

The US Library of Congress has developed a widely used standard for storing bibliographic information called MARC, including an XML serialization. This standard is used by, among many others, OCLC, the parents of WorldCat.

Doesn't that meet the needs of GedcomX for specifying the citationField information? Why reinvent the wheel?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.