WIPO ST.90 ์ด๋ž€?

2024. 5. 29. 17:07ใ†๐Ÿ“‚ ํŠนํ—ˆ์‹ฌ์‚ฌ๋‹จ๊ณ„๋ณ„ ์ฃผ์š” ์ œ๋„ ๋ฐ ๋ฐฉ๋ฒ•/๊ธฐํƒ€


์ตœ์ดˆ์ž‘์„ฑ์ผ : 2024. 05. 29

์ˆ˜์ •์ผ : 2024. 05. 29


๋ณธ ๋‚ด์šฉ์€ ์ง€์‹์žฌ์‚ฐ ๊ด€๋ จ ์—…๋ฌด์— ๊ผญ ํ•„์š”ํ•œ ์ •๋ณด๋งŒ์„ ์š”์•ฝํ•œ ๊ฒƒ์ด๋ฉฐ, ์ด๋Š” ํŠนํ—ˆ๊ด€๋ฆฌ ์†Œํ”„ํŠธ์›จ์–ด์— ํ†ตํ•ฉ๋˜๋Š” ๊ธฐ์ดˆ์ž๋ฃŒ๊ฐ€ ๋ฉ๋‹ˆ๋‹ค. ํ•ด๋‹น ์ฃผ์ œ์™€ ๊ด€๋ จ๋œ ์งˆ๋ฌธ์ด๋‚˜ ์˜๊ฒฌ์ด ์žˆ๋Š” ๊ฒฝ์šฐ, ์ œ๊ณต๋œ ์ด๋ฉ”์ผ์„ ํ†ตํ•ด ์–ธ์ œ๋“ ์ง€ ๋ฌธ์˜ํ•˜์‹œ๊ฑฐ๋‚˜ ์•„๋ž˜์˜ ๋Œ“๊ธ€๋กœ ์˜๊ฒฌ์„ ๋‚จ๊ฒจ์ฃผ์„ธ์š”.

Below is a summary of information essential for intellectual property-related tasks, and this serves as foundational material integrated into the patent management software. If you have any questions or opinions related to the topic, please feel free to contact us via the provided email or leave a comment below.


์ •๋ณด์š”์ฒญ : info@gyeomsabok.com


"์•„๋ž˜์˜ ๋‚ด์šฉ์€ ์ด ์ •๋ณด์™€ ํ•จ๊ป˜ ํ•˜์„ธ์š”. ๋†€๋ž๊ฒŒ๋„ ๋”์šฑ ์œ ์šฉํ•ด์ง‘๋‹ˆ๋‹ค."
I recommend combining the content below with this information. Surprisingly, it becomes even more useful.

Summary of Standard ST.90



  • Purpose: To provide guidelines for APIs to ensure consistent, interoperable, and secure data exchange among Intellectual Property Offices (IPOs) and between IPOs and their users.
  • Objectives: Establish uniform design principles, improve interoperability, encourage reusability, promote secure information exchange, and integrate internal business processes dynamically with business partners.

Definitions and Terminology

  • HTTP: Foundation of data communication for the web, functioning as a request-response protocol.
  • API: Software components providing reusable interfaces for different applications to interact and exchange data.
  • REST: A set of principles for transmitting data over standardized interfaces, focusing on stateless services.
  • SOAP: Protocol for message exchange between applications, using XML-based message exchange.
  • Web Service: Method of communication over the web, categorized into REST and SOAP.
  • Service Contract: Document expressing how a service exposes its capabilities, including metadata for interactions.
  • URI, URL, ETag: Various terms related to resource identification and management on the web.


  • Coverage: Communications between IPOs and their applicants or data users, and between IPOs using device-to-device or device-to-software connections.
  • Design Rules and Conventions: Provided for RESTful and SOAP Web APIs, including a model API documentation or service contract.

Web API Design Principles

  • Standardized Service Contract: Crucial for consistent service design and governance.
  • Service Loose Coupling: Ensures independent evolution of clients and services.
  • Service Statelessness: Enhances scalability.
  • Service Reusability and Autonomy: Well-defined boundaries and reusable services.
  • Service Discoverability: Effective discovery and interpretation of services.
  • Use of Standards: Favors industry standards over locally optimized solutions.
  • Pick-and-choose Principle: Design rules based on specific implementation needs.


  • URI Components: Use hierarchical structures and consistent naming patterns.
  • HTTP Methods: Follow standardized semantics for GET, POST, PUT, PATCH, DELETE, etc.
  • Resource Model: Model as a resource hierarchy, leveraging the URI's hierarchical nature.
  • Multiple Formats Support: Use content type negotiation for JSON and XML formats.
  • Data Query Patterns: Support for pagination, sorting, field projection, and complex search expressions.

Error Handling

  • HTTP Status Codes: Use appropriate codes and detailed error payloads for robust error handling.

Additional Highlights:

  • Supporting Multiple Formats: APIs should support both XML and JSON, with consistent mapping between the two.
  • Service Contract Examples: Provides model contracts for SOAP (using WSDL) and RESTful APIs (using RAML and OAS).
  • Security Model: Emphasizes secure information exchange, with principles like least privilege and maximizing entropy.
  • API Maturity Model: Ensures a structured approach to API development and deployment.


  • Design Rules and Conventions: Detailed guidelines for RESTful and SOAP Web APIs.
  • HTTP Status Codes: Comprehensive list of status codes for consistent API responses.
  • High-Level Security Practices: Best practices for securing web APIs.


This standard provides a thorough framework for designing, implementing, and maintaining web APIs in the context of intellectual property data, ensuring robust, interoperable, and secure communication across different systems and organizations.