Type of respons from Adlib/Axiell API (split from #9)

[ivozandhuis]

@RolfBly asked

<person>
  <name>Rietveld, Gerrit</name>
  <role>creator</role>
  <source>VIAF</source>
  <source>RKD Artists</source>
  <number>https://viaf.org/viaf/15562113/</number>
  <number>https://rkd.nl/nl/explore/artists/66880</number>
  <license/>
  <license>CC-BY</license>
</person>

"If the above is what you'd get from an Adlib/Axiell API, you can transform it using XSLT, server-side. You could configure the API so that it responds with something compliant with schema.org, or turtle. That being the case, which format(s) would best suit LOD usability?"

[ivozandhuis]

There is a difference between the 'fields' (eg schema.org) that you define in your RDF respons and the 'serialization' (eg turtle) that you choose. The first is described in section 1.1 and the second in section 1.2. For short: an RDF respons with schema.org properties and classes might be in RDF/XML or turtle and the other way around, an RDF respons in turtle might have schema.org or CIDOC-CRM properties and classes.

Because the Adlib API is based on XML and XML-transformation the most practical serialization is RDF/XML. In this gitrepo basic XSLT-stylesheet are available for transforming AdlibXML from a standard installation into the RDF/XML serialization. Transformations are available into Dublin Core, schema.org, EDM and linked art (for a practical use of this last standard see this gitrepo.

@RolfBly Do the texts in sections 1.1 and 1.2 help you on this subject? If not, could you help us by explaining what we could improve?

[RolfBly]

Thanks for now, I'll review the sections & come back.