Introduction to Application Profiles
Download as PPTX, PDF10 likes3,813 views
The document provides an overview of application profiles in the context of the semantic web, discussing their role in defining metadata, vocabularies, and the semantics of data descriptions. It emphasizes the importance of interoperability and the evolution of data management practices in a diverse data environment. Additionally, it outlines steps for creating application profiles and the benefits they bring to data documentation and sharing across communities.
![We can map it in a variety of ways for a variety of usesWe can still use MARC as a [lossy] exchange format as long as we need itIt offers insufficient flexibility as the basis for a new data world inter-connected to the WebWe can use our skills and our understanding of bibliographic description to lead the way forwardWhat About Our Legacy Data?1/18/201073CC:DA Application Profile Intro](https://image.slidesharecdn.com/ccdaapintro-100118100943-phpapp01/85/Introduction-to-Application-Profiles-74-320.jpg)
Introduction to Application Profiles
- 1. Jon Phipps: OverviewKaren Coyle: Step-by-StepDiane Hillmann: ContextApplication Profiles
- 2. What's an Application Profile?
- 3. What's an Application Profile?It's a document
- 4. What's an Application Profile?It's a document of an agreement
- 5. What's an Application Profile?It's a document of an agreement on a model
- 6. What's an Application Profile?It's a document of an agreement on a model of our stuff in the world
- 7. What's an Application Profile?It's a document of an agreement on a model of how we describe our things in our world
- 8. What's an Application Profile?It's a document of an agreement on a model of how we describe ourthings in our world (domain) in the context of the global web of data
- 9. Things?
- 10. Things?have a formal definition...
- 11. Things?have a formal definition...Every individual in the OWLworld is a member of the classowl:Thing.
- 12. OWL?
- 14. OWL?Web Ontology LanguageA language that can be used to formalize a domain by defining classes, the relations between them, and properties of those classes
- 15. OWLWeb Ontology Languagecan define the semantics of an Application Profile
- 16. Semantics?
- 17. Semantics?What we mean when we define a class called 'book' and describe it with a property called 'title’.
- 18. Semantics?What we mean when we define a class called 'book' and describe it with a property called 'title'.The 'Semantic Web' is a web of meaning that uses the RDF model
- 21. RDF?Resource Description Framework“is a framework for representing information in the Web”
- 22. RDF?“has a simple data model that is easy for applications to process and manipulate.”
- 23. RDF?“has a formal semantics which provides a dependable basis for reasoning about the meaning of an RDF expression.”
- 24. RDF?“URI references are used for naming all … things in RDF.”
- 25. RDF?“is an open-world framework that allows anyone to make statements about any resource.”
- 26. RDF?“The underlying structure of any expression in RDF is a collection of triples”
- 27. Triples?consist of a subject, a predicate and an object. A set of triples is called an RDF graph
- 28. Triples?consist of a resource, a property and a value surrogate.
- 29. Value Surrogate?Not a value, but some thing that denotes the value
- 30. Value Surrogate?can be a Literal or a non-Literal
- 31. Literal?Can be a Plain Literal or a Typed Literal
- 32. Plain Literal?Is just a string with an optional (in this case totally unnecessary) language typePlain Literal: “Samuel Clemens”@en-US
- 33. Typed Literal?A string that must be interpretedTyped Literal: “27” ^^xsd:integer
- 34. Typed Literal?A string that must be interpretedTyped Literal: “27” ^^xsd:integerdenotes the number 27
- 35. Non-Literal?A URI that refers to a resource
- 36. Non-Literal?http://RDVocab.info/termList/RDAContentType/1012Identifies the skos:Concept labeled“sounds”@en-USIn the skos:ConceptScheme identified by the URIhttp://RDVocab.info/termList/RDAContentType
- 38. URI?A globally unique resource identifier.“All URIs share the property that different persons or organizations can independently create them, and use them to identify things.”
- 39. Predicate?A URIthat identifies the property of the subjectof the triple
- 40. Predicate?“Since RDF uses URIs instead of words to name things in statements, RDF refers to a set of URIs (particularly a set intended for a specific purpose) as a vocabulary”
- 41. Property?http://RDVocab.info/Elements/placeOfProductionidentifies the property labeled“Place of production”in the vocabulary identified byhttp://RDVocab.info/Elements/
- 42. Property?A vocabulary can declare a property to be a subproperty of another property.
- 43. Property?A vocabulary can declare a property to be a subproperty of another property.This creates a formal relationship between the properties
- 44. Can we talk about APs now?Please?
- 45. An AP defines SemanticsThe Classes of resources your metadata is describing
- 46. The Vocabularies that you will use as properties to describe themClasses?OMGPlease, don’t start that again
- 47. An AP defines SyntaxValid value ranges and datatypes for each property
- 48. Valid lists of values (controlled vocabularies) for properties
- 49. Cardinality of each propertyAn AP defines SyntaxDublin Core defines this validation profile for each property as a“Statement Template”
- 50. An AP defines SyntaxA set of Statement Templates is a “Description Set”
- 51. An AP defines…An AP can describe multiple Description Sets.
- 52. An AP defines…An AP can describe multiple Description Sets.The full set of Description Sets is a “Description Set Profile”
- 53. Application ProfilesStep-by-Step1/18/201052CC:DA Application Profile Intro
- 54. 1. Domain modelPersonWEMITopicFRBR1/18/201053CC:DA Application Profile Intro
- 55. 2. Determine elementsWorkTitleFormatetc1/18/201054CC:DA Application Profile Intro
- 56. 3. Identify vocabularies1/18/201055CC:DA Application Profile Intro
- 57. Identify vocabularies1/18/201056CC:DA Application Profile Intro
- 58. Identify vocabularies1/18/201057CC:DA Application Profile Intro
- 59. Vocabulary do's & don'tsDo not select elements based on their names or labelsDo select elements based on their definitionsDo pay attention to what values can be usedDon't think that you can select an element that doesn't quite match your need, and use it anywayDo think: INTEROPERABILITY1/18/201058CC:DA Application Profile Intro
- 60. One vocabularyVocabularyAP1/18/201059CC:DA Application Profile Intro
- 61. More than one vocabularyVocabulary AVocabulary BAP1/18/201060CC:DA Application Profile Intro
- 62. Rolling your ownVocabularyAP1/18/201061CC:DA Application Profile Intro
- 63. Rolling your ownVocabularyAll elments must be defined outside of the AP. AP1/18/201062CC:DA Application Profile Intro
- 64. "Constraints"Mandatory/optionalRepeatabilityValues (cannot conflict with defined element)Free textControlled list of valuesFormatted text (e.g. dates)1/18/201063CC:DA Application Profile Intro
- 65. What is the impact of all this on our world?The Context for Application Profiles
- 66. In the world we knew, interoperability was ensured by “compliance with standards”All of used the same ones in a closed worldData created by humans under strict guidelinesIn an open world, interoperablity depends on:Technologies that reach beyond one communityData built in a variety of ways by people with different ideas of the worldMachines that act broadly based on human oversightUnderstanding Interoperability1/18/201065CC:DA Application Profile Intro
- 67. We’ve long accepted the limits of requiring upfront consensus to ensure interoperabilityIn a world of APs we can specialize beyond the core of generally useful dataWe don’t need humans to ‘dumb down’ specialist data to enable sharing and interoperabilityMachines can invoke relationships to generalize specialist data when necessary, without removing the value of extended specialized data for specialistsWhy This Approach Instead?1/18/201066CC:DA Application Profile Intro
- 68. We can’t afford to “go it alone”We can’t afford to ignore the world of data outside librariesWe can’t afford to create all our data with humansWe can’t afford NOT to rethink how we operateThe Value of an Open World1/18/201067CC:DA Application Profile Intro
- 69. It’s often free and easily availableIt’s ‘good enough’ (our stuff isn’t perfect either)It takes us where we can’t go with our current dataIt’s maintained by someone else We can choose to use data or not, APs allow us to document that use, automate the process, and expose the data to othersWhat’s Out There? Data!1/18/201068CC:DA Application Profile Intro
- 70. Records can be aggregated from statements when we need themStatement-based data can be managed and improved more easily than record-based dataStatement-based data can carry provenance for each statement, allowing quality decisions to be made at a more granular levelChanging Our Data Management Ideas1/18/201069CC:DA Application Profile Intro
- 71. Getting From Here to There1/18/201070CC:DA Application Profile Intro
- 72. The RDA VocabulariesThe principles of extension inherent in the RDF Vocabulary standards usedOur experience in building and using dataUsing What We Already Know1/18/201071CC:DA Application Profile Intro
- 73. Proliferating our ideas and experience with bibliographic data to the broader Web worldUsing newer technology to achieve more efficiency, transparency, and functionalityIf retrenchment is the only answer, the end point is zeroSaving our precious human resources to think, evaluate, ensure quality, and innovateTo Build Ourselves a New Future1/18/201072CC:DA Application Profile Intro
- 74. We can map it in a variety of ways for a variety of usesWe can still use MARC as a [lossy] exchange format as long as we need itIt offers insufficient flexibility as the basis for a new data world inter-connected to the WebWe can use our skills and our understanding of bibliographic description to lead the way forwardWhat About Our Legacy Data?1/18/201073CC:DA Application Profile Intro
- 75. Specialist communities are already thinking about what they need that RDA doesn’t provideUsing the extensibility of RDF vocabularies allows them to choose from a number of options Moving proposals through the RDA processExtending the vocabularies through their community domainChosing the extension option reflects the reality that consensus has its limits, and specialist data may be better managed at a different levelSome Concrete Suggestions1/18/201074CC:DA Application Profile Intro
- 76. With Application Profiles we can:Document our decisions clearlyMeasure compliance with our own intentionsExpress our decisions in a machine-actionable wayMake connections with other data communities by re-using their data semanticsRDA expresses this ideal in its stated goalsWhat Do We Gain?1/18/201075CC:DA Application Profile Intro
- 77. Less one-at-a-time creation and more data design, data improvement, data evaluationAbility to look at our contrained resources and reduced budgets as the opportunity to reinvent ourselvesRethinking Our Role1/18/201076CC:DA Application Profile Intro
- 78. Guidelines for Dublin Core Application Profileshttp://dublincore.org/documents/profile-guidelines/RDA Vocabularieshttp://metadataregistry.org/rdabrowse.htmThanks! Links! Questions?1/18/201077CC:DA Application Profile Intro