[{"data":1,"prerenderedAt":130},["ShallowReactive",2],{"glossary-sml":3},{"id":4,"title":5,"body":6,"description":119,"extension":120,"lastUpdatedAt":121,"letter":122,"meta":123,"navigation":124,"path":125,"seo":126,"stem":127,"summary":128,"term":16,"__hash__":129},"glossary\u002Fglossary\u002Fsml.md","Sml",{"type":7,"value":8,"toc":113},"minimark",[9,29,32,72,75,80],[10,11,12,13,17,18,23,24,28],"p",{},"The ",[14,15,16],"strong",{},"SML"," (Service Metadata Locator) is the central DNS-based directory of the ",[19,20,22],"a",{"href":21},"\u002Fglossary\u002Fpeppol","PEPPOL"," network. Its job is simple: given a PEPPOL participant ID, tell the sender which ",[19,25,27],{"href":26},"\u002Fglossary\u002Fsmp","SMP"," (Service Metadata Publisher) holds that participant's routing metadata.",[10,30,31],{},"The SML doesn't store routing details itself — it only stores a pointer to the right SMP. The full lookup chain works like this:",[33,34,35,48,54,65],"ol",{},[36,37,38,39,42,43,47],"li",{},"Sender has the receiver's ",[14,40,41],{},"PEPPOL ID"," (e.g. ",[44,45,46],"code",{},"0184:CHE123456789",")",[36,49,50,51,53],{},"Sender queries the ",[14,52,16],{}," (DNS lookup) → gets the hostname of the receiver's SMP",[36,55,56,57,59,60,64],{},"Sender queries that ",[14,58,27],{}," → gets the receiver's ",[19,61,63],{"href":62},"\u002Fglossary\u002Faccess-point","access point"," endpoint URL and supported document types",[36,66,67,68],{},"Sender delivers the document directly to that access point via ",[19,69,71],{"href":70},"\u002Fglossary\u002Fas4","AS4",[10,73,74],{},"This design means no central message broker is involved — once the lookup is done, document exchange is point-to-point between access points. The SML just makes discovery possible without a central routing hub.",[76,77,79],"h3",{"id":78},"key-facts","Key facts",[81,82,83,91,94,97,103],"ul",{},[36,84,85,86,90],{},"Operated by: ",[19,87,89],{"href":88},"\u002Fglossary\u002Fopenpeppol","OpenPEPPOL"," (and mirrored by the European Commission for EU public procurement)",[36,92,93],{},"Technology: DNS — participant IDs are hashed and resolved as DNS hostnames",[36,95,96],{},"Role: pointer directory only — stores SMP location, not routing data",[36,98,99,100,102],{},"Works with: ",[19,101,27],{"href":26}," (which holds the actual endpoint data)",[36,104,105,106,109,110,47],{},"PEPPOL ID format used in lookups: scheme + ",[44,107,108],{},"::"," + value (e.g. ",[44,111,112],{},"0184::CHE123456789",{"title":114,"searchDepth":115,"depth":115,"links":116},"",2,[117],{"id":78,"depth":118,"text":79},3,"The SML (Service Metadata Locator) is the central DNS-based directory of the PEPPOL network. Its job is simple: given a PEPPOL participant ID, tell the sender which SMP (Service Metadata Publisher) holds that participant's routing metadata.","md","2026-04-21","S",{},true,"\u002Fglossary\u002Fsml",{"description":119},"glossary\u002Fsml","Service Metadata Locator — the DNS-based PEPPOL directory that tells senders which SMP manages a given participant's routing data.","By1DvXb-dGJ0o8UOg578-nnaUqj8alkN3hrScr5A4Rs",1776886794417]