Bug 543302 - IDREF misused
Summary: IDREF misused
Status: NEW
Alias: None
Product: PDE
Classification: Eclipse Project
Component: Doc (show other bugs)
Version: 4.9   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-Doc-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-09 07:39 EST by Elliotte Rusty Harold CLA
Modified: 2022-12-22 13:46 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Elliotte Rusty Harold CLA 2019-01-09 07:39:09 EST
This is likely a large problem across the plugin docs but let's start with a specific example. See this page:

https://help.eclipse.org/photon/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fextension-points%2Forg_eclipse_core_resources_markers.html

Consider this DTD fragment on that page:

<!ELEMENT super EMPTY>
<!ATTLIST super
type IDREF #REQUIRED>

type - the fully-qualified id of a marker super type (i.e., a marker type defined by another marker extension)


As actually used, the super is *not* an IDREF because the ID element in plugins generally does not (perhaps cannot?) use a fully-qualified id. That is the super attribute in actual plugin.xml files is usually something like com.foo.bar.local while the actual id attribute contains only local. 

Also note that the plugin XSD only lists these attributes as strings, not ID or IDREF.

Also see, https://github.com/GoogleCloudPlatform/google-cloud-eclipse/issues/3354
Comment 1 Eclipse Genie CLA 2020-12-30 12:44:27 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Elliotte Rusty Harold CLA 2020-12-30 16:53:41 EST
autoclosing bugs is rude. This is as valid as the day I filed it.
Comment 3 Eclipse Genie CLA 2022-12-21 06:08:22 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 4 Elliotte Rusty Harold CLA 2022-12-22 13:46:41 EST
autoclosing bugs is rude. This is as valid as the day I filed it.