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


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-lcsc message

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

Subject: Re: [ubl-lcsc] Global attributes and publishing markup

I have looked at the request for Publishing Markup and have some
thoughts on this.  First, do we really want to do this?  And second, if
we do, why don't we just use something that is already invented
somewhere?  As it is mentioned below use XHTML.

So, in light of the first question, do we really want to do this?  I can
see the need within descriptions of items within catalogs, or other
general notes, that need to be marked up like this.  Since we are
talking "Ebusiness" this should mean it is a way to show the data on
screen, as in catalogs.  

Well, it looks like I could go along with this, as long as we know
exactly where we need this type of markup and keep it limited to these

Lisa Seaburg

"Eve L. Maler" wrote:
> Dear LC SC,
> At last week's NDR SC telecon I took actions to ask for feedback from
> your group on two matters.  Would it be possible for you to spend a few
> minutes on these in your call this week and get back to us with the
> results?  If you would like further background, the meeting minutes in
> which these items arose are here:
>    http://lists.oasis-open.org/archives/ubl-ndrsc/200204/msg00048.html
> *Global attributes:
> Gunther has proposed that a small group of XML attributes should appear
> on every element: uid, uidRef, uidRefs, and xs:language.  Effectively,
> these act as "common" properties shared by all object classes.  You can
> find the description of these four in Section 6.2 of the Elements vs.
> Attributes paper:
> http://www.oasis-open.org/committees/ubl/ndrsc/pos/draft-stuhec-elemvsattrib-03.zip
> First, does your methodology account for identifying "common" properties
> such as these?  The spreadsheet would need to say (e.g., though a flag)
> that the property is truly global (that is, it must be applied to *all*
> object classes), and would need to provide a definition of the property
> that could safely be used identically in building all necessary
> documentation.
> Second, can you please consider the four common properties proposed by
> Gunther and confirm whether you want them?  (That is, can you add them
> to your spreadsheet somehow if you want them, and reject them explicitly
> if not?)
> *Publishing markup:
> Can you supply examples of the sorts of generic "publishing structures"
> you might need, such as bold text, paragraphs, lists, etc.?  We realize
> that this is likely to come up in force only when you get to catalogs.
> But if we get some input now, we can start to determine whether we can
> just reuse an existing vocabulary such as XHTML for such purposes, or
> whether something special-purpose will have to be built.  This will have
> an impact on our recommendations for schema modularity.
> Thanks very much for your attention to these requests.
>         Eve
> --
> Eve Maler                                    +1 781 442 3190
> Sun Microsystems XML Technology Center   eve.maler @ sun.com
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>

Lisa Seaburg
AEON Consulting
Website: http://users.gmi.net/~xmlgeek/
Email:  xmlgeek@gmi.net
Phone: 662-562-7676
Cellphone: 662-501-7676

"Artificial Intelligence is no match for Natural Stupidity"

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

Powered by eList eXpress LLC