Rought notes 14 March

[Patrick Durusau <patrick@durusau.net>]

Guys,

Rough notes from today attached.

Hope everyone is having a great day!

Patrick

-- 
Patrick Durusau
Patrick@Durusau.net
Chair, V1 - Text Processing: Office and Publishing Systems Interface
Co-Editor, ISO 13250, Topic Maps -- Reference Model
Member, Text Encoding Initiative Board of Directors, 2003-2005

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

Metadata SC 14 March 2007

*Bruce

*Elias

*Florian

*Gary

Ian

Michael

*Patrick

Rob

*Svante

************

1) the current discussion of the field(s) we want; precise semantics

2) Elias' manifest ontology, including the open issues he noted (namespace URI, etc.)

URI for namespace: From OASIS - Bruce will post a strawman

category is right property name for classification - don't need this,
not a global thing we need to enforce

name graph ID - type manifest entry
 
Elias will post an example being used.

3) Elias' UUID + URI idea 

Don't have clear proposal, yet. More fundamental question to ask -
copy the file in the system (Svante) - if use xml:id and not full
URIs, have to construct a URI, then next aspect is have to make a
decision when the document is changed, does the metadata still apply?

A lot of metadata is stable. That is not in the content. But what
about things that point to an xml:id to infer something about the
content. 

One approach, every element is a new element on each save. 

metadata attached by ID and when ID is changed, the metadata no
longer applies, but if stays the same, it reattaches to the new ID.

Florian, dynamic ids based on editing. Could additionally use this ID
for kept always, even if the content changes. 

Elais - give it an id, and a revision attribute, just keep pumping
the revision attribute. 

Svante - Michael said StarOffice had this but wasn't liked. But
Svante likes it.

Svante - When is metadata is being removed? We don't have to say how
people attach metadata. 

Elais: should be using IRC with the conference call

Elais: paragraph with xml:id and revision:id - then meta:property
attributes don't apply to those ids, meta:about decides which one it
applies to, either to revision or revision less URI. Then can figure
out how to remove the metadata. 

Elias: should not cause any more privacy concerns than current
collection of metadata.

Document ID: Elais, when we make metadata statements, need stable
meta:about, can generate a doc id every time you open it. On every
edit, to generate a new ID. 

See chat session: 

Svante: could put the metadata under revision control -

Elias - good idea, how do we do things where we want it attached to
the element? 

Elias: revision for all metadata - problem with not having only one
file - but maybe can use that for in content attributes, extract
RDF/XML out of the document and attach it to the metadata - 

Florian - sending change tracking on styles - no mechanism like that
in RDF - 

Elias - key is balancing on the versioning 

Bruce - this discussion relates to clarifying the field

4) Meeting next week