Linking to styles with PICS?
It appears there is another W3C effort that may be related to
issues raised here, but the relevant document(s?) are not available
publicly. Could the SGML ERB or someone else from an organization
that is a W3C member take a look and see whether PICs-ng's notion
of wrappers is useful to XML?
From email@example.com Fri Apr 25 07:15:37 1997
Received: from gizmo.lut.ac.uk (firstname.lastname@example.org [18.104.22.168]) by sub.sonic.net (8.8.5/8.8.5) with SMTP id HAA07928 for <email@example.com>; Fri, 25 Apr 1997 07:15:33 -0700
Received: from majordom by gizmo.lut.ac.uk with local (Exim 1.61 #1)
id 0wKjcl-0004N7-00; Fri, 25 Apr 1997 12:57:11 +0100
Received: from oclc.org [22.214.171.124]
by gizmo.lut.ac.uk with smtp (Exim 1.61 #1)
id 0wKjbp-0004Mu-00; Fri, 25 Apr 1997 12:56:19 +0100
Received: from orc.NISOR (orc.dev.oclc.org) by oclc.org (4.1/SMI-4.1)
id AA18041; Fri, 25 Apr 97 07:52:10 EDT
Received: by orc.NISOR (SMI-8.6/SMI-SVR4)
id HAA25686; Fri, 25 Apr 1997 07:52:03 -0400
Date: Fri, 25 Apr 1997 07:52:03 -0400
From: firstname.lastname@example.org (Stu Weibel)
To: email@example.com, advax@Triumf.CA
Subject: Re: HTML Metadata for other Web objects
Cc: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org
As I have said earlier, the PICS 1.1 label facility is not of interest
to the metadata community.
The PICS-ng specification (which is not, as far as I know, now
available publically, in that it is being discussed by the working
group) will allow strings, substructure, qualifiers, and repeatable
Further, there are 4 association models of PICS metadata and resources:
1. meta embedded in the resource header.
easy, requires no additional infrastructure, and readily
harvestable, but perhaps not the best model for efficiency
(bloated headers) and maintainability (keeping metadata
consistent as resources are mirrored or copied will be a problem).
2. resource embedded in a metadata wrapper.
a useful model for wrapping images, for example. same advantages
and disadvantages as #1
3. coupled metadata
metadata is tightly coupled to the resource, may travel with it, but
is not embedded and can be handled as an object in its own right
4. third party metadata
metadata is linked to the resource by reference only; may or may
not be created, maintained, distributed by the manager of the
resource itself. requires additional infrastructure (eg.
database management tools)
this is the model that third party rating providers (label
bureaus) will be based on, but it is also the model for
distributed resource cataloging that already predominates in the
Models 2,3, and 4 could be applied to non-html objects