Integration: verschil tussen versies

Integration
Geen bewerkingssamenvatting
k (Tekst vervangen - "|Producttype=" door "|Lid van=")
 
Regel 5: Regel 5:
|Label (en)=Integration
|Label (en)=Integration
|Toelichting (en)=We have seen a trend 15-20 years ago that we moved from file-based integration towards more message-based integration (using fixed, inflexible XML data structures that were expensive and hard to maintain) and now we see a trend from message-based integration towards more resource-based integration (using more flexible and possibly more open data structures that are more cost efficient and that can be maintained in a uniform way using RDF-based standards with less data duplication)
|Toelichting (en)=We have seen a trend 15-20 years ago that we moved from file-based integration towards more message-based integration (using fixed, inflexible XML data structures that were expensive and hard to maintain) and now we see a trend from message-based integration towards more resource-based integration (using more flexible and possibly more open data structures that are more cost efficient and that can be maintained in a uniform way using RDF-based standards with less data duplication)
|Producttype=Overig
|Lid van=Overig
|Smaller=Frontend integration,Backend integration,Process integration,Application integration,Data integration,File-based integration,Message-based integration,Resource-based integration
|Smaller=Frontend integration,Backend integration,Process integration,Application integration,Data integration,File-based integration,Message-based integration,Resource-based integration
}}
}}

Huidige versie van 21 feb 2020 om 13:27

 
Expert Finding.jpg
Expertise

Eigenschappen

Label (nl)Integratie
Label (en)Integration
Toelichting (en)We have seen a trend 15-20 years ago that we moved from file-based integration towards more message-based integration (using fixed, inflexible XML data structures that were expensive and hard to maintain) and now we see a trend from message-based integration towards more resource-based integration (using more flexible and possibly more open data structures that are more cost efficient and that can be maintained in a uniform way using RDF-based standards with less data duplication)

Relaties

VertrekpuntRelatieEindpunten
IntegrationLid van
IntegrationSmaller
  • Frontend integration (Let op: pagina bestaat niet.)
  • Backend integration (Let op: pagina bestaat niet.)
  • Process integration (Let op: pagina bestaat niet.)
  • Application integration (Let op: pagina bestaat niet.)
  • Data integratie (Expertise)
  • File-based integration (Let op: pagina bestaat niet.)
  • Message-based integration (Let op: pagina bestaat niet.)
  • Resource-based integration (Let op: pagina bestaat niet.)

Afgeleide relaties

VertrekpuntRelatieEindpunt
Data integratie (Expertise)BrederIntegration





Rdf.jpg
Overgenomen van "https://www.pldn.nl/index.php?title=Integration&oldid=19476"

De activiteiten van Platform Linked Data Nederland (PLDN) worden mede mogelijk gemaakt dankzij het Kadaster, TNO, Big Data Value Center (BDVC), ECP, Forum Standaardisatie, Kennisnet, SLO, Waternet, Taxonic, MarkLogic, Triply, Franz Inc., SemmTech, Rijksdienst voor het Cultureel Erfgoed (RCE), Beeld en Geluid, EuroSDR, de KVK en ArchiXL

Nieuwsbrief

Wilt u op de hoogte gehouden worden van nieuws en ontwikkelingen binnen PLDN?

Schrijf u dan in voor de nieuwsbrief

Mogelijk gemaakt door

Leden