Doron Shalvi e=
xpressed at the outset his recommendation and wish that the conversation wo=
uld continue at a time when Andrew Woods=
is available since he is likely to have valuable input on this question.=
li>
Nancy Fallgren summarized the main points of c=
oncern:=20
URIs should be resolvable HTTP URIs.
Using URLs rather than URIs is not a best prac=
tice (i.e. making statements in RDF that blur the line between web resource=
and real-world object).
IDs for abstract concepts are being minted by =
various groups and we need to be able to use those in the RDF published thr=
ough our Fedora instances.
Linked data is primarily for machines and not =
humans.
Currently NLM creates identifiers =E2=80=93&nb=
sp;referred to as permalinks =E2=80=93 to represent these real-world o=
bjects, but it would be difficult if not impossible to use these directly i=
n Fedora as it is currently defined.
Jared Whiklo s=
uggested that one way to talk about real world objects in a Fedora ecosyste=
m would be to use a triplestore alongside Fedora to store RDF about real wo=
rld objects.
Another option would be relaxing the single su=
bject restriction.
Aaron Birkland mentioned OAI-ORE's concept of a resource map as another =
helpful model to consider in this context.
This describes a method of keeping object and =
description separate and yet resolvable
Two methods are recommended for dealing with t=
his problem: hash URIs and a the 303 response (see other)
Aaron Birkland also expressed support for removing the single subject restriction
Danny Bernst=
ein raised the further issue noted in the mailing list thread of the qu=
estion of the appropria=
teness of RDF as a backend data storage format, and asked that this que=
stion be fleshed out.
One issue with RDF is scalability (large datas=
ets tend to balloon to millions and billions of triples rather quickly).
Aaron Birkland suggested that the question may really be about whether the web-based arc=
hitecture is appropriate.
restrictions on URI patterns creates a scalabi=
lity problem for users with large collections of materials
there is a need to make assertions/statements =
about things external to the repository and single subject makes it necessa=
ry to then bury the LDP server under other layers of infrastructure, which =
in turn calls into question the benefit of using Fedora
There seemed to be a consensus that the discus=
sion was valuable and needs to continue, particularly as we move toward fin=
alizing a version of the API specification.