Design for simple application profiles Tom Baker and Karen Coyle - - PowerPoint PPT Presentation

▶
design for simple application profiles
SMART_READER_LITE
LIVE PREVIEW

Design for simple application profiles Tom Baker and Karen Coyle - - PowerPoint PPT Presentation

Dec 20, 2023 24 likes •319 views

Design for simple application profiles Tom Baker and Karen Coyle Dublin Core Metadata Initiative DCMI Application Profiles Application Profiles (1999): how metadata terms from different vocabularies are combined and constrained in

slide-1
SLIDE 1

Design for simple application profiles

Tom Baker and Karen Coyle Dublin Core Metadata Initiative

slide-2
SLIDE 2

DCMI Application Profiles

  • Application Profiles (1999): how metadata terms from

different vocabularies are combined and constrained in community-specific metadata

  • Description Set Profile Constraint Language (2008) -

“templates and constraints”

  • DCMI Application Profiles Interest Group - 2019
slide-3
SLIDE 3

Profile functions

  • For documenting community consensus
  • For data creation
  • For analyzing and validating data
  • For mixing/selecting data from different sources
  • For ingesting data from others
  • For retrieval or display of different views
slide-4
SLIDE 4

What is a profile?

Main Vocabulary Profil Main Vocabulary Profile Vocabulary

vocab

vocab

Profile Main

Profile

Profile

slide-5
SLIDE 5

DCMI AP Interest Group requirements

  • Use tabular format to help non-coders create simple

profiles

  • "Core"
  • Technology-agnostic concepts
  • Convertible into machine-actionable representations
  • Compatible with validation standards (ShEx, SHACL,

XML schemas…)

slide-6
SLIDE 6

Data template

Dublin Core AP Project

AP Template Profile Validation code

slide-7
SLIDE 7

Dublin Core AP Project

AP Template

slide-8
SLIDE 8

Common features of application profiles

  • Selected vocabulary terms
  • Constraints on terms (cardinality, rules)
  • Constraints on values
  • May have more than one entity
slide-9
SLIDE 9

How simple is simple enough? Too simple?

Entity Statement Value

slide-10
SLIDE 10

Dublin Core AP Project

AP Template Profile

slide-11
SLIDE 11

Sample profile

slide-12
SLIDE 12

Dublin Core AP Project

AP Template Profile Data template

slide-13
SLIDE 13

Possibly like ...

BOOK Author Title Date

slide-14
SLIDE 14

Defining values

slide-15
SLIDE 15

Value_type

Community-specific pick lists?

RDA DMP A B

uri URI URI string literal Literal date xsd:date date-time DateTime complex

nested data structure

entity

Entity_name

URIStem term controlled

vocabulary

slide-16
SLIDE 16

Value_type

Community-specific pick lists?

RDA DMP A B

uri URI URI string literal Literal date xsd:date date-time DateTime complex

nested data structure

entity

Entity_name

URIStem term controlled

vocabulary

slide-17
SLIDE 17

Value_type

Usable in conversion scripts

slide-18
SLIDE 18
slide-19
SLIDE 19

Dublin Core AP Project

AP Template Profile Validation code Data template

slide-20
SLIDE 20

Example: Wikidata entity schema from tabular profile

slide-21
SLIDE 21
slide-22
SLIDE 22
slide-23
SLIDE 23
slide-24
SLIDE 24
slide-25
SLIDE 25
slide-26
SLIDE 26

Lots of questions

  • How simple is too simple? How complex is too

complex?

  • Should we define a standard set of basic value types
  • r leave those to communities?
  • What parts of a profile need to be citably identified in
  • rder to be re-used within a profile?
slide-27
SLIDE 27

General conclusions

Many reasons, many requirements - hard to create a "universal" template Simple template is plausible, complex templates require specific user knowledge Basic guidelines for simple profiles would be helpful

slide-28
SLIDE 28

Links

  • http://dublincore.org/groups/application_profiles_ig/
  • https://github.com/dcmi/dcap
  • https://github.com/dcmi/dcap/tree/master/prototypes/
slide-29
SLIDE 29

Thank you

tom@tombaker.org kcoyle@kcoyle.net