Добірка наукової літератури з теми "STANDARD PARASITIC EXCHANGE FORMAT"

Оформте джерело за APA, MLA, Chicago, Harvard та іншими стилями

Оберіть тип джерела:

Ознайомтеся зі списками актуальних статей, книг, дисертацій, тез та інших наукових джерел на тему "STANDARD PARASITIC EXCHANGE FORMAT".

Біля кожної праці в переліку літератури доступна кнопка «Додати до бібліографії». Скористайтеся нею – і ми автоматично оформимо бібліографічне посилання на обрану працю в потрібному вам стилі цитування: APA, MLA, «Гарвард», «Чикаго», «Ванкувер» тощо.

Також ви можете завантажити повний текст наукової публікації у форматі «.pdf» та прочитати онлайн анотацію до роботи, якщо відповідні параметри наявні в метаданих.

Статті в журналах з теми "STANDARD PARASITIC EXCHANGE FORMAT"

1

Pellen, Florian, Sylvain Bouquin, Isabelle Mougenot, and Régine Vignes-Lebbe. "Building an OWL ontology with Xper3." Biodiversity Information Science and Standards 2 (May 21, 2018): e25614. http://dx.doi.org/10.3897/biss.2.25614.

Повний текст джерела
Анотація:
Xper3 (Vignes Lebbe et al. 2016) is a collaborative knowledge base publishing platform that, since its launch in november 2013, has been adopted by over 2 thousand users (Pinel et al. 2017). This is mainly due to its user friendly interface and the simplicity of its data model. The data are stored in MySQL Relational DBs, but the exchange format uses the TDWG standard format SDD (Structured Descriptive DataHagedorn et al. 2005). However, each Xper3 knowledge base is a closed world that the author(s) may or may not share with the scientific community or the public via publishing content and/or identification key (Kopfstein 2016). The explicit taxonomic, geographic and phenotypic limits of a knowledge base are not always well defined in the metadata fields. Conversely terminology vocabularies, such as Phenotype and Trait Ontology PATO and the Plant Ontology PO, and software to edit them, such as Protégé and Phenoscape, are essential in the semantic web, but difficult to handle for biologist without computer skills. These ontologies constitute open worlds, and are expressed themselves by RDF triples (Resource Description Framework). Protégé offers vizualisation and reasoning capabilities for these ontologies (Gennari et al. 2003, Musen 2015). Our challenge is to combine the user friendliness of Xper3 with the expressive power of OWL (Web Ontology Language), the W3C standard for building ontologies. We therefore focused on analyzing the representation of the same taxonomic contents under Xper3 and under different models in OWL. After this critical analysis, we chose a description model that allows automatic export of SDD to OWL and can be easily enriched. We will present the results obtained and their validation on two knowledge bases, one on parasitic crustaceans (Sacculina) and the second on current ferns and fossils (Corvez and Grand 2014). The evolution of the Xper3 platform and the perspectives offered by this link with semantic web standards will be discussed.
Стилі APA, Harvard, Vancouver, ISO та ін.
2

Tardy, Randall D., Steve C. Brown, Mo Harmon, and Richard W. Bradshaw. "Engineering and Survey-Exchange Standard Engineering Data Format: Standard Engineering Data Format." Transportation Research Record: Journal of the Transportation Research Board 1675, no. 1 (January 1999): 75–83. http://dx.doi.org/10.3141/1675-10.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
3

Zaluzec, N. J., E. J. Kirkland, M. S. Isaacson, J. A. Hunt, C. E. Fiori, and C. E. Fiori. "EMSA/MAS standard format for spectral data exchange." Proceedings, annual meeting, Electron Microscopy Society of America 49 (August 1991): 526–27. http://dx.doi.org/10.1017/s0424820100086945.

Повний текст джерела
Анотація:
One of the frustrating problems experimentalists often encounter with computer based spectroscopic instrumentation is the general incompatibility of the data files recorded on different analysis systems. The rapid growth of inexpensive personal computers has resulted in an information explosion which has increased the desirability and need for a simple method for exchange of experimental data between scientists who may be office neighbors or transoceanic collaborators. While it is not reasonable to expect a particular manufacturers software, which was designed and optimized for specific hardware, to function on an competitor's system, it would be of enormous value to the microanalysis community to have a simple method for data interchange. This would allow, for example, the routine distribution of experimental data between research laboratories with a minimum of difficulty or would enable test spectra to be transported between data acquisition systems to compare different data analysis routines. These points as well as all the other merits of a standardized data format have been detailed elsewhere.
Стилі APA, Harvard, Vancouver, ISO та ін.
4

Kyba, Christopher C. M., Dorien E. Lolkema, and Constance E. Walker. "A standard format for measurements of skyglow." Proceedings of the International Astronomical Union 10, H16 (August 2012): 742. http://dx.doi.org/10.1017/s1743921314013258.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
5

FUKUDA, Ken. "BioPAX: A Standard Data Format for Pathway Data Exchange." Seibutsu Butsuri 47, no. 3 (2007): 179–84. http://dx.doi.org/10.2142/biophys.47.179.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
6

Holt, Richard C., Andy Schürr, Susan Elliott Sim, and Andreas Winter. "GXL: A graph-based standard exchange format for reengineering." Science of Computer Programming 60, no. 2 (April 2006): 149–70. http://dx.doi.org/10.1016/j.scico.2005.10.003.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
7

Wang, Zhangang, Honggang Qu, Zixing Wu, and Xianghong Wang. "Geo3DML: A standard-based exchange format for 3D geological models." Computers & Geosciences 110 (January 2018): 54–64. http://dx.doi.org/10.1016/j.cageo.2017.09.008.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
8

Baumbach, Jörg Ingo, Antony N. Davies, Peter Lampen, and Hartwig Schmidt. "JCAMP-DX. A standard format for the exchange of ion mobility spectrometry data (IUPAC Recommendations 2001)." Pure and Applied Chemistry 73, no. 11 (January 1, 2001): 1765–82. http://dx.doi.org/10.1351/pac200173111765.

Повний текст джерела
Анотація:
The relatively young field of ion mobility spectrometry has now advanced to the stage where the need to reliably exchange the spectroscopic data obtained worldwide by this technique has become extremely urgent. To assist in the validation of the various new spectrometer designs and to assist in inter-comparisons between different laboratories reference data collections are being established for which an internationally recognized electronic data exchange format is essential. To make the data exchange between users and system administration possible, it is important to define a file format specially made for the requirements of ion mobility spectrometry. The format should be computer readable and flexible enough for extensive comments to be included. In this document, we define a data exchange format, agreed on by a working group of the International Society for Ion Mobility Spectrometry at Hilton Head Island, USA (1998) and Buxton, UK (1999). This definition of this format is based on the IUPAC JCAMP-DX protocols, which were developed for the exchange of infrared spectra [1] and extended to chemical structures [2], nuclear magnetic resonance data [3], and mass spectra [4]. This standard of the Joint Committee on Atomic and Molecular Physical Data is of a flexible design. The International Union of Pure and Applied Chemistry have taken over the support and development of these standards and recently brought out an extension to cover year 2000 compatible date strings and good laboratory practice [5]. The aim of this paper is to adapt JCAMP-DX to the special requirements of ion mobility spectra [6].
Стилі APA, Harvard, Vancouver, ISO та ін.
9

Kjær, Jesper, and Bruno Ledergerber. "HIV Cohort Collaborations: Proposal for Harmonization of Data Exchange." Antiviral Therapy 9, no. 4 (May 2004): 631–33. http://dx.doi.org/10.1177/135965350400900421.

Повний текст джерела
Анотація:
HIV cohort studies have provided useful information on the natural history of HIV infection and the effects of antiretroviral therapy. It has become increasingly common to combine data from several cohorts into one dataset in order to address certain specific questions with more statistical power than can be achieved with the individual studies. This requires each cohort to map data into a standard format before merging. Until recently, this standard format has differed for each such collaborative analysis. We have therefore developed the HIV Cohort Data Exchange Protocol (HICDEP), which is freely available at http://www.cphiv.dk/HICDEP.pdf . Once individual cohorts have set up a means of transfering data into this format, as and when required, this should greatly facilitate data merging for future joint analyses. The HICDEP incorporates data from HIV drug resistance tests, which have been particularly challenging for cohorts to integrate into databases.
Стилі APA, Harvard, Vancouver, ISO та ін.
10

Egerton, R. F., D. S. Bright, S. D. Davilla, P. Ingram, E. J. Kirkland, M. Kundmann, C. E. Lyman, P. Rez, E. Steele, and N. J. Zaluzec. "Standard formats for the exchange and storage of image data." Proceedings, annual meeting, Electron Microscopy Society of America 51 (August 1, 1993): 220–21. http://dx.doi.org/10.1017/s0424820100146941.

Повний текст джерела
Анотація:
In microscopy, there is an increasing need for images to be recorded electronically and stored digitally on disk or tape. This image data can be shared by mailing these magnetic media or by electronic transmission along telephone lines (e.g. modem transfer) or special networks, such as Bitnet and Internet. In each case, the format in which the image is stored or transmitted must be known to the recipient in order to correctly recover all the information. Because there are many image formats to choose from, it would undoubtedly save misunderstanding and frustration if a group of individuals with similar interests and needs could agree upon a common format. The MSA Standards Committee has surveyed several formats which could be of particular interest to microscopists, with a view to making a recommendation to our community.Our chief concern has been compatibility with existing software, combined with an adequate representation of the data, compactness of data storage (on disk) and reasonable rate of data transfer.
Стилі APA, Harvard, Vancouver, ISO та ін.

Дисертації з теми "STANDARD PARASITIC EXCHANGE FORMAT"

1

Onyeako, Isidore. "Resolution-aware Slicing of CAD Data for 3D Printing." Thesis, Université d'Ottawa / University of Ottawa, 2016. http://hdl.handle.net/10393/34303.

Повний текст джерела
Анотація:
3D printing applications have achieved increased success as an additive manufacturing (AM) process. Micro-structure of mechanical/biological materials present design challenges owing to the resolution of 3D printers and material properties/composition. Biological materials are complex in structure and composition. Efforts have been made by 3D printer manufacturers to provide materials with varying physical, mechanical and chemical properties, to handle simple to complex applications. As 3D printing is finding more medical applications, we expect future uses in areas such as hip replacement - where smoothness of the femoral head is important to reduce friction that can cause a lot of pain to a patient. The issue of print resolution plays a vital role due to staircase effect. In some practical applications where 3D printing is intended to produce replacement parts with joints with movable parts, low resolution printing results in fused joints when the joint clearance is intended to be very small. Various 3D printers are capable of print resolutions of up to 600dpi (dots per inch) as quoted in their datasheets. Although the above quoted level of detail can satisfy the micro-structure needs of a large set of biological/mechanical models under investigation, it is important to include the ability of a 3D slicing application to check that the printer can properly produce the feature with the smallest detail in a model. A way to perform this check would be the physical measurement of printed parts and comparison to expected results. Our work includes a method for using ray casting to detect features in the 3D CAD models whose sizes are below the minimum allowed by the printer resolution. The resolution validation method is tested using a few simple and complex 3D models. Our proposed method serves two purposes: (a) to assist CAD model designers in developing models whose printability is assured. This is achieved by warning or preventing the designer when they are about to perform shape operations that will lead to regions/features with sizes lower than that of the printer resolution; (b) to validate slicing outputs before generation of G-Codes to identify regions/features with sizes lower than the printer resolution.
Стилі APA, Harvard, Vancouver, ISO та ін.

Книги з теми "STANDARD PARASITIC EXCHANGE FORMAT"

1

Mapping, Canadian Council on Surveying and. Standard EDP file exchange format for digital topographic data. Sherbrooke: Energy Mines and Resources, Surveys, Mapping and Remote Sensing Sector, 1989.

Знайти повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
2

East, E. William. The standard data exchange format for critical path method scheduling. Champaign, Ill: US Army Corps of Engineers, Construction Engineering Research Laboratories, 1995.

Знайти повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
3

Forberg, J. D. Profiler standard format for data exchange: Profiler site to hub computer. Boulder, Colo: U.S. Dept. of Commerce, National Oceanic and Atmospheric Administration, Environmental Research Laboratories, 1985.

Знайти повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
4

United States. Federal Interagency Coordinating Committee on Digital Cartography. Standards Working Group. Federal geographic exchange format: A standard format for the exchange of spatial data among Federal Agencies : version 01.08 : final draft. [Washington, D. C.]: The Committee, 1986.

Знайти повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
5

National Information Standards Organization (U.S.). Proposed American national standard record format for patron records. Bethesda, MD: National Information Standards Organization, 1990.

Знайти повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
6

IEEE Power Engineering Society. Power Systems Relay Committee., Institute of Electrical and Electronics Engineers., and IEEE-SA Standards Board, eds. IEEE standard Common Format for Transient Data Exchange (COMTRADE) for power systems. New York, N.Y., USA: Institute of Electrical and Electronics Engineers, 1999.

Знайти повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
7

IEEE Power Engineering Society. Power Systems Relaying Committee., Institute of Electrical and Electronics Engineers., and IEEE Standards Board, eds. IEEE standard common format for transient data exchange (COMTRADE) for power systems. New York, N.Y., USA: Institute of Electrical and Electronics Engineers, 1991.

Знайти повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
8

Burton, Celia. ONIX for libraries: An investigation into the feasibility of using ONIX International as a standard for bibliographic data transmission between the book trade and libraries in the UK : a study conducted for Book Industry Communication. London: Book Industry Communication, 2001.

Знайти повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
9

Devlin, Bruce, Oliver Morgan, Nick Wells, and Jim Wilkinson. MXF Book: An Introduction to the Material EXchange Format. Taylor & Francis Group, 2013.

Знайти повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
10

Devlin, Bruce, Oliver Morgan, Nick Wells, and Jim Wilkinson. MXF Book: An Introduction to the Material EXchange Format. Taylor & Francis Group, 2006.

Знайти повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.

Частини книг з теми "STANDARD PARASITIC EXCHANGE FORMAT"

1

Beyer, Dirk, and Karlheinz Friedberger. "Violation Witnesses and Result Validation for Multi-Threaded Programs." In Leveraging Applications of Formal Methods, Verification and Validation: Verification Principles, 449–70. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-61362-4_26.

Повний текст джерела
Анотація:
Abstract Invariants and error traces are important results of a program analysis, and therefore, a standardized exchange format for verification witnesses is used by many program analyzers to store and share those results. This way, information about program traces and variable assignments can be shared across tools, e.g., to validate verification results, or provided to users, e.g., to visualize and explore the results in order to fix bugs or understand the reason for a program’s correctness. The standard format for correctness and violation witnesses that was used by SV-COMP for several years was only applicable to sequential (single-threaded) programs. To enable the validation of results for multi-threaded programs, we extend the existing standard exchange format by adding information about thread management and thread interleaving. We contribute a reference implementation of a validator for violation witnesses in the new format, which we implemented as component of the software-verification framework "Image missing" . We experimentally evaluate the format and validator on a large set of violation witnesses. The outcome is promising: several verification tools already produce violation witnesses that help validating the verification results, and our witness validator can re-verify most of the produced witnesses.
Стилі APA, Harvard, Vancouver, ISO та ін.
2

Beyer, Dirk, and Sudeep Kanav. "An Interface Theory for Program Verification." In Leveraging Applications of Formal Methods, Verification and Validation: Verification Principles, 168–86. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-61362-4_9.

Повний текст джерела
Анотація:
Abstract Program verification is the problem, for a given program $$P$$ and a specification $$\phi $$, of constructing a proof of correctness for the statement “program $$P$$ satisfies specification $$\phi $$” ($$P \models \phi $$) or a proof of violation ("Equation missing"). Usually, a correctness proof is based on inductive invariants, and a violation proof on a violating program trace. Verification engineers typically expect that a verification tool exports these proof artifacts. We propose to view the task of program verification as constructing a behavioral interface (represented e.g. by an automaton). We start with the interface $$I_{P}$$ of the program itself, which represents all traces of program executions. To prove correctness, we try to construct a more abstract interface $$I_{C}$$ of the program (overapproximation) that satisfies the specification. This interface, if found, represents more traces than $$I_{P}$$ that are all correct (satisfying the specification). Ultimately, we want a compact representation of the program behavior as a correctness interface $$I_{C}$$ in terms of inductive invariants. We can then extract a correctness witness, in standard exchange format, out of such a correctness interface. Symmetrically, to prove violation, we try to construct a more concrete interface $$I_{V}$$ of the program (underapproximation) that violates the specification. This interface, if found, represents fewer traces than $$I_{P}$$ that are all feasible (can be executed). Ultimately, we want a compact representation of the program behavior as a violation interface $$I_{V}$$ in terms of a violating program trace. We can then extract a violation witness, in standard exchange format, out of such a violation interface. This viewpoint exposes the duality of these two tasks — proving correctness and violation. It enables the decomposition of the verification process, and its tools, into (at least!) three components: interface synthesizers, refinement checkers, and specification checkers. We hope the reader finds this viewpoint useful, although the underlying ideas are not novel. We see it as a framework towards modular program verification.
Стилі APA, Harvard, Vancouver, ISO та ін.
3

Lang, Clemens, Silvia Winkler, Johannes Koren, Gerhard Gritsch, Tilmann Kluge, and Christoph Baumgartner. "First Clinical Experiences with the New DICOM Neurophysiology Standard." In dHealth 2023. IOS Press, 2023. http://dx.doi.org/10.3233/shti230030.

Повний текст джерела
Анотація:
Background: Exchange of EEG data among institutions is complicated due to vendor-specific proprietary EEG file formats. The DICOM standard, which has long been used for storage and exchange of imaging studies, was expanded to store neurophysiology data in 2020. Objectives: To implement DICOM as an interoperable and vendor-independent storage format for EEG recordings in the Clinic Hietzing. Methods: A pilot implementation for automated conversion of EEG data from a proprietary to standardized DICOM format was developed. Additionally, EEG review based on a central DICOM archive in a DICOM EEG viewer (encevis by AIT) was implemented. Results: More than 200 long-term video EEG recordings and over 3000 routine EEGs were archived to the central DICOM archive of the WIGEV. Conclusion: Using DICOM as a storage format for EEG data is feasible and leads to a substantial improvement of interoperability and facilitates data exchange between institutions.
Стилі APA, Harvard, Vancouver, ISO та ін.
4

Schaminée, P., A. Bezuijen, and H. den Adel. "Geotechnical exchange format language a base for a physical modelling data standard?" In Physical Modelling in Geotechnics. Taylor & Francis, 2006. http://dx.doi.org/10.1201/noe0415415866.ch29.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
5

Tosoni, Luca. "Article 93 Committee procedure." In The EU General Data Protection Regulation (GDPR). Oxford University Press, 2020. http://dx.doi.org/10.1093/oso/9780198826491.003.0141.

Повний текст джерела
Анотація:
Article 28(7) (Standard contractual clauses); Article 40(9) (Codes of conduct); Article 43(9) (Certification mechanisms); Article 45(3) and (5) (Adequacy decisions); Article 46(2)(c)–(d) (Standard data protection clauses); Article 47(3) (Binding corporate rules); Article 61(9) (Format and procedures for mutual assistance); Article 67 (Exchange of information); Article 70(1) and (3) (Tasks of the Board); and Article 92 (Exercise of the delegation).
Стилі APA, Harvard, Vancouver, ISO та ін.
6

McGrath, Tim. "The Reality of Using Standards for Electronic Business Document Formats." In Handbook of Research on E-Business Standards and Protocols, 21–32. IGI Global, 2012. http://dx.doi.org/10.4018/978-1-4666-0146-8.ch002.

Повний текст джерела
Анотація:
This chapter presents the challenges faced when developing and using standard formats for electronic business document exchange and tries to identify the real values and costs. As a reference it takes the OASIS Universal Business Language (UBL) and demonstrates how, despite the challenges, UBL can provide a common bridging format (sometimes called a “lingua franca”) for exchanging business information between different communities.
Стилі APA, Harvard, Vancouver, ISO та ін.
7

Ziminski, Timoteus B., Steven A. Demurjian, Eugene Sanzi, Mohammed S. Baihan, and Thomas Agresta. "An Architectural Solution for Health Information Exchange." In Virtual and Mobile Healthcare, 283–327. IGI Global, 2020. http://dx.doi.org/10.4018/978-1-5225-9863-3.ch014.

Повний текст джерела
Анотація:
Health information technology (HIT) systems including electronic health records (EHRs) have a market saturation nearing 92% at individual institutions but are still unsuited for cross-institutional collaboration of stakeholders (e.g., medical providers such as physicians, hospitals, clinics, labs, etc.) in support of health information exchange (HIE) of different HIT systems in geographically separate locations. In the computer science field, software architectures such as service-oriented architecture, grid computing, publish/subscribe paradigm, and data warehousing are well-established approaches for interoperation. However, the application of these software architectures to support HIE has not been significantly explored. To address this issue, this paper proposes an architectural solution for HIE that leverages established software architectural styles in conjunction with the emergent HL7 standard Fast Healthcare Interoperability Resources (FHIR). FHIR models healthcare data with XML or JSON schemas using a set of 93 resources to track a patient's clinical findings, problems, allergies, adverse events, history, suggested physician orders, care planning, etc. For each resource, a FHIR CRUD RESTful Application Program Interface (API) is defined to share data in a common format for each of the HITs that can then be easily accessible by mobile applications. This paper details an architectural solution for HIE using software architectural styles in conjunction with FHIR to allow HIT systems of stakeholders to be integrated to facilitate collaboration among medical providers. To demonstrate the feasibility and utility of HHIEA, a realistic regional healthcare scenario is introduced that illustrates the interactions of stakeholders across an integrated collection of HIT systems.
Стилі APA, Harvard, Vancouver, ISO та ін.
8

Rinaldi, Eugenia, and Sylvia Thun. "From OpenEHR to FHIR and OMOP Data Model for Microbiology Findings." In Studies in Health Technology and Informatics. IOS Press, 2021. http://dx.doi.org/10.3233/shti210189.

Повний текст джерела
Анотація:
HiGHmed is a German Consortium where eight University Hospitals have agreed to the cross-institutional data exchange through novel medical informatics solutions. The HiGHmed Use Case Infection Control group has modelled a set of infection-related data in the openEHR format. In order to establish interoperability with the other German Consortia belonging to the same national initiative, we mapped the openEHR information to the Fast Healthcare Interoperability Resources (FHIR) format recommended within the initiative. FHIR enables fast exchange of data thanks to the discrete and independent data elements into which information is organized. Furthermore, to explore the possibility of maximizing analysis capabilities for our data set, we subsequently mapped the FHIR elements to the Observational Medical Outcomes Partnership Common Data Model (OMOP CDM). The OMOP data model is designed to support the conduct of research to identify and evaluate associations between interventions and outcomes caused by these interventions. Mapping across standard allows to exploit their peculiarities while establishing and/or maintaining interoperability. This article provides an overview of our experience in mapping infection control related data across three different standards openEHR, FHIR and OMOP CDM.
Стилі APA, Harvard, Vancouver, ISO та ін.
9

Fermoso Garcia, Ana María, and Roberto Berjón Gallinas. "Business Information Integration from XML and Relational Databases Sources." In Database Technologies, 1959–83. IGI Global, 2009. http://dx.doi.org/10.4018/978-1-60566-058-5.ch117.

Повний текст джерела
Анотація:
This chapter introduces different alternatives to store and manage jointly relational and eXtensible Markup Language (XML) data sources. Nowadays, businesses are transformed in e-business and have to manage large data volumes and from heterogeneous sources. To manage large amounts of information, Database Management Systems (DBMS) continue to be one of the most used tools, and the most extended model is the relational one. On the other side, XML has reached the de facto standard to present and exchange information between businesses on the Web. Therefore, it could be necessary to use tools as mediators to integrate these two different data to a common format like XML, since it is the main data format on the Web. First, a classification of the main tools and systems where this problem is handled is made, with their advantages and disadvantages. The objective will be to propose a new system to solve the integration business information problem.
Стилі APA, Harvard, Vancouver, ISO та ін.
10

Fermoso Garcia, A. M. "Business Information Integration from XML and Relational Databases Sources." In Adaptive Technologies and Business Integration, 282–307. IGI Global, 2007. http://dx.doi.org/10.4018/978-1-59904-048-6.ch014.

Повний текст джерела
Анотація:
This chapter introduces different alternatives to store and manage jointly relational and eXtensible Markup Language (XML) data sources. Nowadays, businesses are transformed in e business and have to manage large data volumes and from heterogeneous sources. To manage large amounts of information, Database Management Systems (DBMS) continue to be one of the most used tools, and the most extended model is the relational one. On the other side, XML has reached the de facto standard to present and exchange information between businesses on the Web. Therefore, it could be necessary to use tools as mediators to integrate these two different data to a common format like XML, since it is the main data format on the Web. First, a classification of the main tools and systems where this problem is handled is made, with their advantages and disadvantages. The objective will be to propose a new system to solve the integration business information problem.
Стилі APA, Harvard, Vancouver, ISO та ін.

Тези доповідей конференцій з теми "STANDARD PARASITIC EXCHANGE FORMAT"

1

Sim, Susan Elliott, Ric Holt, and Rainer Koschke. "Workshop on standard exchange format (WoSEF) (workshop session)." In the 22nd international conference. New York, New York, USA: ACM Press, 2000. http://dx.doi.org/10.1145/337180.337825.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
2

Saele, H. "ODEL - standard format for exchange of metering and settlement information." In 16th International Conference and Exhibition on Electricity Distribution (CIRED 2001). IEE, 2001. http://dx.doi.org/10.1049/cp:20010929.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
3

Bender, Andreas, Karl Haesler, Claus Thomas, and Jaroslaw Grochowicz. "Development of Universal Brake Test Data Exchange Format and Evaluation Standard." In SAE 2010 Annual Brake Colloquium And Engineering Display. 400 Commonwealth Drive, Warrendale, PA, United States: SAE International, 2010. http://dx.doi.org/10.4271/2010-01-1698.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
4

Piron, L., T. Inskip, and K. Hughes. "Improving content interoperability with the dash content protection exchange format standard." In IBC 2015 Conference. Institution of Engineering and Technology, 2015. http://dx.doi.org/10.1049/ibc.2015.0023.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
5

Jackson, E., Bruce Hildreth, Brent York, and William Cleveland. "Evaluation of a Candidate Flight Dynamics Model Simulation Standard Exchange Format." In AIAA Modeling and Simulation Technologies Conference and Exhibit. Reston, Virigina: American Institute of Aeronautics and Astronautics, 2004. http://dx.doi.org/10.2514/6.2004-5038.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
6

Tsuboi, S., and S. Morino. "Conversion of SEED format to XML representation for a new standard of seismic waveform exchange." In 3rd International Workshop on Scientific Use of Submarine Cables and Related Technologies. IEEE, 2003. http://dx.doi.org/10.1109/ssc.2003.1224164.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
7

Stokes, Harlan. "IGES Success on a Shoestring: A Management Case Study of CAD/CAM Data Exchange." In ASME 1991 International Computers in Engineering Conference and Exposition. American Society of Mechanical Engineers, 1991. http://dx.doi.org/10.1115/cie1991-0043.

Повний текст джерела
Анотація:
Abstract In the Autumn of 1988, the Materials Operations at Control Data Corporation’s Computer Products Group began a program to electronically exchange mechanical CAD models with its suppliers. The “Supplier CAD-Link” program provided many immediate benefits and offers a unique learning experience about electronic data interchange. Existing technologies are used, so the program operates on a shoestring budget with no major dollar investments required of CDC or the suppliers. The program uses the IGES standard file format, so suppliers can apply the lessons learned to CAD/CAM data exchanges with other companies. Now, with the continuing success of the CAD-Link program. Computer Products is re-evaluating many of the old paper based methods of doing business. This paper explores some of the issues for managing a CAD/GAM data exchange program.
Стилі APA, Harvard, Vancouver, ISO та ін.
8

Gischner, B., P. Lazo, K. Richard, and R. Wood. "Enhancing Interoperability Throughout the Design & Manufacturing Process." In SNAME Maritime Convention. SNAME, 2005. http://dx.doi.org/10.5957/smc-2005-p21.

Повний текст джерела
Анотація:
As part of the NSRP program, various tools and standards have been developed to enable the efficient exchange of product models during the design process. In particular, the ISE Project has developed and demonstrated the capability for successful transfer of structural, piping, and HVAC product models that could be used in detail design. During 2005, NSRP awarded a project for ISE Interoperability Modules (known as ISE4). This project will expand the testing and implementation of ISE tools to support both early stage design and manufacturing efforts. An International Standard (ISO 10303-215: Application Protocol for Ship Arrangements) will be used to exchange product model information during early stage design. Another task in this project entitled “Steel Processing” will focus on using ISE tools and the STEP Standard to define a shipbuilding product model format that will support the requirements of multiple, disparate manufacturing processes. The ISE4 Project also includes tasks to enhance interoperability by providing exchange capabilities for Engineering Analysis and Electrical data. This paper and presentation will show how these new ISE tools will facilitate the exchange of ship product models to support interoperability from early stage design (using Ship Arrangements) through manufacture.
Стилі APA, Harvard, Vancouver, ISO та ін.
9

Sunderland, Richard, Richard Crowder, and Bob Damper. "An Approach to the Simulation of Robotic Systems Using XML Based Configuration Files." In ASME 2004 International Design Engineering Technical Conferences and Computers and Information in Engineering Conference. ASMEDC, 2004. http://dx.doi.org/10.1115/detc2004-57678.

Повний текст джерела
Анотація:
This paper presents a environment using the eXtensible Markup Language, XML, to describe a robotic systems in a format suitable for simulation, and to support the integration of several programming environments to create a flexible physical simulation system. Data exchange via open-standard based plain text files allows the system components to be loosely-coupled, rather than combined them into a single integrated development environment. This ensures that the most appropriate tools can be used for each component and the system can be extended with minimal disruption. Those parts of the system that require real-time data exchange use simple UNIX socket-based interactions, which are configured using shared XML configuration files. The environment is demonstrated by the simulation of a simple task using a SCARA robot.
Стилі APA, Harvard, Vancouver, ISO та ін.
10

Pan, Chunxia, and Shana Smith. "Extracting Geometrical Data From CAD STEP Files." In ASME 2003 International Design Engineering Technical Conferences and Computers and Information in Engineering Conference. ASMEDC, 2003. http://dx.doi.org/10.1115/detc2003/cie-48224.

Повний текст джерела
Анотація:
Most CAD tools currently do not have advanced capability built in for directly analyzing the feasibility of product assembly during the design stage. As a result, the feasibility of product assembly has to be analyzed using external assembly analysis tools. To integrate external assembly analysis tools with CAD tools, geometrical data from the CAD models must be extracted from CAD files and imported into the assembly analysis tools. To transfer geometrical data between CAD tools and assembly analysis tools, a neutral file format is needed. STEP (standard for the exchange of product model data) is a neutral file format for convenient and reliable data exchange between different design and manufacturing systems. Therefore, STEP is considered as one of the most popular formats for saving designs. As a result, to evaluate designs, extracting geometrical data from CAD-STEP file is important. Comparing with some other currently available methods, first translating STEP file into XML and then using Java DOM to get geometrical information from XML file is much better. This paper explores the process of extracting geometrical data from a CAD-STEP file for assembly sequence planning. A STEPXML translator, Java-XML parser and DTD (document type definition) generator are used on the JDK 1.4 platform. In this project, DOM (document object model) is applied as the API (Application Programming Interface) for XML.
Стилі APA, Harvard, Vancouver, ISO та ін.

Звіти організацій з теми "STANDARD PARASITIC EXCHANGE FORMAT"

1

Grote, H., J. Holt, N. Malitsky, F. Pilat, R. Talman, and C. G. Trahern. SXF (Standard eXchange Format): definition, syntax, examples. Office of Scientific and Technical Information (OSTI), June 1998. http://dx.doi.org/10.2172/1119545.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
2

East, E. W. The Standard Data Exchange Format for Critical Path Method Scheduling. Fort Belvoir, VA: Defense Technical Information Center, September 1995. http://dx.doi.org/10.21236/ada303566.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
Ми пропонуємо знижки на всі преміум-плани для авторів, чиї праці увійшли до тематичних добірок літератури. Зв'яжіться з нами, щоб отримати унікальний промокод!

До бібліографії