Architecture as Linked Data
Download as PPTX, PDF•0 likes•265 views
The document discusses the concept of architecture as linked data, emphasizing the importance of using linked data vocabularies for increased accessibility and clarity in architectural communication. It critiques the ArchiMate specification, highlighting its vagueness, and presents the European Interoperability Reference Architecture as an example of effective interoperability. The document concludes that publishing architecture as linked data can enhance understanding and facilitate reuse of architectural elements.
Architecture as Linked Data
- 1. Architecture as Linked Data Danny Greefhorst
- 2. Agenda • Why Architecture as Linked Data • Demonstrator Architecture as Linked Data • Linked Data vocabularies for Architecture als Linked Data • Example: European Interoperability Reference Architecture
- 3. Problem: what is a data object? ArchiMate specification: • “A data object represents data structured for automated processing.” • “A data object should be a self-contained piece of information with a clear meaning to the business, not just to the application level. Typical examples of data objects are a customer record, a client database, or an insurance claim.” In ArchiMate you can apparently call a lot of different things a data object. What exactly you mean by that remains unclear. If you are working with data, you would like to distinguish between more specific data objects such as record, database, document, dataset, distribution, catalog
- 4. Architecture content also needs to be FAIR https://www.go-fair.org/fair-principles/
- 5. Architecture intrinsically is about cohesion and as such about relationships and linking
- 6. Why Architecture as Linked Data? • ArchiMate definitions are abstract and leave a lot of room for interpretation • Specific Linked Data vocabularies offer more specific meanings • It is important to publish architecture in an accessible way • Linked Data is specifically aimed at publishing in an accessible manner via the web • ArchiMate requires specific knowledge of architectural concepts • Linked Data vocabularies use concepts that are more widely recognized and used • ArchiMate models can only be used in architecture tools • There are many different tools for Linked Data • ArchiMate standardizes only types and no properties • Specific Linked Data vocabularies also standardize the properties of types • ArchiMate specifies and relates only architecture elements • Linked Data makes it possible to capture and connect all data elements
- 7. ArchiMate2RDF https://github.com/bp4mc2/archimate2rdf Linked Enterprises: deriving a hypermodel from ArchiMate https://www.linkedin.com/pulse/from-archimate-language- web-ontology-dr-nicolas-figay Experimentation on OWL derivations https://github.com/nfigay/archimate.owl OWL Exchange Plug-in for Archi https://github.com/archimatetool/OWLExchange How to export Archi(mate) file into RDF or OWL https://forum.archimatetool.com/index.php?topic=309.0 Using RDF/OWL to analyse ArchiMate models https://groups.google.com/forum/#!topic/open-archimate- forum/poUR2BRqve0 ArchiMate TTL https://github.com/ikm- group/ArchiMEO/blob/master/ARCHIMEO/ARCHIMATE/ArchiM ate.ttl Linked Data representations of ArchiMate based on: https://github.com/bp4mc2/archimate2rdf
- 9. Extensions to archimate2rdf • Creation of URI's that are dereferenceable • Promotion of Linked Data properties in ArchiMate (that start with "http" or contain a ":") to true RDF properties • Inclusion of namespaces of a number of popular vocabularies, allowing shorthand reference in ArchiMate properties or their values • The option to generate a SKOS enriched version of the model • Translation of model metadata to a SKOS ConceptScheme • The option to refer to images, generated by Archi, in SKOS output • Translation of views to SKOS concepts • Generation of SKOS Collections for all ArchiMate concepts in ArchiMate ontology • Inclusion of ArchiMate definitions in ArchiMate ontology.ttl
- 10. Enrich ArchiMate with semantics
- 16. Architecture as Linked Data in the DERA https://dera.netwerkdigitaalerfgoed.nl/index.php/Begrippenlijst
- 17. WikiXL - SemanticWiki as Linked Data editor
- 19. ArchiMate elements expressed with schema.org Person, Organization HowTo Organization Role Service Product DigitalDocument Order Class, DefinedTerm Event Software Application Dataset, DataDownload, DigitalDocument WebPage, Software SourceCode WebAPI Place, GeoShape Consortium material operatingSysten device WebAPI
- 20. ArchiMate elements expressed with schema.org Place, GeoShape Consortium Order Event WebAPI material device operatingSysten WebAPI Software Application Person, Organization Product Service Dataset, DataDownload, DigitalDocument HowTo DigitalDocument Class, DefinedTerm WebPage, Software SourceCode Organization Role
- 22. ArchiMate elements expressed with other vocabularies SKOS System Connection Connection Connection Connection ConnectionPoint ConnectionPoint Connection System Device Device System FRBR Concept FOAF Concept Place Expression, Work Equipment Object Object Event DCAT Document Dublin Core Dataset Distribution DataService BibliographicResource CIDOC CRM gist Material PhysicalThing SEAS Agreement Event Function Network Link System Network Node Person, Agent Person, Group Person, Organization Place Function Artifact
- 23. ArchiMate elements expressed with popular vocabularies System Connection Connection Connection ConnectionPoint ConnectionPoint Connection System System Device System Concept Concept Equipment Object DataService Material PhysicalThing Consortium Order WebAPI material Device Object device operatingSystem WebAPI Software Application Product Service Expression, Work Dataset Dataset HowTo Document Distribution BibliographicResource DigitalDocument Class, DefinedTerm WebPage, Software SourceCode OrganizationRole Agreement Event Event Concept Function Connection Network Link Network Node SKOS FRBR FOAF DCAT Dublin Core CIDOC CRM SEAS Schema.org gist Person, Agent Person, Group Person. Organization Person, Organization Place Place, GeoShape Place Function Artifact
- 24. European Interoperability ReferenceArchitecture The European Interoperability Reference Architecture (EIRA©) is a reference architecture for delivering interoperable digital public services across borders and sectors Focus is on interoperability Aligned to the EIF and TOGAF®, uses SOA and ArchiMate® Structure Products Defines concepts as Architecture Building Blocks (ABBs) ABBs organised in four views (Legal, Organisational, Semantic, Technical) Solution Architecture Templates (SATs) to model requirements • HL*: IoP goals and principles • DL*: Specifications per ABB Solution models * High-Level (HL), Detail-Level (DL)
- 25. EIRA © structure EIF Framework and principles EIRA© Implementation guidelines and specifications Legal Organisational Semantic Technical
- 29. ADMS lowers interoperability barriers & facilitates reuse
- 31. The number of solutions per EIRA© architecture building block (1) PREFIX dcat: <http://www.w3.org/ns/dcat#> PREFIX dct: <http://purl.org/dc/terms/> PREFIX skos: <http://www.w3.org/2004/02/skos/core#> SELECT ?eira_abb_name count(?solution) as ?number_solutions WHERE { ?solution a dcat:Dataset . OPTIONAL { ?solution dct:type ?eira_abb_uri . ?eira_abb_uri skos:prefLabel ?eira_abb } BIND ( IF( BOUND(?eira_abb), ?eira_abb, "No ABB linked!" ) AS ?eira_abb_name) } GROUP BY ?eira_abb_name ORDER BY DESC(?number_solutions) https://joinup.ec.europa.eu/collection/joinup/technical-documentation
- 32. The number of solutions per EIRA© architecture building block (1)
- 33. Conclusions • Architecture should be published as Linked Data • You can enrich ArchiMate with Linked Data vocabularies • You can also decide to model architectures with just Linked Data vocabularies • There are already a number of architectures published as Linked Data