English version. Proposal for a XML-based format for storage and exchange of design data in the footwear industry - PDF

Please download to get full document.

View again

of 13
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Information Report
Category:

Technology

Published:

Views: 332 | Pages: 13

Extension: PDF | Download: 6

Share
Description
CEN WORKSHOP CWA July 2004 AGREEMENT ICS ; English version Proposal for a XML-based format for storage and exchange of design data in the footwear industry Dit document mag slechts
Transcript
CEN WORKSHOP CWA July 2004 AGREEMENT ICS ; English version Proposal for a XML-based format for storage and exchange of design data in the footwear industry Dit document mag slechts op een stand-alone PC worden geinstalleerd. Gebruik op een netwerk is alleen. toestaan als een aanvullende licentieovereenkomst voor netwerkgebruik met NEN is afgesloten. This document may only be used on a stand-alone PC. Use in a network is only permitted when a supplementary license agreement for us in a network with NEN has been concluded. This CEN Workshop Agreement has been drafted and approved by a Workshop of representatives of interested parties, the constitution of which is indicated in the foreword of this Workshop Agreement. The formal process followed by the Workshop in the development of this Workshop Agreement has been endorsed by the National Members of CEN but neither the National Members of CEN nor the CEN Management Centre can be held accountable for the technical content of this CEN Workshop Agreement or possible conflicts with standards or legislation. This CEN Workshop Agreement can in no way be held as being an official standard developed by CEN and its Members. This CEN Workshop Agreement is publicly available as a reference document from the CEN Members National Standard Bodies. CEN members are the national standards bodies of Austria, Belgium, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom. EUROPEAN COMMITTEE FOR STANDARDIZATION COMITÉ EUROPÉEN DE NORMALISATION EUROPÄISCHES KOMITEE FÜR NORMUNG Management Centre: rue de Stassart, 36 B-1050 Brussels 2004 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No.:CWA 15043:2004 E Contents Contents... 2 Foreword... 4 Introduction Scope Normative References Internet standards EAN-UCC Definitions and abbreviations Definitions Abbreviations The ShoeML data format General structure of the ShoeML Framework Target Audience Potential Usages Relationship with the EFNET2 schemas Core and container schemas The core ShoeML schemas ShoeML_Core ShoeML_BasicGeometry ShoeML_AdvancedGeometry ShoeML_Measurements ShoeML_Last ShoeML_Technical Instruction ShoeML_Picture The Container ShoeMLschemas Design DesignPart DesignGroup CAMInterface Annex A1 (Normative): the ShoeML core schemas ShoeML_Core.xsd ShoeML_BasicGeometry.xsd ShoeML_Picture.xsd ShoeML_Measurement.xsd ShoeML_Last.xsd ShoeML_TechnicalInstruction.xsd ShoeML_Design.xsd Annex A2 (Normative): the CAMInterface sub-schemas NestingData CuttingData StitchingData LastingData Annex A3 (Normative): ShoeML Geometry General usage rules Instancing geometries through the Transform General structure UML diagrams Relationships between the simple geometrical entities: Relatioships between the complex geometrical entities Usage of the Transform and instancing mechanisms Point Line Circle 8.7 Arc PolyPoint PolyLine Plane BezierCurve PolygonMesh NURBS Curves and Surfaces NurbsCurve NurbsSurface Foreword The production of this CEN Workshop Agreement (CWA) was accepted by the CEN/ISSS Workshop FINEC (Footwear INdustry Electronic Commerce) at the 2 nd plenary meeting, held in Milan in March The FINEC Workshop was launched by CEN/ISSS in collaboration with the European Footwear Manufacturers Federation in March 2001, in order to deal with XML issues specific for the footwear industry. The Workshop validated results of the two pilot projects EFNET2 and EFNET3, which targeted respectiuvely electronic data exchange in the downstream and upstream part of the shoe supply chain. The Workshop FINEC gathered representatives from footwear trade associations (retailers and manufacturers), research centres, consultants and CAD/CAM suppliers in the footwear sector in Europe. The present CWA was drafted by experts appointed by partners of the EFNET3 project (Electronic Footwear Network Electronic Trading), coordinated by CESECA, an Italian Service Centre for SMEs in the footwear industry. At various stages the draft CWA was sent out for comments. The final draft was presented at the Workshop FINEC plenary meeting held in Madrid in November The endorsement round ran from 12 December 2003 to 15 January This CEN Workshop Agreement is publicly available as a reference document from the National Members of CEN : AENOR, AFNOR, BSI, COSMT, DIN, DS, ELOT, IBN/BIN, IPQ, IST, MSA, NEN, NSAI, NSF, ON, SEE, SIS, SFS, SNV, UNI. Comments or suggestions from the users of the CEN Workshop Agreement are welcome and should be addressed to the CEN Management Centre. 4 Introduction This document describes the proposal for a modern data format, based on XML, for the storage and exchange of business documents containing design data in the Footwear Industry. The proposed data format has the form of a set of XML Schemas organized in a framework. The set of Schemas is publicly known under the acronym of ShoeML (Shoe Markup Language ). The term business design data is here meant to represent all the data that is managed or exchanged by companies in electronic form in the design phase of the products. These data is usually employed inside Computer Aided Design (CAD) and Manufacturing (CAM) systems in the footwear industry. It covers all the phases from an early idea of a new footwear product, up to the detailed data needed to actually produce the various footwear sizes, and partially extends also to other parts of the footwear chain (production, electronic catalogues, re-selling information and so on). The data formats described in this document are intended to be used side by side with the ones proposed by the EFNET2 project and contained in CWA The focus of the EFNET3 proposal is on the business data exchanged in the first ring of the footwear chain, hereafter indicated as design data, while the proposal from EFNET2 covers data exchanged in the reselling phase. The two proposals naturally blend together, with a well-defined overlap between business data for footwear design and production and for ordering and invoicing. The main common parts are universally unique identifiers, generic classifications of shoe types and party information. Besides reusing some sub-schemas from EFNET2, the EFNET3 proposal has been designed to be completely compatible with the work already done. Although several industry standard formats exist that partially cover the needs of the footwear design phase, most of them are old, not specific for footwear design, and exist in a multitude of sub-versions. The usage of custom undocumented formats for storing a part of the data is the rule, causing exchange and conversion problems for exchanging business documents, implying high costs, and exposing the industry to long term reliability problems. Accumulated experiences, under the form of reuse of successful designs, are the real value for the design departments of footwear industries. The continuous change of software applications, operating systems and data formats, on the contrary, actually exposes the industry to the risk of loosing (in the long term) part of this richness, and severely constraint the competitiveness in aggressive markets. Reliable storage of design data, as well as easy conversion (and reuse of information), are becoming a must in the footwear industry to increase productivity, to lower the costs, and to enable really distributed virtual factories in Europe. New, modern, reliable and compatible data formats are needed. The proposal contained in this document aims to solve at least partially the problem, and to cover the needs of the footwear design ring as much as possible. Design is the least standardized part of the footwear chain, and the one that offers the highest potential of improvement about times, costs and reliability. It has been clear, since the beginning of the project, that the task was (and still is) huge, given the complexity and the heterogeneous nature of data stored or exchanged. Honestly speaking the creation of a new universal data format capable of substituting all the variants existing now is extremely complex, but the problem can be split into smaller parts, and the Footwear Industry can greatly benefit even from the availability of partial solutions. The usage of XML, on the other side, guarantees easy extensibility (to cover niche needs) without breaking the compatibility with the core standard. The choice of XML for designing the new data format has been natural. It fits in the general trend of the EFNET projects (and of many other efforts actually going on), and can guarantee easy extension of the data formats, compatibility with existing data, reliable long-term storage. XML can also solve the coverage problem, as it enables the industries to adopt the common sub-formats while leaving them free to extend the core solution to whatever extent they need. This proposal for a new data format for footwear design business documents has been formulated with the structure of a general framework of sub-formats, collectively called ShoeML (Shoe Markup Language). The framework structure comprises both core and container schemas: 5 The core schemas are new data formats for specific footwear related data, footwear geometry data or footwear measurement data for example, that solve the storage problem for specific data types. The core schemas have a validity that extends even out side the scope of the project, in other words they can be used even stand-alone as substitutes of traditional data formats. The container schemas are simply data wrappers or collectors, in other words they are used to assemble specific solutions for specific design scenarios by collecting together one or more set of data stored with one of the core formats. These containers are usable in a recursive manner, and should be able to fulfil the needs of both simple and complex business data exchange scenarios. To ensure the formulation of a proposal with production quality level, the main core schemas were implemented and tested by the partners of the project, with a particular attention to the Geometry subschemas, actually the most important part of the data to be managed. Direct implementation of the format under development allowed the design team to field test it and to learn how to improve it. At the end of the project we have 5 CAD systems (both 2D and 3D) with support for the proposed formats. The practical implementations clearly demonstrate the actual feasibility of the approach, the low resources needed and the short time to market. The interest generated into the footwear industry during the development phase also indicates that the needs are high and that the proposal should be welcome in many contexts. 6 1. Scope This document describes the general structure of the ShoeML framework of data formats for the business documents containing footwear design data. The new data formats have been designed and implemented as a set of XML Schemas. The document describes the coverage of the data formats, their capabilities and internal details, the built-in validation rules about their content, and lists the main intended usages. Annex A1 and Annex A2 actually contain the latest version of the ShoeML Schemas, together with short descriptions, with the scope to drive the software implementation. Technical details about the Geometry subschemas, actually the most complex ones, are contained in Annex A3. The proposal is complemented by two documents intended as guidelines or best practices about the following aspects: Footwear Measurements Footwear Design Terms They cover several aspects of design on which consensus was impossible to find, and are intended as initial efforts to make the experts in the field converge. In the following paragraphs a high-level description of the ShoeML data format is attempted. The format, as you will see, is made of simple and complex parts. The core of the proposal can be considered quite stable (BasicGeometry, Design, DesignPart, DesignGroup, Picture ), but many extensions will be needed to cover fully the needs of the sector. During the project this extension process was started by defining 4 extension schemas covering the CAM interfacing part, namely the exchange of business data between pure design activities and production. This process is far from being complete, but the proposal contains the general structure of the extension mechanism, that will be used in the future as a guide to complete the coverage. Extensibility is indeed the secret weapon of the proposal. Built in into XML itself, the capability of extending the formats to suit specific needs is the key to the widespread adoption of the new proposal in the complex field of footwear design and production. While working on the project we already had the occasion to meet requirements, actually coming from footwear CAM industries, to split design data into a public one and a machine dependent one. Protection of information considered sensible by the industry has always been the main reason behind the usage of custom and undocumented formats, actually generating the conversion mess we are accustomed to. In the past there was no choice: either completely open and conformant to a standard, or completely closed. The new approach, actually part of this proposal, is to adopt a highly modular data format with extensibility mechanisms built-in, allowing each industry to actually split data into public and custom (or protected) parts. This simple extension mechanism will allow recovery and simple reuse of the public parts, which are often the most valuable ones. Recovering geometry data, for instance, will allow to adapt a particular building operation from a specific machine to another, thus preserving the industry s investments in the long period. 7 2 Normative References The following normative are important for the application of the CWA. Given the overlap between this proposal and the one of the EFNET2 project (CWA 14746), also the normative referenced in that document are applicable, mainly as regards the ISO standards on which that proposal is heavily based. The EFNET3 proposal, in order to maintain compatibility, complies with the definitions used by EFNET2 in CWA Internet standards The data formats defined in this CWA are conforming to the XML Schema Recommendation as defined on the W3C Web site (www.w3c.org). The extended use of XML syntax recommendation 1.0 is part of this CWA EAN-UCC The EFNET schemas must be compliant with EAN-UCC rules, so EAN-UCC core schemas are used as the basis for EFNET2 and hence EFNET3. The scope of these schemas for EFNET3 is more limited, mainly to the identification and classification part, and covers the overlapping area between EFNET2 and EFNET3. The rest of the schemas retain their validity also without these parts. Universally unique identification is considered only an option for generic design data, because design data is usually exchanged in electronic form in well-defined contexts (between specific partners) and is not intended to be available freely on the market (as a footwear product in the EFNET2 sense). Despite of that it was felt that a general mechanism for universal exchange and identification was needed, so a specific Design Data Identifier (DDI) is modelled as part of this proposal. The DDI is based on EAN- UCC identifiers, so this reference is mandatory. 8 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following definitions apply: EFNET: European Footwear Network EFNE2 formats: the set of XML schemas that constitute the EFNET2 proposal. They are focused on traditional EDI (Electronic Data Interchange) data, namely textual and numerical information covering the complete sale process managed with electronic means (catalogues, orders, invoices, returns, receipts.). They are described in CWA EFNET3 formats: the set of XML schemas that constitute the EFNET3 proposal. They are focused on footwear design data, namely all the business data (textual, numerical, images, geometrical coordinates) that are managed by CAD and CAM systems to design a shoe. Footwear Design data: all the computer data that is managed by CAD and Cam systems to allow for the design of footwear. Actually made by several types of data, including but not limited to geometrical data, numbers, textual information, pictures CAD: Computer Aided Design, the design of an object or product made by electronic means. Both generic CAD systems exist, mainly used in the mechanical industry, and specific footwear CAD systems, where some of the traditional procedures of the footwear expert are supported or used by the software application. The data formats contained in this proposal are specific for footwear CAD systems (although some parts can be used also in the generic ones). CAM: Computer Aided Machinery, any kind of machine that can be controlled with a computer to produce some work. Specialized footwear CAM systems exist. The data formats contained in this proposal are intended also to ease the transfer of data (commands, part programs ) to such machines. Geometrical data: the set of data used to represent a geometrical entity on a CAD system. Each object is represented by e set of points, lines, curves or surfaces, and the CAD system actually manages these data to represent the object on the screen, to manipulate it, to drive CAM machines and so on. Actually a set of numbers represented with a specific format (usually IEEE single or double precision floating point, or integers), plus other control information (about mathematical formulas used to generate the curves or to approximate a surface) that can also be very complex. 2D / 3D CAD: both 2-dimentional and 3-dimentional CAD systems exist for footwear data. The 3D ones are the most complex, and are actually used for the higher levels of design (last design, shoe design as a whole), while the 2D systems are used for specific sub-parts that can be actually represented on a plane (with only two coordinates). Both 2D and 3D data must be stored in order to completely support footwear design ShoeML : Shoe Markup Language, the acronym of the set of schemas actually constituting the EFNET3 proposal. A language based on XML used to store footwear design data Legacy data formats: all the industry standard computer data formats (file formats) that are traditionally used in the CAD (and specifically footwear CAD) industry. As an example the DXF or IGES formats. E-commerce: Although more extended definitions are commonly used, e-commerce thus becoming a vague concept, this CWA defines e-commerce as the use of information and communication technologies as a mean to trade between different and independent business. The business to consumer aspect of e- commerce is not considered in this CWA. Synonym: e-trade 9 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CEN European Committee for Standardization CEFACT CSG EbXML EFNET EDI ISO OASIS SGML SME Party, partner, trading partner Centre for the Facilitation of procedures and practices in Administration, Commerce and Transport CEFACT Steering Group Electronic business XML European Footwear Network Electronic Data Interchange International Organisation for Standardisation Organisation for the Advancement of Structured Information Standards Standard Generalised Markup Language Small to Medium sized Enterprise An organisation or business with which e-commerce links are established. Thanks to these links, the trading partners become e- trading partners and the exchange e-business documents between them, preferably between their in house applications. UML URL URI W3C XML GLN GTIN Unified Modeling Language Universal Resource Locator Universal Resource Indicator World Wide Web Consortiu
Recommended
View more...
We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks
SAVE OUR EARTH

We need your sign to support Project to invent "SMART AND CONTROLLABLE REFLECTIVE BALLOONS" to cover the Sun and Save Our Earth.

More details...

Sign Now!

We are very appreciated for your Prompt Action!

x