OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

regrep message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: Re: UDEF's day in the sun


<H2> within an HTML document is used to highlight or emphasize something and
can be used as a title but as you point out is not limited to that role.
Perhaps what is most important is that <H2> is a notation used for presentation
whereas <TITLE> carries semantic meaning in the context of a document or a
human. The UDEF is intended to be used for those data elements that carry
semantic meaning in the context of an object (such as those within the UDEF),
not how the data element might be presented.

Ron Schuldt

Jon Bosak wrote:

> Ron,
> In addition to the problem that Robin has referred to, I don't
> understand how the UDEF scheme handles the very common case where
> two elements that appear to have the same meaning are intended to
> be used in different contexts.  The required context is part of
> the meaning too, isn't it?
> An <H2> in HTML performs much the same function that a <TITLE> in
> a <SECT2> does in DocBook ... but the DocBook TITLE element is
> constrained to occur within a section container, while the HTML H2
> element is not.  Do these two elements have the same meaning?
> Jon
>    Delivered-To: fixup-regrep@lists.oasis-open.org@fixme
>    Date: Sat, 29 Apr 2000 10:23:31 -0600
>    From: rschuldt <rschuldt@uswest.net>
>    X-Mailer: Mozilla 4.7 [en] (Win98; I)
>    X-Accept-Language: en
>    MIME-Version: 1.0
>    CC: Registry-Repository <regrep@oasis-open.org>,
>       Terry Allen <tallen@sonic.net>, Robin Cover <robin@isogen.com>,
>       kevin@xmls.com
>    References: <Pine.GSO.3.96.1000428175631.27966L-100000@grind>
>    Content-Type: text/plain; charset=us-ascii
>    Content-Transfer-Encoding: 7bit
>    Sender: owner-regrep@lists.oasis-open.org
>    Reply-To: regrep@lists.oasis-open.org
>    Precedence: bulk
>    Content-Length: 2188
>    Robin,
>    Thank-you for the note to the group and for including the pointer from
>    your home page. As noted in past regrep meetings, I believe that a UDEF
>    based naming convention that conforms to ISO/IEC 11179 and that uses the
>    property terms (class words) of DoD 8320.1-M-1 is a necessary part of
>    the global registry and repository. The article by Bill Lewis does an
>    excellent job of highlighting the fact that XML needs an answer to the
>    semantic dispersion problem. Until a solution is widely adopted, the
>    various XML dialects will continue to generate applications that are
>    designed for computer-to-human-to-computer integration.
>    A joint AIA/EIA/DoD effort to create a National standard for Data
>    Interoperability and Configuration Management (EIA 836) is planning to
>    include the UDEF naming convention as part of the standard. The EIA 836
>    announcement is at:
>    http://www.geia.org/eoc/G33/g33index.htm
>    Ron Schuldt
>    Robin Cover wrote:
>    > Regrep member Ron Schuldt (rschuldt@uswest.net) has reminded us
>    > from time-to-time about the UDEF solution to the network's
>    > "semantic dispersion" problem.
>    >
>    > UDEF (The Universal Data Element Framework) has been identified
>    > as a "Dewey Decimal-Like Indexing System" for the Web.
>    >
>    > This month's issue of Intelligent Enterprise features an article
>    > by William J. Lewis which references and explains UDEF.
>    > I have duly abstracted this in my "XML Articles" collection,
>    >
>    >   http://www.oasis-open.org/cover/xmlArticles.html
>    >
>    > Or see:
>    >
>    > "XML Microstandards"
>    >  http://www.intelligententerprise.com/000428/supplychain.shtml
>    >
>    > - Robin Cover
>    >
>    > PS  Actually, I think the *easy* case is when we have
>    > umpteen names (sic! "tags") for "the same thing", such that a
>    > solution can amount to a semantic declaration and (numeric/ID)
>    > "key that allows an unlimited number of aliases."  The
>    > more common case, and the harder one, is where
>    > "almost-the-same-thing" (times twelve or thirty) has different
>    > names AND a slightly different conceptual model; this
>    > factoring problem is what causes the semantic mismatch,
>    > and no (easy) magic can be conjured to make the
>    > same "things" (only 80, 85, 90, 99, 99.2 % "identical")
>    > behave identically.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC