Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: Fedora 4.5.1
    • Fix Version/s: Fedora 5.0.0
    • Component/s: f4-core
    • Labels:
    • Roadmap Theme:
      API Specification
    • Sprint:
      Sprint 2017 - 19

      Description

      Currently, an LDP-NR is created whenever:
      a) content-type of a POST or PUT request is not RDF
      or
      b) Content-Disposition: attachment header is present

      At present, this is not codified in the specification draft doc:
      https://docs.google.com/document/d/1ad3MhTQWGof0IJ03yY5jVofCK8uO9yPKMVXVYq7a44o/edit#

      The LDP spec is fairly silent about when a repository should create an LDP-NR. This ticket is to see if there is a better way (possibly leveraging LDP headers) to explicitly convey a client's intent that a given resource should be created as a LDP-NR, and incorporate the conclusion into the spec draft.

      A case to consider is persisting an arbitrary RDF document (e.g. an owl document, RDF-based dataset, etc) as a binary resource in Fedora with an rdf media type. This case precludes (a) from the above techniques for specifying binary resource creation.

      See discussion in https://github.com/fcrepo4/fcrepo4/pull/1081

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              birkland Aaron Birkland
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: