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

 


Help: OASIS Mailing Lists Help | MarkMail Help

stdsreg message

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


Subject: [stdsreg] mtg minutes 21 May 2002 [N019]


Minutes of the Standards Registry committee
conference call #7, 21 May 2002 [N019]

Attendence: Makx Dekkers, Karen Boehme, Beatrice Gbatte, Bob Hager, John
Ketchell/Luc van den Berghe (part), Monica Vago

 (Call hosted by CEN/ISSS)

1. Introduction

Roll call and welcome from Bob Hager in Karl Best's unavoidable absence.
The agenda was approved (document N 017).

2. Approval of record of fifth meeting (document N016)

The record was approved

3.  Review of the status of action items

  5.1. Mark Norton: ideas for using multiple classification schemes.
Further discussion of single vs multiple schemes; follow-on to action
items 4.1 and 4.2 of previous meeting.  Deferred in Mark's absence
  5.2. Sally Fuger: input on metadata from ebXML Registry. Deferred in
Sally's absence
  6.1. Bob Hager: direct mapping between ISO 11179-3 and the Dublin Core

This was discussed with the participation of Makx Dekkers of Dublin
Core. Makx felt that whether the Dublin Core mapped the ISO standard or
not was not particularly important.  DC had in fact tried to conform but
had not really been able to align, since the ISO focus was on code lists
and not on the meta-data content at the document level.  DC definition
1/5 however gave a number of attributes that had been taken up in ISO
11179.

Bob recommended that the Committee use the Dublin Core approach. Karen
would e-mail her meta-data experts to check this was acceptable to them.


4.	Further input on metadata draft (document N018)

Bob introduced this for discussion, as the promised revision to his
document N015;  he apologised for the unavoidable late circulation.

Makx noted that resource was a major element in the Dublin Core, and
this seemed to be absent.  However, we were not here considering the
same kind of activity as DC, for example in requiring a registration of
the data with an
authority.

a. Document status

Bob noted that this field seemed to have been the major subject of
debate at the previous meeting.

In discussion, it was noted that keeping in effect a document history
was unnecessary - all that was needed was a kind of snapshot of the
state of affairs.  It was therefore agreed to specify only the date
referring to the most recent milestone.  The document would therefore
specify one of the following, with a date:
1.  project initiation
2.  draft available
3.  document approved
4.  document published

b. Rights information

Makx wondered whether we were talking about rights in the meta-data or
rights in the documents themselves.  Bob confirmed the latter was the
case - ie did we need to include a pointer as to who held the rights on
the documents.  Makx suggested in that case there were three potential
pieces of information - whether the document was free, whose was the
copyright, and any detail relating to electronic rights.

c. Security classification

This might be an additional issue:  whether in some cases there were
restrictions on who could access documents.

d.  Equivalent standards

There was some confusion amongst the group as to what this meant.  Karen
felt it was not needed.  John noted that in CEN/ISSS, there was a case
of parallel standardization activities using different technologies
(Microsoft and Sun) and therefore perhaps one was "equivalent" to the
other.

e. Standardized address model  (SDO contact table)

Makx noted that DC had not yet resolved how to handle addressing, though
it had a WG on the issue.  The meta-data on the resource provided
information as to who published the document, so there was no need for
an addressing system.  However, there were global initiatives, for
instance in the rights management community (eg MPEG-21), that decribed
addressing in that context.

f.  Additional comments

Makx noted that price and "available from" could not be mapped to Dublin
Core.  The Committee noted that pricing was a potentially unstable and
complex element.  On the other hand, the available source of published
documents was standard library data.

 - any other business
 - schedule next meeting and solict host

5.  Any other business

Bob noted that participation had improved.  He thanked Makx for joining
the Committee.  He would also inform the ANSI Organization Member
Council (the topic was on the agenda for the June 27 meeting of the
"summit") and the ISO ITSIG, which would also provide information to
other parts of the world than the US and Europe.  The meta-data
standardization activity in the educational area might also be useful to
approach (IEEE, ISO/IEC JTC1/SC36, CEN/ISSS WS/LT).

Monica suggested Bob's presentations might be made available on the web
site.  Bob agreed to do this (action 7/1 - Bob).


6. It was hoped that Karl would chair.  Bob agreed to host the call.


------------------------------------------------------------------------
Best regards
John Ketchell
Director, CEN/ISSS - Information Society Standardization System

URL:http://www.cenorm.be/isss

Rue de Stassart, 36	email (direct) john.ketchell@cenorm.be
B-1050 Brussels	email (secretariat) isss@cenorm.be
Belgium	                        Tel (direct) + 32 2 550 08 46
Fax + 32 2 550 09 66	Tel (secretariat) + 32 2 550 08 13
Tel (GSM) +32 475 594 828





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


Powered by eList eXpress LLC