[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re[2]: [cgmo-webcgm] APS 'name' attribute in XCF?
Hi Robert, When an application needs to export metadata (elements or attributes) that are not part of the WebCGM DTD, they should be inserted using XML namespaces: <webcgm xmlns="http://www.cgmopen.org/" xmlns:extra="something"> <grobject apsid="myId" extra:name="myName"/> </webcgm> More inline... Monday, June 6, 2005, 1:35:28 PM, Robert wrote: RO> Thanks Benoit (and Dieter). I think the issue for at least some RO> of our users is that they want access to all of the metadata in a RO> given WebCGM instance without having to parse the CGM file itself. Would they be trying to access all the metadata within a viewer or some other XML process. RO> Having the metadata in an XML file is very convenient, I guess that means "XML process", i.e. companion file. RO> because XML parsers are readily available. Yes. And parsers will be able to extract information in various namespaces. RO> The bindByName element will serve that purpose, albeit somewhat RO> indirectly since it cannot be a child element of the grobject, RO> para, or subpara elements. <bindByName> is mostly meant to apply new attribute values to various APS sharing the same name. (I have a feeling that you are more concerned about exporting companion files than reading them back into the application.) RO> But it does allow me to put all of the names used in a given RO> WebCGM instance into the XCF. It looks like our users will have RO> to write some JavaScript to associate name attributes to a RO> specific APS. I'm not sure that's still required if you use XML namespaces. -- Benoit mailto:benoit@itedo.com RO> Rob RO> -----Original Message----- RO> From: Benoit Bezaire [mailto:benoit@itedo.com] RO> Sent: Monday, June 06, 2005 10:57 AM RO> To: CGM Open WebCGM TC RO> Subject: Re: [cgmo-webcgm] APS 'name' attribute in XCF? RO> Hi Robert, RO> No it is not an oversight. The group sees the 'name' attribute very RO> similar to the 'id' attribute... It is not possible to set both those RO> attributes via the XML companion file. Both these attributes have to RO> be assigned a value within authoring tools. The DOM and XCF RO> functionality around the 'name' attribute is aimed at queries. From a RO> DOM and XCF perspective, the 'id' and 'name' attributes are read-only. RO> Cheers,
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]