Re: One example

Hi Karen,

walking through the requirements there appear to be some duplicates 
(apologies if I misunderstand them):

Duplicate 1:

  * #1 For every CulturalHeritage object (CHO) the URI of the
    ProvidedCHO and the URI described in edm:aggregatedCHO must be the same

  * #6 Each EDM CHO must have exactly one instance of rdf:type
    edm:ProvidedCHO and one instance of rdf:type ore:Aggregation
    (DC:R-225) (W3:R-6) (W3:R-12.2)

Duplicate 2 (maybe subtle differences, hard to understand for me):

  * #2 For every CHO or ore:Proxy dc:coverage or dc:subject or dc:type
    and dcterms:spatial; dc:language for text,dc:title or
    dc:description, must be present (DC:R-68) (W3:R-5.2)
  * #13 if edm:ProvidedCHO or ore:Proxy is present, at least one
    dc:title or dc:description should be present, one dc:subject or
    dc:type or dc:coverage or dcterms:spatial and edm:type should be
    present (DC:R-71) (W3:R-6) (W3:R-6.2) (W3:R-6.7)
  * #14 For each edmProvidedCHO or ore:Proxy (provider proxy)
    dc:coverage or dc:subject or dc:type or dcterms:spatial,dc:language
    (for text objects), dc:title or dc:description or edm:type must be
    present (DC:R-67) (W3:R-6.2) (W3:R-6.7)

Duplicate 3:

  * #3 We must have only one PrefLabel per language. Ideally the
    language tag should be present (DC:R 49) (W3:R-6.4)
  * #5 We must have only one PrefLabel per language. Ideally the
    language tag should be present (DC:R 49) ((W3:R-6.4)


Some more questions:

- For #8 "Check that the edm:hasView, edm:isShownBy and edm:object 
resolves to a media", does this mean that the values of those properties 
must have a certain rdf:type (e.g. edm:WebResource) or does it mean that 
the system shall do a web look-up to check for a valid HTTP response?

- The page at "#9 The value of edm:rights must come from the list at 
http://pro.europeana.eu/web/available-rights-statements" only seems to 
contain HTML - is there an RDF version that lists the valid values? How 
else can this be checked?

Thanks
Holger


On 5/17/2015 13:03, Karen Coyle wrote:
> OK, the example should work now -- at least, it passes validation in 
> the RDF validator and rapper. It appears to have 3 "records" worth of 
> data, so there are multiple "outer" graphs. If that's a problem, I can 
> reduce it down to a single "outer" graph.
>
> kc
>
> On 5/16/15 7:20 PM, Karen Coyle wrote:
>> OK, I'll see if I can find anyone who can answer that, since this isn't
>> my data. I'm thinking there's something basic going wrong - such as the
>> software not finding the ontology.
>>
>> Meanwhile, here's the link to the latest version of the ontology:
>> https://github.com/europeana/corelib/blob/master/corelib-edm-definitions/src/main/resources/eu/rdf/edm-v524-130522.owl 
>>
>>
>>
>> I'll try to get back to you soon.
>> kc
>>
>> On 5/16/15 5:05 PM, Holger Knublauch wrote:
>>> Also, the RDF/XML file
>>>
>>> http://kcoyle.net/temp/EDMvalidexamples.xml
>>>
>>> doesn't seem to be parse, and produces many errors, see
>>>
>>> http://www.w3.org/RDF/Validator/rdfval?URI=http%3A%2F%2Fkcoyle.net%2Ftemp%2FEDMvalidexamples.xml&PARSE=Parse+URI%3A+&TRIPLES_AND_GRAPH=PRINT_TRIPLES&FORMAT=PNG_EMBED 
>>>
>>>
>>>
>>>
>>> Holger
>>>
>>>
>>> On 5/17/2015 8:02, Karen Coyle wrote:
>>>> In case anyone wants a real example to work with, I have created a
>>>> short page that lists the requirements and the file of data those
>>>> requirements pertain to. The requirements themselves are also embedded
>>>> in the XML file so you can see what graph they are associated with.
>>>>
>>>> http://kcoyle.net/temp/EDMvalidReqs.html
>>>>
>>>> While it may be the case that no one wants to tackle this at this
>>>> time, it does include some common use cases. The list includes both DC
>>>> and SHACL requirements numbers, and links to the spreadsheet with DC
>>>> requirements, that then in turn links to further information.
>>>>
>>>> kc
>>>
>>>
>>>
>>
>