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


Help: OASIS Mailing Lists Help | MarkMail Help

tm-pubsubj message

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

Subject: Re: [tm-pubsubj] Range of Application


Peter Brown wrote:
> Hi Carl, Hi Bernard....
> <quote who="Carl Mattocks">
>  >Acknowledged - the link is for OASIS members.
>  >
>  >Below is an extract from the charter.
>  ><charter-extract>
>  >The Semantic Content Management SC was established by the OASIS ebXML...
> </quote>
> Unfortunately, the link is even for the TC administrator only, not even 
> OASIS members...
> I would be interested in more detail, particularly as there is always 
> the danger of "scope creep": although there are plenty of things that do 
> need to be done, "our" TC is about Published Subjects, not about 
> semantic interoperability through public registration of ontologies and 
> ontological constructs...The SCMSC sounds closer to the "SeeBIG" TC idea....
Was not trying to suggest "scope creep", just an observation that 
Published Subjects could be used by a number of different technologies.

> BTW: the OASIS members area doesn't show *any* reference at all 
> to SemConManSC of the ebXML Registry....???
> <quote who="Patrick Durusau">
>  >
>  > What I am thinking is that the definitions should be as generic to the
>  > general concept of PSIs as possible so as to allow for future
>  > deliverables to address the needs to topic maps and other technologies
>  > (or the development of deliverables by other communities for their own
>  > purposes).
> </quote>.
> Is this not the tail wagging the dog? Surely business drivers will lead 
> to definition of general concepts and requirements, and *then* such 
> generic definitions can be "narrowed" to specific TM implementations...?

No because no matter how urgent a business driver may be, it cannot 
supply the intellectual content that underlies the general concepts and 
terminology. Such drivers may well influence how soon such concepts and 
terminology are narrowed for specfic cases but that is a different issue.

We may well be talking about the same thing in slightly different ways. 
What I think is important is that the concepts and terminology be 
specific enough to be useful but not limited to a particular set of 
uses. Able to be driven to narrower cases by more specific business 
drivers if you like.

Hope you are having a great day!


> Peter
> ------------------------------------------------------------------------
> Peter Brown
> (formerly Pappamikail)
> Head of Information Resources Management
> European Parliament
> This mail reflects the views and opinions of the author alone. 
> Institutional affiliation is indicated for information purposes only. 
> Any formal correspondence on any matter contained within this mail 
> should be addressed to pbrown@eurpoarl.eu.int 
> <mailto:pbrown@eurpoarl.eu.int>

Patrick Durusau
Director of Research and Development
Society of Biblical Literature
Chair, V1 - Text Processing: Office and Publishing Systems Interface
Co-Editor, ISO 13250, Topic Maps -- Reference Model

Topic Maps: Human, not artificial, intelligence at work!

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