| ★ wanayoo — archive 1999 http://www.xml.com/pub/r/UCLP_v.3.0 | Nouvelle recherche | Portail wanayoo |
|
Home | Search | Resources | Buyer's Guide | FAQs |
Free Newsletter |
| . | |
|
|
|
| |
 Search FAQs  Annotated XML 1.0 What is XML?  Buyer's Guide XML Resources Standards List Submissions List Events Calendar  View Messages Register Login Change profile  Community Companies E-commerce Instruction Linking Metadata Multimedia Perspectives Programming Publishing Specifications Style Tools Vertical Industries Vocabularies |
|
XML Resource Guide: Commerce, EDI, RDF, Schema, W3C Member Submissions (Notes)UCLP v.3.0Universal Commerce Language and ProtocolLink: http://www.w3.org/TR/NOTE-uclpDate: Jan. 20, 1999 Source: SAIC, Bellcore
Excerpted from "Introduction" and "UCLP and XML" sections: "The Universal Commerce Language and Protocol (UCLP) is an XML-compliant schema for tagging metadata that can be used in identifying and retrieving data residing across the Internet. The tags provide a base level of data typing while allowing industry-specific names to be defined as necessary to describe those properties and attributes which a user needs when discriminating among available choices. The introduction of data typing has been discussed as a needed extension to the XML 1.0 Recommendation, but UCLP is intended to introduce a new paradigm for dynamic data tagging for which data typing is only a required tool." "The release of the W3C XML recommendation provides a syntax for tagging data, but it is still necessary to define the content, or at least the relationships, that the tags represent. Document type definitions (DTDs) serve this purpose in standard SGML applications, but these can introduce other nontrivial challenges." "One such challenge is the common effort needed to define industry-specific, standard DTDs that capture the industry content. While there are certainly examples where such DTDs have been developed and provide a useful common language, the process often requires extensive negotiation among the industry representatives and thus can be very time consuming. Once the negotiations are complete, the resulting compromises, while providing a middle ground, may not adequately satisfy individual needs or provide sufficient incentive for member organizations to fully participate." "Even if initially adequate, the DTD scope and specifics must be updated to include technology advances and other changes. Here, time again becomes an issue: if users wait for agreement on DTD changes, this does not support the pace of commerce; if individuals generate modified DTDs, there is soon divergence from an unambiguous standard and point-to-point solutions result. This is the present predicament with EDI." "In the XML recommendation, DTDs are optional and this invites the creation of a new paradigm where DTDs are not needed. For such a paradigm, one needs to look for a tagging schema which captures the relevant parameters describing an object, but which can also evolve to capture changes in the marketplace in the same timeframe in which these are occurring." "The system using these tags would have to be flexible in incorporating changes, would have to provide the industry domain with means to monitor and regulate changes according to their own policies, and must be sufficiently general so that advances made in one domain can be transferred to others. The technology transfer would include both growth in the hierarchy which captures content organization and improvements in the software which allow users to establish connections between entities." Submitted by Lisa Rein
|
|
| . | |
|
|
|
| . | |
| Copyright © 1998-1999 Seybold Publications and O'Reilly & Associates, Inc. | |