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

Compare with Current View Page History

« Previous Version 12 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 particular communities 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"
    3. 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. HTTP does this.
        2. For semantics, that means sharing your semantics with a community committed to the same worldview. RFDS/OWL/SKOS help with this.
          1. More and more communities are publishing their common semantics in these languages. Can you think of some in use for your community?
      2. We're interested in extensibility
        1. Extensible syntax is minimal but powerful. RDF is this.
        2. Extensible semantics choose for open assumptions like OWA and against global conditions like UNA.
      3. We're interested in interoperability.
        1. Common syntax is completely necessary to interoperability.
        2. Common semantics lowers the cost of interoperability.
  2. Relationships to Fedora 3 concepts
    1. Fedora 3 content modeling did a lot of things at once!
      1. Ontology
      2. Workflow
      3. Validation
    2. Where do these functionalities go in Fedora 4?
      1. Ontology
      2. Workflow
        1. Outside the repository, at least in most circumstances
        2. Apache Camel now under extensive investigation
      3. Validation
        1. Suggestions?
  3. Make thoughtful commitments
    1. Your commitment to Fedora appears in:
      1.  the way you manage your resources with respect to persistence, fixity, and other low-level technical aspects.
    2. Your commitment to the specific communities you serve appears in:
      1. what your resources mean (the vocabularies and 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 or general semantic 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, Linked Data caches)
          1. Common vocabularies. What such vocabularies are you using now? Where are you storing or caching them?
          2. Common ontologies.
          3. Authorized facts (e.g. personal or corporate authority information).
      2. Don't build 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. Don't use your repository to manage information that is ultimately transactional. E.g.,
          1. Identity management, groups management
          2. Workflow state a la Stanford "robot" systems (maybe an edge case)
    2. Choosing common vocabularies (common semantics) lets us share work with the communities that use those vocabularies
    3. Choosing common ontologies (common semantics) lets us share work with the communities that see the world that same way
  • No labels

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