Startseite Version 7

• 19.11.2015 (Köln)
• 28.01.2016 (Köln)
• 17.03.2016 (Köln)
• 19.05.2016 (Oberkochen)
• 30.06.2016 (Leonberg)
• 28.09 - 30.09.2016 (Leonberg)
• 15.03.- 17.03.2017 (Westerwald)

http://forum.b2boptic.com/viewtopic.php?f=50&t=776

The meeting takes place on the 15.03.-17.03.2017 in the Westerwald on the Mausmühle www.mausmuehle.de, pension@mausmuehle.de, telephone 02626/411.

On March 15, 2017, the first day of the next three-day meeting of the b2bOptic working group “LensCatalog”, we would like to invite all developers who have already dealt with the implementation of the new LC7 standard, giving the opportunity to address detailed questions and problems personally with the group discuss.

Anyone who would like to participate is welcome and please contact Diana Kroll .

• Bernd Freyermuth (Lensware)
• Pia Geschke (IPRO)
• Nicole Backmann (Zeiss)
• Viktor Bauer (Essilor - EPM)
• Anahid Sufi (Essilor)
• Sebastian Raring (IPRO)
• Thomas Barth (IPRO)
• Peter Kraus (Kraus-IT)
• Johan Voskamp (Optiplaza)
• Diana Kroll (R+H)
• Gerd Bernau (COMCEPT)

  * Organizational     * The next meeting should be over 2-3 days. Reason: presentation of the final version in November 2016. Place will be announced.     * Point 1 of the agenda is to be the topic OptionPrice.

 * Geometry data Lensgeo     * For what is the LensGeo needed:       * Graphical representation       * Geometry check     * Presentation of the identifiers of the OMA standard (Excel document was sent by B.Freyermuth. The Excel list is not 100% OMA.)     * This Excel list is revised and distributed by T.Barth and S.Raring.     * For variable progression length: If something is not left, what is the default length?     * B.Freyermuth: Designshift Consider the decentration     * N.Backmann: Distributed a drawing. It will insert and distribute the link to the B.Freemmuth data     * N.Backmann: For elliptical lenses, instead of two diameters, only one diameter plus the difference value should be given.     * Prism reference point (OC) is the optical center and is to be used as a reference point for all further distances and positions in the future     * H.Obermayer: Observe the production tolerance for the minimum impact.     * N.Backmann: incorporate ET edge.     * Production tolerance and ET margin are two different elements in the new format.     * P.Kraus: Enter a default value in the order options.     * Progressionslength: Discussion: Where should this be shown? In the Geo or Order Options box.       * There are fixed progressions> No order options.       * There are variable progression lengths> into the order options.       * Progressive length depends on the refra-values. Is given by the lens manufacturer. > Where should this value be stored?

  * Base Curves     * B.Freyermuth: Specify only the curves without range.     * N.Backmann: Plausibility only as a webservice.     * Basic curves in own branch and the lens by ID pretend.     * Further suggestion: Set values ​​per base curve as a tree.     Conclusion> It remains as it is, plus addition.     * P.Kraus> Attach base curves to the range.     * B.Freyermuth> Attach base curves to the lens.     * Conclusion> Attach base curve to the lens.

  * Prices     * Prisms and higher cylinders are added as an option. EDV code is freely definable.     * Separate branch in which EDV codes are defined as prisms and higher cylinders.     * Second lens: First fall away. Because too complex. Will be canceled within the scope of the action processing for the next SF7.

  * Information     * A new Type Product Picture.     * Additional branch picture

  * Combi-Frame-Lens     * Presentation of Mr. Obermayer.     * Very interesting. Is something that is needed. However, there is a lack of time at the next meetings.     * Combi-Lens-Frame becomes a new standalone format.

  * OrderoptionNames     * Simple key-value list.

  * OrderoptionRanges     * By means of an ID and to the order option. But must be considered more carefully.     * Please note that the range may be different for two products. (E.g. HSA at YSIS and HSA at Sport.

  * Included Features     * Time range for Insurace etc.

* Lensrange      * G.Bernau: Ranges in a four- or multi-dimensional coordinate system        * Rejected because the amount of data would bloat.      * G.Bernau: Sph Cyl Add in a lower tree at Lensrange append. This allows more complex range images to be generated without having to save the rest redundantly.

  * Nicole Backmann (Zeiss)   * Diana Kroll (R + H)   * Katrin Wurdinger (Rodenstock)   * Johan Voskamp (Optiplaza)   * Michiel Husken (Essilor Netherlands)   * Sebastian Raring (IPRO)   * Hans Obermayer (Rodenstock)   * Malte Neumann (Prisma)

   Organizational     * At the next meeting focus on Geo, but also other topics. Prices     * Inviting Geo experts to the next meeting, alternatively written description of the wishes    Geometry     * Implementation of the actual state until next meeting     * Elaboration of a description of the routes in the Geo, for the purpose of documentation and verification on different interpretations in the past ⇒ Nicole Backmann     * Replace “Exact diameter” fields with absolute values ​​with relative values, e.g. In the case of elliptical lens, height 5 mm is smaller than width     * Width of manufacturing margins    OrderOptions     * Elaboration of a description of distances / angles (e.g., slice angles) for the purpose of documentation and checking for different interpretations in the past ⇒ Nicole Backmann     * Is referenced by Lens or option    OrderOptionRanges     * Is referenced by OrderOption     * The units used correspond to the unit in the LensOrder; When a new LensCatalog version is adopted, the current LensOrder version (definition must be documented)     * In addition to value ranges, there must also be the possibility of enum values    OrderOptionNames     * Depends directly on the root element    Lens / Option     * If a property is not the same for a basic lens and the selected options, the property of the option always wins; If a property is not set to “No”, it will lose it; Exceptions must still be examined and, where appropriate, defined in the document; (E.g. Lens with hard, option with SuperHart ⇒ Total lens has feature SuperHart; Open question: Prio for several options e.g. Option1 with hard, Option2 with SuperHart    Lens     * Characteristics is moved to the LensMaterialProps     * RGB values ​​for colors are desired in Belgium     * CombiLenses branch needs reference to informationId     * CombiLenses branch decided upon discussion    LensPrice     * Several suggestions discussed ⇒ more precise considerations needed ⇒ decision postponed to next meeting     * Prism / cylinder group conversion or alternatives discussed ⇒ more precise considerations needed ⇒ decision postponed to next meeting     * Prices no longer depend on the range, but on a reference to a RangeID, the priceGroupIds is optionally referenced at the same time     * Sphere / cylinder filter as absolute values ​​(definition must be in docu)    LensRanges     * No longer fixed to the lens, but via ID    CodeSubstitution     * Scope of possibilities still sufficient     * Addition by a date indicating the beginning of the validity of the substitution definition; Without end date     * A list of old codes is attached to the current lens / surcharge.     * An old code may only be entered for several current products if it is a product proposal but not for a replacement. (Definition must be in docu)    Frame / Lens combinations     * Development of a proposal as XML schema ⇒ Hans Obermayer ==== 17.03.2016 Meeting in Köln ==== === Participants: ===   * Diana Kroll (R + H)   * Niko Zonker (HOYA)   * Katrin Wurdinger (Rodenstock)   * Johan Voskamp (Optiplaza)   * Michiel Husken (Essilor Netherlands)   * Gerd Bernau (COMCEPT)   * Sylvia Estermann-Keßel (COMCEPT)   * Raimund Hamacher (COMCEPT)   * Sebastian Raring (IPRO)   * Hans Obermayer (Rodenstock)   * Malte Neumann (Prisma) === Protocol === == Topic LensCatalog Version 7 (SF7) ==    ordering options     * Discussion in the Forum     * - two connecting points: LensRange and option     * - tree structure (thus also logical links) comparable to the new Kombis     * - Priorities: can, must, not necessary (weakens a “must” on a “can”) can not (highest Prio)     * - a “must” cancels any “can” property to an OrderOption, and so on. A prio order    OrderOptionNames     * - depending on the lens    OrderOptionRanges     * - on the plane of the lens     * - Integrate basic curves, if possible    Lens-mount connector     * - expert group (leader: Hans Obermayer) first develops the requirements     * - First left open: own standard or part of the LensCatalog     * - Where is the pricing?     * - Complete lenses at the moment. At Rod, R + H, Nika, Hoya, SA, Ess. If necessary ask further requirements.    Geometry     * - expert group (organization: Gerd Bernau) is to be given the possibility to propose and formulate requirements in the next 2-3 months     * - Invite other experts on geometry       * (Suggestion: P. Haas, P. Krause, Ollendorf, Mr. Freyermuth, Mr. Reinhartz)     * - according to European and / or German standards an overview of the official names of the routes and points in the wiki is to be created (organization: Nicole Backmann)     * - Use the Din standard designation as an identifier in Lenspricelist format.     * - Requirements from PMS view: real height / width and tolerance for diameter calculation; Possibly still position of the notes for the lens presentation    Others     * Product groups in the future a grouping for the lens selection of the user, without other functionality (as in the version 6)     * - Product names (3 lengths): Short description 15 characters, medium name 40 characters, long description without limit     * - Support for variable color intensities: Flag in OrderOptions and possible values ​​in OrderOptionRanges     * - no prism / cylinder groups     * - no single prism / cylinder liners, but the finished lens prices depend on e.g. From the prism to a lens == General Topic ==   * Guideline for application from the lens manufacturer.     * Example: Should be displayed hard in the area of ​​anti-reflective coatings?   * Notifications from the forum at regular intervals   * Certification for Lenspricelist     * Different degrees of certification   * Hoya Mets in the SF6 and LensOrder.   * LensOrder     * Please order the goods voucher in the order. ==== 02.10.2015 Meeting in Köln ==== Subscriber:
Malte Neumann, Diana Kroll, Nicole Backmann, Niko Zonker, Hans Obermayer, Anahid Sufi, Claudia Natusch-Pleger, Gerd Bernau, COMCEPT ), Raimund Hamacher (COMCEPT) Protocol   * * Combinations     * * There were no objections to the idea of ​​combinations in the branch.     * * Mr Obermeyer has suggested a similar proposal, but noted that it is almost identical in principle to our proposal. His proposal had a level with which one could determine the possible coatings in “90% of cases”.     * * Include order options in the combinations.     * * Take the edge into the combinations.     * * Prices     * * The assembly of the delivery area and price was rejected by the lens distributors. In practice this is probably two very different points, which have nothing to do with each other directly.     * * Prices as a sub-point of the lens and define the prices. In this case, the respective price range is indicated.     * * There are different dependencies for prices. prices] These dependencies have to be considered.   * * Note by Nicole Backmann: Design the lens. (Mr. Kraus can help if necessary.)   * * Mr. Zonker described the necessity of a converter SF7 to SF6.   * * Depending on the focal range (range) create a possibility that the lens maker can store hints that the software then displays. Background: With Hoya, some lenses and higher thicknesses may create trailing edges that reduce the effective diameter. Mr. Zonker would like to present this to the customer.   * * Recording of remote options in the catalog.     * * Depending on the lens thickness     * * Depending on options     * * Forced by remote edging     * * Nylor / drilling points possible / not possible   * * Idea by Mr. Zonker: There are defined implementation levels for the implementation of the standard, in which the functionality has to be supported * * Order Options     * * Options of lenses and coatings may be excluded.     * * Order options require an or link of different options.   * * Mandatory ordering of certain lenses / options.   * * The necessity is seen that the next meetings should take place at short intervals. ==== 19.03.2015 Telko ==== Subscriber:
Malte Neumann, Sebastian Raring and Gerd Bernau Subjects   * * Several post-discussions on the previous Telko.   * * Arrange the required date with a lens distributor to present the work done. ==== 05.02.2015 Telko ==== Subscriber:
Malte Neumann, Sebastian Raring and Gerd Bernau Subjects   * * Combinations: There were two options.     * * In XML a full tree is built up into the depth ^.       * * Advantages:         * * Human readable         * * All in one place       * * Disadvantage:
        * * The tree can only branch further. A merge is no longer possible.
        * * Larger data because no duplicate nodes are eliminated
    * * Only nodes created by ID are linked to one tree.       * * Advantages:
        * * Data volume can be reduced start
        * * Easy to transfer into a database       * * Disadvantage:
        * * Without editor not human readable
             * * Keep the range with the information as it is today (diameter + thickness range), do not extract diameter and thickness as shown by Gerd Bernau.     * * Problem Prices
    * * On the one hand there are prices of basic lens price + prices of the chosen options; on the other hand there are certain options with certain options in certain areas (options in the LensRange and price over the delivery area index).     * * Suggestion of Malte Neumann price to the range to hang is not good. This means that the documentation must define a prioritization of the prices.   * * Delivery period is not required in the lens. Can be delivered through the delivery areas → no delivery range available → Lens not available.   * * In the XML structure, the material with properties may be outdated, since with many lenses identical.   * * OrderOptions:     * * Everyone is trying to think of a solution. So far it is only defined that it should not be directly integrated into the combinatorial, but should be defined separately.     * * Requirements for the options:       * * Dependency of basic lens and options       * * There are options that are mutually exclusive (e.g., coarse / fine)       * * Range of values ​​must take into account strengths (e.g., proximity areas depend on the addition). This could possibly also the Basecurve.dat into the options transfer.            ==== 23.01.2014 Meeting in Köln ==== Subscriber:
(Not known) Forum Review in Forum Subjects   * * Presentation of various combinations     * * Advantages and disadvantages of the proposal by Gerd Bernau.     * * Presentation of Malte Neumann.     * * Malte Neumann's proposal turned out to be a better alternative and should be pursued further.   * * Multilingualism   * * Geometry data   * * Effective areas   * * Possibilities of distribution ==== 14.11.2013 ==== Subscriber:
IT-Kraus, HOYA, R & H, Rodenstock, Zeiss, COMCEPT, IPRO and PRISMA Forum
Review in Forum Subjects**
  * * Catalog offer by Peter Haas (Zeiss)   * * Catalog suggestion of Peter Kraus   * * Combinations in SF7 by Gerd Bernau