{"id":104601,"date":"2022-07-05T15:36:51","date_gmt":"2022-07-05T13:36:51","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/deczentralizovannye-identifikatory-budut-standartizirovany-nesmotrya-na-vozrazheniya-google-i-mozilla"},"modified":"2022-07-05T15:36:51","modified_gmt":"2022-07-05T13:36:51","slug":"deczentralizovannye-identifikatory-budut-standartizirovany-nesmotrya-na-vozrazheniya-google-i-mozilla","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sv\/blog\/news\/deczentralizovannye-identifikatory-budut-standartizirovany-nesmotrya-na-vozrazheniya-google-i-mozilla","title":{"rendered":"Decentraliserade identifierare kommer att standardiseras, trots inv\u00e4ndningar fr\u00e5n Google och Mozilla","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Tim Berners-Lee har meddelat att specifikationen som definierar decentraliserade identifierare f\u00f6r webben (DID, Decentralized Identifier) har f\u00e5tt status som rekommenderad standard. Inv\u00e4ndningarna fr\u00e5n f\u00f6retagen Google och Mozilla har avvisats. <\/p>\n
DID-specifikationen introducerar en ny typ av unika globala identifierare som inte \u00e4r kopplade till enskilda centraliserade tj\u00e4nster och organisationer, s\u00e5som dom\u00e4nregistratorer och certifikatmyndigheter. En identifierare kan associeras med en valfri resurs och genereras av system som \u00e4garen av resursen litar p\u00e5. F\u00f6r att autentisera identifieraren anv\u00e4nds \u00e4gandebevisverifiering baserat p\u00e5 kryptografiska mekanismer, s\u00e5som digitala signaturer. Specifikationen m\u00f6jligg\u00f6r anv\u00e4ndning av olika metoder f\u00f6r distribuerad hantering och h\u00e4mtning av information om identifierare, inklusive metoder baserade p\u00e5 blockchain. <\/p>\n
Det nya URI-formatet skapas som \"did:metod:unik_identifier\", d\u00e4r \"did\" definierar det nya URI-schemat, \"metod\" anger mekanismen f\u00f6r identifierarens behandling, och \"unik_identifier\" representerar en resursidentifierare som \u00e4r specifik f\u00f6r den valda metoden, till exempel \"did:example:123456789abcdefghi\". I f\u00e4ltet f\u00f6r metod anges namnet p\u00e5 den tj\u00e4nst som anv\u00e4nds f\u00f6r att lagra verifierbara data och som garanterar identifierarens unika karakt\u00e4r, definierar dess format och m\u00f6jligg\u00f6r kopplingen av identifieraren till resursen f\u00f6r vilken den skapades. URI med identifieraren omvandlas till ett dokument i JSON-format med metadata som beskriver det beg\u00e4rda objektet och inkluderar publika nycklar f\u00f6r att verifiera \u00e4garen.
<\/center> <\/p>\n
Implementeringen av metoderna str\u00e4cker sig bortom DID-standarden, definieras i sina specifikationer och st\u00f6ds i ett separat register. F\u00f6r n\u00e4rvarande har 135 metoder f\u00f6reslagits baserat p\u00e5 olika blockkedjor, kryptografiska algoritmer, distribuerade teknologier, decentraliserade databaser, P2P-system och identifieringsmekanismer. Det \u00e4r ocks\u00e5 till\u00e5tet att skapa DID-omslag ovanp\u00e5 centraliserade system, till exempel g\u00f6r metoden web det m\u00f6jligt att anv\u00e4nda kopplingen till traditionella v\u00e4rdnamn (till exempel \"did:web:example.com\"). <\/p>\n
Google's objections relate to the separation of the specification for the general mechanism of decentralized identifiers from the specifications for the final implementations of methods, making it impossible to analyze the correctness of the main specification without studying the method specifications. Publishing the main specification while the method specifications are not ready complicates the review process, and Google has suggested postponing the standardization of the general DID specification until several best method standardizations are ready, as during the process of method standardization, subtle details may arise that require refinement of the main specification. <\/p>\n
Mozilla's objections are based on the specification not adequately promoting portability, putting this issue on the shoulders of the method registry. The registry has already proposed over a hundred methods created without consideration for compatibility and standardization of typical solutions. In its current form, it encourages the creation of a new method for each task instead of attempting to adapt existing methods to one's needs. <\/p>\n
The W3C's position is that the standardization of the DID specification, which defines a new extensible class of identifiers and the associated syntax, will serve as an impetus for developing methods and achieving consensus regarding method standardization. There is enough evidence of the applicability of the main specification to address the problems demanded by the community developing decentralized technologies. Proposed method implementations should not be evaluated in analogy with new URL schemes, and the creation of many methods can be seen as aligning the base specification with the needs of developers. <\/p>\n
The standardization of certain methods is viewed as a more complex task in terms of achieving consensus among developers than the standardization of the general class of identifiers. Therefore, adopting the general specification before standardizing methods is considered a solution that could potentially inflict less harm on the community implementing decentralized identifiers. \n K\u00e4lla: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
![\"Decentraliserade](\"\/wp-content\/uploads\/2022\/07\/d24f33dbbd6f855bdfa66400a3397da5.jpg\")
<\/center> <\/p>\n