You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

  1. Your Fedora repository is a part of the Web
    1. What are the special qualities of your part of the Web?
      1. Durability
      2. Connections to the community you serve
    2. What qualities does your part of the Web share with the rest of the Web?
      1. HTTP, RDF, and RFDS/OWL/SKOS as common "languages"
  2. Good choices for syntax and semantics help us support our values
    1. We're interested in durability
      1. For syntax, that means sharing your syntax with a big community
      2. For semantics, that means making your semantics intelligible broadly
    2. We're interested in extensibility
      1. Extensible syntax is minimal but powerful
      2. Extensible semantics choose for open assumptions like OWA and against global conditions like UNA
    3. We're interested in interoperability
  3. Make thoughtful commitments
    1. Your commitment to Fedora appears in:
      1.  the way you manage your resources with respect to persistence, fixity, other low-level technical aspects
    2. Your commitment to the specific communities you serve appears in:
      1. what your resources mean (the ontologies you use to do content modeling) and
      2. your workflows, which are useful to the members of your communities.
  4. What does this look like in practice?
    1. Fedora is an object repository, not a triple store
      1. Only put things in your Fedora repository for which only you are responsible
        1. For things for which the communities you serve are responsible, put them in other places (e.g. triple stores)
      2. Don't architect so that your repository is made responsible for anything other than the durability of your own stuff
        1. Don't provide discovery services directly over Fedora (don't use Fedora as an index)
    2. Choosing common vocabularies (common semantics) lets us share work with the communities that use those vocabularies
      1. MeSH example
    3. Choosing common ontologies (common semantics) lets us share work with the communities that see the world that same way
      1. Inferencing example using Plant Ontology
  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.