[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: 7 April Regrep call minutes
OASIS Regrep TC Conference Call Friday 7 April 2000 Attending: Nagwa Abdelghfour, Sun Terry Allen, Commerce One Lisa Carnahan, NIST Una Kearns, Documentum, in part Priscilla Walmsley, XMLSolutions Yutaka Yoshida, Sun Attending as visitor: Len Gallagher, NIST There being a quorum, the meeting was called to order by the chairman. Terry had made a new revision of the technical specification, circulated in email, but too late for review at this meeting; he described some of the changes. Among these is that the OASIS-specific values for attributes and the like have been removed to a customization layer. This change now raises the question, what does OASIS-compliant mean? Len observes that data-element needs data-element reference. (Terry to fill out the definition of data element in the DTD.) data-element also needs keywords, etc. Len asserts that a d.e.d. is a special kind of data element. Is this defensible? Terry to write up why not. Discussion of literary work issue: Docbook 3.1 could be regarded as a data element dictionary set. Docbook 3.1 is something for which you don't put anything in the repository, although you have information about it in the registry; it's only the modules that go in the repository (plus perhaps the whole distribution zipped up). Terry to write up a sample for a single data element and a single-storage-entity DTD. Is there a field to show that the metadata has been updated and when?. Yes, date-last-modified. What about the case where the registered item is a spec not a DTD? How do we handle multiple representations? - EBXML update - no news - NIST update - still coding and looking for test data - XML.org update - working on it Adjourned.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC