Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SAAM LOD link should be owl:sameAs #24

Open
VladimirAlexiev opened this issue Mar 31, 2017 · 1 comment
Open

SAAM LOD link should be owl:sameAs #24

VladimirAlexiev opened this issue Mar 31, 2017 · 1 comment

Comments

@VladimirAlexiev
Copy link
Member

VladimirAlexiev commented Mar 31, 2017

<http://data.americanartcollaborative.org/saam/object/id/2> foaf:homepage	
  <http://americanart.si.edu/collections/search/artwork/?id=2>,
  <http://edan.si.edu/saam/id/object/1973.28.2>.

The first is a web homepage. But the second is not, it's the object represented as LOD.
It has just the same stature as http://data.americanartcollaborative.org/saam/object/id/2.

So, change the RDF to this:

<http://data.americanartcollaborative.org/saam/object/id/2>
   foaf:homepage <http://americanart.si.edu/collections/search/artwork/?id=2>;
   owl:sameAs <http://edan.si.edu/saam/id/object/1973.28.2>.

To @workergnome You argued elsewhere this may mix the AAC and the SAAM data. It would only if you load them to the same repo and apply smushing. To prevent this, we must say that http://data.americanartcollaborative.org/saam/object/id/2 is not E22_MMO but is a foaf:Document describing the E22_MMO... which we are not prepared to do now.

@workergnome
Copy link

This is probably part of a larger, longer discussion about how to best work with external linked data, which I think we're going to have to have as we start integrating the reconciled LOD.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants