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


Help: OASIS Mailing Lists Help | MarkMail Help

entity-resolution message

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

Subject: Re: Catalog Requirements

/ Lauren Wood <lauren@sqwest.bc.ca> was heard to say:
| understanding what gets applied where. It would also help with
| precedence questions. I would want a STYLESHEET and a NAMESPACE keyword.

There should be *no* precedence questions. If you're looking for a
stylesheet, use the STYLESHEET mapping, if you're looking for a
namespace, use that one.

I think we should have an API (er, are we going to define a standard
API?  Yes, let's, I say) that lets you select only one category at a

The interesting question is, what are we going to do about delegation?
Off the top of my head, I see a small conflict. Delegation makes sense
for public identifiers (as described in TR9401), but it also makes
sense for URNs, which could apply across categories. Hmmm....

| We could also think about some "hints" for extensions to meet other uses
| that we haven't specified yet to help steer extensions in a direction
| that can be standardised readily later.

Got anything in mind?

                                        Be seeing you,

Norman.Walsh@East.Sun.COM | A man is not necessarily intelligent
XML Technology Center     | because he has plenty of ideas, any more
Sun Microsystems, Inc.    | than he is a good general because he has
                          | plenty of soldiers.--Chamfort

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

Powered by eList eXpress LLC